Real, anonymous reports from people who interviewed for Software Engineer at Revolut, newest first and distilled into what to expect across the loop.
I started after a LinkedIn outreach and had a recruiter conversation where the process was laid out end to end. It felt organized, with a recruiter who stayed available as I moved through each step. I then went into a live coding interview followed by a system design interview, each one acting like a qualifier for the next round.
My process started with HR, where it was mostly straightforward technical conversation and setting expectations for what came next. Then I moved into technical rounds that were much more demanding, centered on building and explaining transactional-style behavior. The hardest part wasn’t just implementing logic—it was handling concurrency, locking, and getting the edge cases right, and they were very explicit that I’d be writing unit tests for the scenarios I covered.
The interview process typically starts with a recruiter conversation, followed by a series of technical rounds including coding, system design, and sometimes behavioral interviews. Candidates noted that the structure felt organized, but the timeline could be lengthy and sometimes repetitive.
Candidates faced live coding interviews that emphasized practical problem-solving, including concurrency, locking, and unit testing. The coding challenges often required a solid understanding of algorithms and data structures, with some candidates feeling the pressure of timed assessments.
The system design interviews required candidates to demonstrate a deep understanding of architectural concepts, including event sourcing, CQRS, and handling edge cases in distributed systems. Candidates were expected to articulate their design choices clearly and consider operational concerns.
Early stages included behavioral questions that assessed candidates' past experiences and alignment with company values. Interviewers looked for specific examples and familiarity with relevant terminology, indicating a focus on cultural fit alongside technical skills.
Candidates experienced varying levels of communication throughout the process, with some reporting delays or a lack of feedback after interviews. A consistent theme was the need for clearer follow-up and closure, especially after multiple stages.
The overall difficulty of the interviews was described as average to challenging, with specific emphasis on concurrency and database concepts. Candidates felt that meeting the technical bar was crucial, and those who struggled with key concepts often did not advance.
