J'ai postulé en ligne. Le processus a pris 3 jours. J'ai passé un entretien chez Revolut en oct. 2024
Entretien
I recently had an interview with Revolut that left me quite frustrated. The task given was to implement a class for registering instances with unique addresses, with an additional requirement that the load balancer could accept up to 10 addresses. After that, I was asked to develop an algorithm to randomly return one of the registered instances when invoking a method multiple times. There was supposed to be a third requirement, but I wasn’t given the chance to complete it because they claimed that a senior engineer should solve all of these tasks in under an hour.
This is highly unreasonable because it fosters an environment where quick, poorly thought-out solutions are prioritized over maintainable, well-structured code. When I asked at the beginning if I should write unit tests, I was told it's "up to me," but in reality, they could have just said not to waste time, as the interview was apparently focused more on speed than thoroughness.
Overall, it felt like a useless interview that values speed over quality and encourages engineers to produce fast but ugly, unmaintainable code. This kind of process is not what I would expect from a company aiming to hire experienced, thoughtful engineers.
1
Autres retours d’entretien d’embauche pour un poste comme Senior Software Engineer chez Revolut
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.
Meilleures entreprises pour « Rémunération et avantages » près de chez vous