Revolut Software Engineer candidates commonly report recruiter screening, practical live coding, backend and concurrency discussion, system design, and a later team-fit conversation.
$150K
Avg. Base Comp
$185K
Avg. Total Comp
3-6 rounds
Typical Rounds
1-2 months
Process Length
Revolut Software Engineer interviews reported here place substantial weight on practical backend reasoning. Live coding is frequently paired with tests, concurrency, and follow-up discussion, rather than being limited to a familiar algorithm puzzle. Candidates describe implementing load balancers, URL shorteners, account transfers, account ledgers, and a concurrent calculator. Be ready to explain correctness, edge cases, test choices, and the trade-offs behind the code while still making steady progress.
For Java and backend-oriented tracks, recurring reports emphasize thread safety, deadlock avoidance, SQL transactions, database locking, ACID, CAP, CQRS, and concise explanations of distributed-systems concepts. A useful rehearsal is a transfer or ledger workflow: explain what happens under concurrent requests, choose a locking strategy, and connect the application logic to a SQL transaction. Some accounts also describe rapid technical questioning, so practice giving precise definitions before expanding on trade-offs.
System design is another recurring evaluation point. Reported prompts include apartment or hotel booking, card delivery, and integrating a service with an existing environment or third-party provider. Start by clarifying scope, then establish the core architecture, data model, dependencies, failure handling, and major trade-offs before diving into smaller details. Some candidates also report a later team-fit or manager conversation focused on past work and role alignment. Formats vary by team and progression, but the consistent preparation theme is clear communication about production-oriented engineering decisions.
Synthesized from 52 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 most demanding part of the process was the hands-on coding round: I had to implement a bank transaction while talking through my thinking in considerable detail. The exercise focused on concurrency and TDD, so it was not just about getting code working; I needed to explain how I would approach correctness and the implementation as I went.
The process moved from an initial screening into technical questions, the practical coding exercise, a system design discussion, and finally a team-fit conversation. In the technical portion, I was asked about areas such as database sharding and partitioning. The system design question was to design a URL shortener against a set of requirements. The interviewers were polite and calm throughout, which made the conversations feel comfortable despite the depth of the topics.
I received an offer. My main advice is to practice explaining a concurrent, transaction-style implementation step by step while using TDD, and be ready to discuss the tradeoffs in a URL shortener design along with database sharding and partitioning.
Prep tip from this candidate
Practice implementing a bank transaction with concurrency and TDD while narrating each decision in detail. Also prepare to design a URL shortener and discuss database sharding and partitioning.
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 | |
| Last Transaction | |
| Daily Retention Summary | |
| Month Over Month | |
| Daily Logins | |
| Size of Joins | |
| Real-Time Transaction Streaming | |
| Google Maps Improvement | |
| Third Purchase | |
| Payments Received | |
| Sort Strings | |
| Rolling Average Steps | |
| Hurdles In Data Projects | |
| Success Measurement | |
| Word Frequency | |
| Cumulative Reset | |
| Duplicate Rows | |
| Digitizing Student Test Scores | |
| Count Transactions | |
| Subscription Retention | |
| Slow SQL Query | |
| Concurrent LLM Serving | |
| Data Pipelines and Aggregation |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an opening recruiter or HR conversation about experience, motivation, expectations, project work, and sometimes technical fundamentals such as Big O, parallel processing, Java concurrency, PostgreSQL, or locking. Some also describe recruiter preparation calls before later stages, so use early conversations to clarify the track and expected format.
Candidates report practical coding tasks such as a load balancer, URL shortener, concurrent transfer, payment processor, parking service, matrix problem, or changes to an existing Android project. Testing, validation, edge cases, and narration may be assessed alongside a working implementation; the exact language and task vary by role.
Several candidates report follow-ups on thread safety, deadlocks, SQL transactions, optimistic versus pessimistic locking, isolation, idempotency, distributed systems, and resilience. Prepare to connect code-level decisions to database behavior and explain trade-offs concisely rather than relying on definitions alone.
Candidates report design discussions for reservation services, wallets, identity management, banking systems, CI/CD workflows, and task-assignment systems. The discussion may require requirements clarification, architecture, data modeling, external dependencies, concurrency, failure handling, and operational workflow; scope and interviewer emphasis differ.
Candidates who reached later stages report team-fit, hiring-manager, behavioral, or team-matching discussions. These may explore prior projects, measurable impact, leadership, manager feedback, weaknesses, and alignment with a team. Some reports describe more than one fit conversation, while others end earlier in the process.
