The recruitment process began when HR contacted me via LinkedIn and asked me to share my availability for an initial HR discussion. After providing my availability, I received an invitation for the discussion.
The process consisted of four rounds (this may vary based on experience and the role applied for).
In the first round, HR asked both general and technical questions.
Following this, the second round, the Coding round, was scheduled.
In the Coding round, I was given a problem to solve with code. The interviewer shared the problem statements via chat, and I had to solve them in code. After successfully completing the Coding round, I was scheduled for the next round, the Coding + Tech round.
In the Coding + Tech round, I was asked to solve a problem statement using code or pseudocode. The interviewers asked many questions related to multi-threading and concurrency. Both of them asked a variety of questions, and I loved this conversation. I even admitted when I didn't understand a question. After clearing the round, I realized how mature they were. Following this, HR scheduled me for the fourth and final round, the System Design round.
During the System Design round, I was given a problem statement and asked to discuss the final design, including API creation and schema design, etc. However, due to the interviewer's accent, I faced difficulty understanding what was being said. I had to clarify several times and get his agreement on what I thought the design was, as it's all about the conversation and how you would work with your peers in reality. Although, in my opinion, the interviewer's questions were more inclined towards the domain rather than technical aspects. Additionally, his accent made it difficult for me to understand 30-40% of what was being said. Unfortunately, I did not clear this round and received feedback that I was asking for more hints. Disappointed – but that's how it is. This interview should have involved discussing trade-offs rather than focusing on the domain perspective. His accent was a problem for me in understanding what was being said.
Mainly core Java, multithreading concepts, and distributed systems.
The following metrics were computed from 1 interview experience for the Revolut Lead Software Engineer role in London, United Kingdom.
Revolut's interview process for their Lead Software Engineer roles in London, the United Kingdom is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Revolut's Lead Software Engineer interview process in London, United Kingdom.