High-performance teams, career growth, and work-time flexibility
High-performance teams, career growth, and work-time flexibility
- Good compensation based on performance.
- Data-driven decisions, including product development and performance reviews.
- Strong tech foundation across the entire company.
- Very skilled teams, especially in engineering, with strong collaboration between teams.
- Autonomous teams and flexible working schedules, allowing each team and each person to easily manage their time.
- A lot of opportunities inside the company. We can easily switch products and learn new domains without leaving the company.
-
It may not be easy to keep a good WLB all the time, especially when working 100% remote. It requires each person to properly manage their time and priorities.
-
Fast-paced environment. This can also be a positive thing sometimes, as you feel you're delivering often and creating a sense of accomplishment. However, it may be hard to manage the WLB, especially when dealing with regulatory requirements.
Additional Ratings
Was this helpful?
Revolut Interview Questions
Revolut Interview Experiences
Senior Software Engineer
Technical recruiter asking very random technical questions. It felt like they probably had some sheet of acceptable answers because anything outside of that sheet (for example, if you wanted to elaborate or explain an opinion) was met with silence o
Senior Software Engineer
It's a lengthy process, and I didn't go past the first coding interview. First, you have a call with the recruiter. This call follows a script and involves a bunch of questions. Topics include: * ACID * HashMap time complexity * Database indexes * T
Senior Software Engineer
The process Pretty straightforward. Most of the technical questions are already on GitHub (revolut_coding), so if you work through those and can explain your answers clearly, you’ll be fine for the technical rounds. My experience I cleared all the
Senior Software Engineer
GermanyJanuary 27, 2020Technical recruiter asking very random technical questions. It felt like they probably had some sheet of acceptable answers because anything outside of that sheet (for example, if you wanted to elaborate or explain an opinion) was met with silence o
Senior Software Engineer
London, United KingdomOctober 1, 2023It's a lengthy process, and I didn't go past the first coding interview. First, you have a call with the recruiter. This call follows a script and involves a bunch of questions. Topics include: * ACID * HashMap time complexity * Database indexes * T
Senior Software Engineer
United StatesAugust 1, 2025The process Pretty straightforward. Most of the technical questions are already on GitHub (revolut_coding), so if you work through those and can explain your answers clearly, you’ll be fine for the technical rounds. My experience I cleared all the
