The interview process was quite structured and well-organized. It began with a call from the recruiter, who explained the overall process. The first stage was an online coding round, where you were required to write production-grade code that compiles successfully and is covered with comprehensive unit tests. Next came another coding round, where you were asked to write a simple function and then translate it into an SQL query—this formed the first half of the round. The second half focused purely on technical questions related to databases, architectural patterns, distributed systems, microservices, deployment, observability, and more. Following that was the system design round. You were given a vague description of a system that needed to be integrated into Revolut's existing environment. The expectation was that you would navigate through the ambiguity by asking relevant questions until the interviewer was satisfied with your solution. Unlike typical system design interviews that focus on large-scale distributed systems like YouTube or Google Drive, this round was centered on FinOps-related designs. Next came the behavioral round, followed by the team-matching round. Before each stage, a recruiter would conduct a prep session, giving an overview of the types of questions you might be asked and providing feedback from the previous round. One downside of the process was the lack of detailed feedback. If you failed any round, you would simply receive a generic rejection email with no explanation, leaving little opportunity to learn from any mistakes. A notable negative aspect of interviewing at Revolut is the rigid approach to technical questioning. There is little consideration for a candidate’s thought process or experience; instead, they expect instant, precise answers. For example, if asked about CQRS, you are expected to deliver a Wikipedia-style definition in just a few sentences. Similarly, failing to recall what each letter in ACID stands for would be considered a red flag. The volume of technical questions is overwhelming, so a strong grasp of fundamentals is essential. Overall, despite not making it to the final stage, I am still satisfied with the process. However, even if I had received an offer, I doubt I would have accepted it, given the overly mechanical nature of the interviews, Revolut’s reportedly harsh company culture, and the widely discussed lack of work-life balance.

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.