Revolut Live Coding Interview: 60-Minute Format, Tasks & Prep

Last updated: August 2026

Quick Answer

The Revolut live coding interview is a 60-minute round in which you build a small working service in your own IDE while an engineer watches. Candidates report roughly 10 minutes of introductions, about 40 minutes on a two-part task, and 10 minutes of follow-up questions. It is not a LeetCode round: the tasks are miniature production problems such as an in-memory account service or a load balancer, and the score comes from thread-safe, tested, readable code rather than an optimal algorithm.

Element	What candidates report
Duration	60 minutes: about 10 intro, 40 coding, 10 follow-up
Environment	Your own IDE, screen shared, your own language
Task shape	Two connected parts, the second extending the first
Deliverable	Working code with unit tests, not pseudocode
Interviewer	One engineer, occasionally two

What Revolut Is Testing in This Round

Whether you write code that could be merged. The round simulates a real ticket rather than a puzzle: do you handle concurrency correctly, do you write tests without being asked, do your boundaries survive a second requirement landing halfway through, and do you handle errors instead of assuming the happy path. The follow-up questions carry as much weight as the code, because a candidate who ships slightly less and diagnoses its weaknesses accurately outscores one who finishes and cannot name a single flaw.

What to Expect

Format. One 60-minute video call, screen shared, coding in your own editor. You choose the language: Java and Kotlin are common given Revolut’s backend stack, but candidates report Python, Go and C# without penalty.

The task. A small service with two connected parts, where the second adds a requirement that punishes a rushed design: another routing strategy, a concurrent caller, a new currency. Reported prompts include an in-memory account service handling deposits, withdrawals and transfers, a load balancer supporting several selection strategies, and a currency conversion engine.

Expectations. Thread safety where the prompt implies concurrency, unit tests written as you go, explicit error handling for the ambiguous cases, and clean separation of concerns. Candidate reports name SOLID principles and test-driven development as stated evaluation axes.

Where it sits. The round usually follows the take-home task and precedes the Revolut system design interview and the culture rounds. The full loop is in the Revolut interview guide.

Example Questions and How to Answer Them

1. “Build an in-memory account service supporting deposit, withdraw and transfer.” Model the balance in integer minor units, never a float. Guard mutations so a transfer between two accounts cannot deadlock: lock in a consistent order, and say why. Write a test for the overdraw case before you write the transfer.

2. “Now make it safe under concurrent transfers.” This is usually part two and is the real test. State the invariant out loud (no transfer creates or destroys money, no balance goes negative), then implement it. A test that spawns several threads doing opposing transfers and asserts the total is unchanged is the most persuasive thing you can produce here.

3. “Implement a load balancer with pluggable selection strategies.” Define the interface first, implement round-robin, then show where least-connections slots in. Interviewers watch the seam more than the algorithm. Handle registration, removal, and an empty pool.

4. “Add a currency conversion step to the transfer.” Scope it: which rate, sourced when, rounded how, and what happens if the lookup fails mid-transfer. Rounding must not leak money; show where the residual goes.

5. “What would you change to make this production-ready?” Three answers ready: durability (persistence and an append-only ledger), idempotency (a client-supplied request identifier so a retried transfer cannot double-apply), and observability.

How to Prepare in 3 Days

Day 1. Build the in-memory account service from scratch, with tests, in 45 minutes. Throw it away and do it again; the second attempt is where the muscle memory forms.

Day 2. Build the load balancer with two strategies, then add a third without touching the first two. If you had to modify existing classes, your interfaces were wrong. Redo it.

Day 3. Write a multi-threaded test that fails against a naive implementation, then fix it. Rehearse the production-readiness answer until it is under two minutes.

Use OphyAI Coding Interview to pressure-test your concurrency reasoning on one of these prompts, then re-solve with nothing open. Follow it with a technical mock in OphyAI Interview Practice to rehearse narrating while typing. Start practicing →

Common Mistakes

No tests. The most cited reason candidates fail this round. One test written early changes how the whole session reads.

Using floating point for money. In a fintech interview this reads as inexperience, not as a shortcut.

Ignoring concurrency until the interviewer raises it. If the prompt mentions transfers between accounts, concurrency is the exercise.

Silence. The interviewer cannot score reasoning they cannot hear. Narrate the trade-off before you type it.

Over-engineering part one. An elaborate abstraction leaves no time for part two. Ship something simple with a clean seam, and set up your editor, test runner and a blank project the day before.

Related Guides

• Revolut interview guide
• Revolut software engineer interview
• Revolut system design interview
• Revolut build it interview round

Frequently Asked Questions

How long is the Revolut live coding interview?

Candidates report 60 minutes in total: roughly 10 minutes of introductions, about 40 minutes of coding across a two-part task, and a final 10 minutes of follow-up questions about your design. Some reports describe a 45 to 60 minute hands-on session with less preamble. Treat 40 minutes as your working budget and keep part one to half of it, because part two carries the scoring signal.

Is the Revolut live coding round LeetCode style?

No. Candidate reports consistently describe a practical build rather than an algorithmic puzzle: an in-memory banking or account service, a load balancer with several routing strategies, or a currency conversion component. Data structure knowledge helps, but the round is scored on thread safety, unit tests, error handling and clean structure. Preparing only with algorithm drills is the most common mistake for this round.

Do I have to write unit tests during the round?

Yes in practice. Candidate reports name test-driven development and unit testing as explicit evaluation criteria, and shipping no tests is the most frequently cited failure. You do not need exhaustive coverage in 40 minutes: one test for the core invariant, one for an error case, and one concurrency test if the task involves shared state will read far better than untested code that does more.

Can I use an AI interview copilot during the Revolut live coding round?

Revolut has not published a policy we could verify on candidate use of AI assistants during live interviews, and rules differ by employer and round, so ask your recruiter and follow what they say. This round ends with follow-up questions about your own code, so anything you cannot explain yourself works against you. The dependable use is preparation, before the real round.

Sources and verification notes

Sources checked August 2026. Direct first-party fetches were blocked by the network policy here, so third-party guides and candidate reports were consulted through search summaries. Revolut publishes no format, duration or rubric for this round, so every specific here is candidate-reported.

• InterviewQuery, Revolut software engineer interview guide: reported round order and the 60-minute live coding structure. Third-party, checked August 2026.
• Dataford, Revolut software engineer interview guide 2026: reported task types and the thread safety, SOLID and unit testing criteria. Third-party, checked August 2026.
• TechPrep, Revolut’s interview process 2026: reported stage sequence and overall timeline. Third-party, checked August 2026.
• Glassdoor, Revolut software engineer interview experiences: candidate accounts of the round, including the personal IDE. Self-reported, checked August 2026.