Revolut software engineer candidates commonly report practical coding, concurrency and database trade-offs, system design, and later experience or team-fit discussions.
$130K
Avg. Base Comp
$190K
Avg. Total Comp
3-6 rounds
Typical Rounds
1-2 months
Process Length
Revolut software engineer interviews are described here as practical backend evaluations rather than a single algorithm screen. Candidates report live coding tasks such as a load balancer, account ledger, concurrent payment processor, or small warehouse-style service. Working code is only the starting point: reports mention validation, edge cases, tests or TDD, thread safety, maintainability, and explaining how an implementation behaves under concurrent requests.
Database reasoning is a recurring thread. Be ready to discuss a money-movement or balance-update workflow as a transaction, explain optimistic versus pessimistic locking, and connect isolation, idempotency, consistency, and multiple service instances to the design. Several candidates also encountered Java concurrency questions or detailed PostgreSQL discussions. The exact exercise can differ, so practice explaining the reasoning behind your choices rather than memorizing one prompt.
System-design reports include hotel or apartment booking, wallet or banking services, and card delivery. Candidates describe prompts that reward clarifying scope, establishing the main architecture, choosing a data model, and discussing operational trade-offs. Some interviewers provided little feedback, so practice driving the discussion and relating detailed questions back to the core design.
The supplied accounts describe multi-stage processes with recruiter, coding, system-design, and possible team-fit touchpoints. One candidate said the process took close to a month. Use any recruiter preparation call to confirm the upcoming format and rehearse concise explanations of your technical decisions.
Synthesized from 16 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.
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 | |
| Total Spent on Products | |
| Find the First Non-Repeating Character in a String | |
| Last Transaction | |
| Month Over Month | |
| Size of Joins | |
| Daily Logins | |
| Daily Retention Summary | |
| Google Maps Improvement | |
| Third Purchase | |
| Payments Received | |
| Sort Strings | |
| Rolling Average Steps | |
| Hurdles In Data Projects | |
| Cumulative Reset | |
| Word Frequency | |
| Success Measurement | |
| Duplicate Rows | |
| Count Transactions | |
| Subscription Retention | |
| Slow SQL Query | |
| Optimistic vs Pessimistic Locking | |
| Diagnosing Query Speed Degradation | |
| Solo ML Deployment | |
| Swipe Payment API | |
| Duplicate Product Names |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report recruiter conversations covering background, projects, collaboration, technologies used, and sometimes technical topics such as Big O, Java concurrency, transactions, locks, or database concepts. Some candidates also report preparation calls before technical stages.
Candidates report live coding tasks ranging from a load balancer or URL shortener to account transfers, payment processing, matrix problems, and small services. Expect to explain choices around validation, tests, edge cases, and correctness while making steady implementation progress.
Several reports describe follow-ups on thread safety, multiple service instances, PostgreSQL transactions, isolation, locking, MVCC, idempotency, and optimistic versus pessimistic locking. Prepare to relate a concrete implementation to its transactional or SQL behavior.
Candidates report designing booking, wallet, banking, task-assignment, and developer-platform systems. The discussion may require clarifying assumptions, defining data structures, addressing external dependencies, and explaining consistency, resilience, scalability, or workflow trade-offs.
Later conversations may cover prior projects, measurable impact, leadership, behavioral examples, and team alignment. Some candidates report that team-fit interviews remain evaluative and can include broad product, management, or design exercises.