La procedura ha richiesto 2 settimane. Ho sostenuto un colloquio presso Revolut
Colloquio
I was interview on the senior backend developer role. It consist of these steps:
1) 1h - Call with HR, where he suddenly starts to ask you technical questions (cqrs, O(n) , log(n), etc)
2) 1h - Live code assessment with 1-2 developers
3) 1h - Another deep tech talk with 1-2 devs, also practical task, but mostly questions
4) ~1h - Design tech talk, architecture
5) HR soft skills talk
Domande di colloquio [1]
Domanda 1
2) On live code assessment I was asked to write 3 tasks in a row on the same project about load balancing, just to look up at code speed writing, no deep knowledge needed. Junits.
3) A lot of irrelevant questions, deep understanding of how everything works under the hood, small code task on concurrency code, isolation levels, atomicy, replica and sharding, microserevices and monolith, I was expecting them to ask which assembler commands being called for particular operation.
Ho presentato la mia candidatura tramite un selezionatore. Ho sostenuto un colloquio presso Revolut
Colloquio
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.
Ho presentato la mia candidatura online. La procedura ha richiesto 5 giorni. Ho sostenuto un colloquio presso Revolut nel mese di mag 2026
Colloquio
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.
Ho presentato la mia candidatura tramite un selezionatore. Ho sostenuto un colloquio presso Revolut (Dubai) nel mese di mag 2026
Colloquio
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
Domande di colloquio [2]
Domanda 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