I applied through a recruiter. The process took 1 day. I interviewed at Revolut (London, England) in Feb 2021
Interview
I'm describing here my experience with the Live Coding Interview.
This is the first of their 6 steps process.
I was given to implement a service that does something relatively simple. Think simple business logic.
My approach was to gain all the clarifications at the beginning to make sure that what I implement I won't have to change too much.
After I completed the first requirement the second requirement required me to do quite a bit of refactor and also introduced a new concept that wasn't given any requirement. Normally introducing a new concept requires also it's own set of business use cases.
Anyway, the third requirement in the same manner and I got a bit confused with the refactoring but my interviewee help me not to go off track with solving the problems that come with refactoring, such as refactoring the previous tests.
Another tiny bit was maybe understanding the person because of the specific foreign English accent.
At then end I could ask him questions and he did his best to reply to them.
All in all a great experience but maybe unnecessary when you want to hire a Senior Engineer.
Interview questions [2]
Question 1
I see you have this method here, is there a way that we can eliminate it?
I applied through a recruiter. I interviewed at Revolut
Interview
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.
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.
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