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." However, 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.
The following metrics were computed from 10 interview experiences for the Revolut Senior Software Engineer role in Germany.
Revolut's interview process for their Senior Software Engineer roles in Germany is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Revolut's Senior Software Engineer interview process in Germany.