Revolut Senior Software Engineer interview questions

1. Screening with recruiter Questions about my background, some technical questions just to check if I'm familiar with basic required things. Recruiter gave a very detailed information about what to expect from tech interview, which topics may be covered and what kind of questions may be asked. 2. Technical interview. Coding challenge. I was asked to implement simple in-memory load balancer for pool of IP addresses. Then requirements changes to add different balancing strategies. Another time I was asked to implement URL shortener service. In this interview focus must be on TDD, patterns, SOLID and clean code. 3. Technical interview. I was given a code snippet, Account class and service with transfer() method, where I need to implement transfer logic. In this interview focus is on thread-safety, concurrency, DDD. First implement with pure java locks (ReentrantLock), then option with DB lock. Implement pure procedural SQL implementation. Deep dive into transaction isolation levels, anomalies, optimistic/pessimistic locks. Also in previous interview I was asked about resilience/stability patterns, microservices, DB indexes. Overall impression is that they are don't have high need for engineers, just looking if some genious guy, who doesn't make any mistake while coding in the interview and answers all the questions 200% correct. If you loose attention and make couple of mistakes, you'll fail the interview. I felt like I did good in the interview, but was rejected both times. As I said, small mistakes, and you are done.

The process Pretty straightforward. Most of the technical questions are already on GitHub (revolut_coding), so if you work through those and can explain your answers clearly, you’ll be fine for the technical rounds. My experience I cleared all the technical stages, but things fell apart at the team match stage. • Recruiter: Very responsive in the beginning and guided me well. After the team matches though, communication just stopped — no feedback despite several follow-ups. • First team match: Honestly, not great. The interviewer interrupted a lot, dismissed answers as “obvious,” and the whole vibe felt unprofessional. As a Ukrainian, I personally felt there may have been bias based on my national and political background. I’ve since seen other candidates here mention similar concerns, so I don’t think I was the only one who felt this way. • Second team match: Completely different. The interviewer was professional, we discussed projects, trade-offs, success metrics — it was the kind of conversation you hope for. Concerns After that first team match, I filled out the interviewer feedback survey and mentioned the communication issues. Not long after, I was dropped from the process without explanation. I can’t prove the two were connected, but the timing was odd enough to make me wonder. Overall The technical process is clear and easy to prepare for, which is a plus. But the later stages were inconsistent, and feedback just stopped altogether. I personally felt some bias in one interview, possibly influenced by national or political background, and other reviews suggest I wasn’t alone. If you’re applying, study the GitHub repo and you’ll likely get through the technicals — just don’t expect much clarity or feedback once you hit the team match stage.