Senior Software Engineer applicants have rated the interview process at Revolut with 2.8 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 20% positive. To compare, the company-average is 49.8% positive. This is according to Glassdoor user ratings.
Candidates applying for Senior Software Engineer roles take an average of 18 days to get hired, when considering 5 user submitted interviews for this role. To compare, the hiring process at Revolut overall takes an average of 26 days.
Common stages of the interview process at Revolut as a Senior Software Engineer according to 5 Glassdoor interviews include:
Phone interview: 50%
Skills test: 38%
One on one interview: 13%
Here are the most commonly searched roles for interview reports -
The experience was similar to what has already been described by others. I passed the first two stages but did not pass the system design interview.
My first attempt was definitely on me — I was not prepared well enough. I took the feedback seriously, prepared much better for the second attempt, and expected a more balanced evaluation. However, the second system design interview felt frustrating because the interviewer repeatedly guided the discussion toward minor or less important parts of the design, which consumed a significant amount of time and prevented me from properly covering the core architecture and trade-offs.
Overall, the process was useful, but the system design stage felt inconsistent and highly dependent on the interviewer’s style.
Interview questions [1]
Question 1
Live coding:
Implement a load balancer.
Implement an account ledger.
SD:
apartment booking system
card delivery system
I applied through a recruiter. I interviewed at Revolut (Dubai) in May 2026
Interview
Interview begins with recruiter calling, explaining you the process
- Coding round
- System Design
- Hiring Manager round
- Bar raiser round
Each rounds are qualifier to another round. I did the coding round and system design, and I was ruled out
Interview questions [2]
Question 1
Coding round for the Matrix grid problem for 60 min coding round
First Part of the problem
- Randomly fills a matrix (a * b) with 5 'x' alphabet, reset would be 'o' alphabet
Second part of the problem (minesweeper game on Windows OS)
- Given a matrix fill with 'x', find number of minds adjacent to it
You need to solve both problems in 40 mins to qualify (First 10 mins Introduction, last 10 minutes is follow-up question)
Remember to ask follow-up questions else it mark as candidate isn't proactive in asking questions
2. System Design Round (90 mins)
They ask to design an internal developer portal that establishes a fully automated, version-control CI/CD pipeline at scale.
It basically involves designing the Internal developer, I started with requirements, non-funtional requirements, entities in system, I started with API design but they said it's okay to skip, and high level design.
I started with Component-Based Design where I drawn frontend, CLI, API Gateway, catalog services, ... and all other components of the developer portal
But they were interested in detailed CI/CD pipeline steps. This is where I screwed up; I caught the hint much later in the interview when there were 10 mins left, and I quickly drawn CI pipeline and a CD pipeline, but wasn't able to explain each step in the CD pipeline in detail.
They wanted a more comprehensive Workflow and Operational design of CI/CD pipeline instead of a component-based design of the internal developer portal.
Since I didn't complete the design, I was ruled out of the interview
I applied online. The process took 5 days. I interviewed at Revolut in May 2026
Interview
During the initial HR screening call, the recruiter explicitly stated that Revolut was not hiring for a specific team and that team fit would be determined only after the coding and system design stages.
However, after passing the screening, I received the following rejection message: “After carefully reviewing your experience, we've decided to move forward with candidates whose profiles more closely align with the specific requirements of the role. Please note that this decision is based on current team needs.”
This creates a clear inconsistency in the communication. If team allocation and specific requirements were to be evaluated only in later technical rounds, a rejection citing “current team needs” right after screening appears contradictory. Such practices can lead to candidates investing time in the interview process based on incomplete or misleading information at the early stage.