Revolut Software Engineer interviews, as candidates describe them, combine a recruiter screen, practical coding, system design and team fit, with a heavy focus on concurrency, SQL and banking-style problems.
$140K
Avg. Base Comp
$170K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Revolut Software Engineer candidates most often describe practical, banking-flavored coding rather than named algorithm puzzles. Two report building a load balancer, one of them using TDD with thread safety and tested random selection. Others report a concurrent money transfer between two accounts, and one candidate then translated that solution into an SQL transaction using optimistic or pessimistic locking. One live coding round required working in your own IDE and explaining how you would test the code. A URL shortener task came with follow-ups on SOLID and testing. Expect follow-up questions on ACID, database locks, CQRS, DDD and resilience patterns. One candidate said answers were expected to be concise and textbook-exact, and another was asked to explain the options for scaling an SQL database.
System design prompts vary. Reported examples include an apartment or hotel booking service that depends on a legacy third-party provider, a card delivery system, and integrating a FinOps-related service where the interviewer changed an assumption about a third-party API mid-design. One candidate who did not receive an offer after system design found the discussion pulled toward minor details. Clarify scope early, establish the core architecture quickly, and keep relating detailed questions back to the main trade-offs.
Some candidates mention recruiter prep calls before stages and feedback between them. Team-fit or team-matching interviews came after the technical rounds, and one candidate who reached the final Team Fit call was rejected there. Reports on pace, interviewer engagement and communication differ widely. They range from a compressed format with minimal interaction to a smooth, respectful process spread over several weeks. Outcomes include both offers and rejections, so prepare for a demanding technical bar and a variable experience.
Synthesized from 106 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Revolut process.
The coding question is the part I remember most from my Revolut process, and it was a practical one. I was asked to implement a load balancer in Java, which in practice meant building a service registry that tracks services, their instances, and where those instances live. The rules were specific: each instance is registered by its address, every address has to be unique, duplicate registrations need to be prevented, and the load balancer can hold no more than 10 addresses.
What made it manageable was the interviewer. The atmosphere was friendly and approachable, so talking through the problem out loud felt natural rather than like being graded on every word. The question was really testing whether I could take a list of requirements and turn them into a working implementation, with core Java fundamentals underneath.
I didn't get an offer. The role was framed as a graduate Java developer position, and the question stayed on core Java rather than anything exotic. The takeaway for me is that the constraints were the real test. Enforcing uniqueness and a hard cap matters as much as getting the basic add-and-lookup behavior to run.
Prep tip from this candidate
Practice building a small Java registry from written requirements alone, enforcing address uniqueness, rejecting duplicates, and capping the collection at 10 entries. The review stressed translating requirements into working code, so focus on those constraints rather than only the happy path.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Revolut
Write a query that returns all neighborhoods that have 0 users.
| Question | |
|---|---|
| Top Three Salaries | |
| Rolling Bank Transactions | |
| Like Tracker | |
| Top 3 Users | |
| Retailer Data Warehouse | |
| Total Spent on Products | |
| Find the First Non-Repeating Character in a String | |
| Daily Retention Summary | |
| Last Transaction | |
| Size of Joins | |
| Month Over Month | |
| Daily Logins | |
| Real-Time Transaction Streaming | |
| Google Maps Improvement | |
| Third Purchase | |
| Payments Received | |
| Rolling Average Steps | |
| Sort Strings | |
| Hurdles In Data Projects | |
| Success Measurement | |
| Cumulative Reset | |
| Word Frequency | |
| Duplicate Rows | |
| Suspicious Card Activity | |
| Digitizing Student Test Scores | |
| Count Transactions | |
| Subscription Retention | |
| Consecutive Spending Growth | |
| Slow SQL Query |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an initial recruiter or HR conversation that explains the process and the stages ahead. Some describe recruiter prep calls before later stages and feedback after each one. One candidate found the recruiter call rushed, while another found the prep hints directly useful.
Candidates report hands-on coding such as a load balancer, a URL shortener, an account ledger, or a concurrent transfer between two accounts. One describes TDD with thread safety, and another coded in their own IDE. Follow-ups may cover testing approaches, SOLID or an SQL version using locking.
Some candidates describe a technical Q&A on transactions, optimistic versus pessimistic locking, ACID, CQRS, DDD, microservices and resilience patterns. One reports roughly 30 minutes of fast, textbook-style questions, and another was asked about scaling an SQL database. Concise, precise answers typically help.
Candidates report prompts such as hotel or apartment booking with a legacy provider, a card delivery system, or integrating a FinOps-related service. One candidate found the interviewer steered toward minor details, and another saw assumptions change mid-design. Clarifying scope early may help.
Candidates describe team-fit or team-matching conversations after the technical rounds. One candidate said team matching weighed how closely past work aligned with Revolut's product scale and domain. Another was rejected at the final Team Fit call. Prepare concrete examples of past work.
