Senior Software Engineer applicants have rated the interview process at Revolut with 2.9 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 29% positive. To compare, the company-average is 35.5% positive. This is according to Glassdoor user ratings.
Candidates applying for Senior Software Engineer roles take an average of 15 days to get hired, when considering 69 user submitted interviews for this role. To compare, the hiring process at Revolut overall takes an average of 23 days.
Common stages of the interview process at Revolut as a Senior Software Engineer according to 69 Glassdoor interviews include:
Phone interview: 36%
One on one interview: 23%
Skills test: 22%
Presentation: 9%
Group panel interview: 4%
Background check: 3%
IQ intelligence test: 1%
Other: 1%
Personality test: 1%
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. I interviewed at Revolut (Singapore) in Jun 2026
Interview
The coding round itself isn't particularly difficult. The challenge isn't solving the problem—it's writing code that could realistically be shipped to production.
Getting the code to work is the baseline. What the interview really evaluates is whether you naturally make production-quality engineering decisions: choosing appropriate data models, validating inputs, designing maintainable APIs, handling edge cases, considering concurrency, writing tests, and producing code that can evolve as requirements change.
My impression is that they're testing engineering habits more than pure problem-solving ability. You can solve the problem correctly and still struggle if your design choices suggest the code wouldn't be suitable for a real production system.
Quite long an challenging. 3 stages of technical interview - live coding, technical discussion and system design. Then last stage team fit. It took almost a month to go through the whole process
Interview questions [1]
Question 1
System design - you need to prepare a system design
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