J'ai postulé via un recruteur. J'ai passé un entretien chez Revolut en déc. 2019
Entretien
1. HR-screen - 30 min. About 8 general questions in CS on data structures, etc.
2. Pair programming session - 1h. Simple, but revealing task with TDD in mind. You will create design of simple system covered as 1 class, the idea is to TDD it with a dedicated test.
3. Technical interview & Systems design interview - 2h.
I had good times with Recruiter & pair programming Senior Engineer where feedback was rather good about me, but not with final interview with 4 Senior Engineers.
Feedback I got from recruiter was hair-pulling a bit - he mentioned couple of my errors during interview which I agree with but then he said that I didn't answered some questions - while I remember I answered them. Can't say how angry I am. But that's okay.
In systems design interview it's even worse - they didn't provide correct/incorrect answers - but rather said that I was not able to put enough justification for my solution. But during interview when I asked them if it's reasonable - they said - "yes, good". I always asked if that is the solution they are agree and looking for.
I bet if I was going to explain solutions a bit further they would say that I am too detailed.
The team itself is rather an average team of devs that I saw in 15 years of experience - both in terms of confidence & quality excellence.
For potential candidates I would suggest to find a good referral if you want to join the team cause even if you're good enough they may not like you and write in feedback that you didn't answer questions that you really answered correctly.
Bottom line
Interview is easy - but interviewers very subjective and will want to treat you as you don't know basic questions like what is encapsulation even if you decades experienced and had a solid CS teaching background. So be prepared to be confident - if you don't confident at all they will say you didn't answer question correctly - even if you did.
Attitude - we know better, but we will not tell you what's wrong :-) you just wrong :-)
I guess the truth is somewhere in between assuming that they have 40 new hires / month. Engineers just bothered with the interviews.
For me I decided not to apply anymore - it's all about luck now. Much depends if it's a good day and time.
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.
Questions d'entretien [1]
Question 1
Live coding:
Implement a load balancer.
Implement an account ledger.
SD:
apartment booking system
card delivery system
J'ai postulé via un recruteur. J'ai passé un entretien chez Revolut
Entretien
The experience was disappointing and reflected a lack of professionalism.
The interaction gave the impression of a disorganised or potentially unhealthy work culture.
Answered most of the questions accurately and to the best of my ability.
The interview was initially scheduled for a short time slot. Toward the end, the interviewer asked for my availability and indicated that they would schedule a follow-up session to continue the discussion. However, no further communication or follow-up was received.
J'ai postulé en ligne. Le processus a pris 5 jours. J'ai passé un entretien chez Revolut en mai 2026
Entretien
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.