Revolut System Design Interview: Questions, Rubric & Prep

Last updated: August 2026

Quick Answer

The Revolut system design interview is a 45-60 minute live round, usually after the take-home review, where a senior engineer asks you to design a fintech system such as a multi-currency ledger, a card payment flow, or real-time FX pricing. You are scored on whether you handle money correctly under failure, not on how many components you name. Rehearse one full fintech design end to end in OphyAI Coding Interview first.

Element	What it looks like
Format	Live video, shared whiteboard or text editor
Duration	45-60 minutes
Interviewer	Senior or staff engineer from a nearby team
Prompt style	An open fintech problem, deliberately underspecified
Applies to	Mid-level and above; junior loops often skip it

What Revolut Is Testing in This Round

Revolut is testing whether you can be trusted with money-moving infrastructure. That is narrower than general system design, and it changes what scores.

Interviewers look for four things: correctness under failure (what happens to a balance when a service crashes mid-transaction, a message is delivered twice, or a provider times out), explicit trade-offs (eventual consistency for a feed but strong consistency for a balance, and why), regulatory awareness (audit trails, immutability, and the banking licences Revolut operates under across jurisdictions), and driving an underspecified problem by asking for constraints rather than waiting to be given them.

The published Revolut and QuantumLight hiring playbook makes the last point explicit: candidates get no data unless they ask for it. Treat the opening five minutes as requirements gathering, not a formality. Our Revolut hiring playbook analysis covers that rubric across the whole loop.

What to Expect

The round usually lands after your take-home review, in the same block as the technical deep dive described in the Revolut software engineer interview guide.

You get a one-line prompt and a blank canvas. The interviewer typically stays quiet for a few minutes, then probes: “what happens if that queue backs up”, “where is the money at this instant”, “how do you reconcile at end of day”. Interviewers commonly push a design until it breaks, so a challenge is usually a probe rather than a sign you are failing.

Revolut’s backend is predominantly JVM based, so JVM services, event streaming, and relational stores with strong transactional guarantees will feel native to your interviewer. You are not required to use their stack, but you should be able to justify whatever you pick.

Example Questions and How to Answer Them

”Design a multi-currency ledger.”

The core insight is double-entry: every movement is two balanced entries, and balances are derived from an append-only log rather than mutated in place. Say that early. Then cover idempotency (a client-supplied key so a retried transfer cannot double-post), currency handling (integer minor units, never floats, with the FX rate stored on each entry), and reconciliation against provider statements.

”Design real-time currency exchange pricing.”

Clarify the latency target and volume first. Aggregate quotes from multiple liquidity providers, apply a margin, and serve the best rate from a hot cache with a short TTL. The interesting part is staleness: what you do when a quote expires mid-transaction, and how you circuit-break a provider returning bad or slow quotes.

”Design card payment authorisation.”

Walk the authorisation path end to end and be explicit about the strict latency budget a card network imposes. Cover the hold on funds at authorisation, settlement arriving later and possibly for a different amount, and partial reversals. Fail-closed versus fail-open when you cannot reach the ledger in time is a genuine judgement call, and interviewers want to hear you reason about it.

”Design a fraud detection pipeline.”

Separate the synchronous path (a fast in-line risk score inside the authorisation budget) from the asynchronous path (heavier models, analyst review). Discuss false positive cost explicitly: blocking a legitimate customer’s card abroad is real harm, not just a metric.

Practise defending one of these out loud in OphyAI Interview Practice, which gives follow-up questions and per-answer feedback rather than a silent whiteboard.

How to Prepare in 3 Days

Day 1: ledger fundamentals. Learn double-entry properly if you have not used it. Be able to draw the entries for a transfer, an FX conversion, a refund, and a failed payment. This topic underpins most Revolut prompts.

Day 2: failure modes. Take one design and stress it. Write down what breaks with duplicate messages, partial failures, and a provider outage, and what your design does about each. Practise saying “at this instant the money is held here” for every step.

Day 3: full rehearsal. Run one complete 45-minute design out loud, from clarifying questions to reconciliation, then a second on a different prompt. Use OphyAI Coding Interview to rehearse the structure and find where your reasoning skipped a step. Start practicing →

Common Mistakes

Designing a generic web service. A design that would work equally well for a social feed signals you did not engage with the money problem. Name the ledger, the idempotency key, and the audit trail.

Using floating point for money. This alone can sink a strong round. Use integer minor units.

Skipping the clarifying questions. Revolut interviewers deliberately withhold constraints, so diving straight into boxes and arrows costs you a scored dimension.

Ignoring reconciliation and audit. A regulated system must be provably correct after the fact.

Defending a choice too rigidly. Changing your mind with a stated reason reads as strength; digging in reads as inflexibility.

Related Guides

• Revolut interview guide (the hub)
• Revolut software engineer interview
• Revolut skills interview
• Revolut bar raiser interview

Frequently Asked Questions

Does every Revolut engineering candidate get a system design round?

No. It is standard for mid-level, senior, and staff backend and platform roles, and often skipped or simplified for junior and graduate candidates, whose loops weight the take-home and practical coding more heavily. Frontend and mobile candidates may get a client architecture discussion instead, covering state management, offline behaviour, and API design. Ask your recruiter which rounds your loop includes.

How long is the Revolut system design interview?

The round typically runs 45 to 60 minutes, including a few minutes at the end for your questions. Spend roughly the first five to ten minutes clarifying requirements, the bulk of the time on the design, and the final stretch answering probes on failure modes. Interviewers go deep on one or two areas rather than reviewing every component you draw.

What tech stack should I use in the answer?

Use whatever you can defend. Revolut’s backend is predominantly JVM based, so those choices will feel familiar, but nobody is scored on naming the company’s exact technologies. What is scored is whether your choice fits the constraint you identified: picking a strongly consistent store for balances and explaining why matters far more than which database you named.

Can I use an AI assistant during the Revolut system design round?

Treat outside tools as not permitted in live Revolut rounds unless your recruiter explicitly says otherwise, and ask if you are unsure. Use Interview Copilot and Interview Practice for mock rounds instead, where they give feedback on structure and completeness with no ambiguity about the rules of the real interview.

Sources and verification notes

Last reviewed August 2026. Revolut does not publish a system design rubric, so the format and scoring dimensions above describe what is typical and consistently reported by candidates. Treat it as a well-supported pattern, not a guarantee for your loop, and confirm your rounds with your recruiter.

• Revolut Careers: official role descriptions and engineering levels.
• Revolut Engineering Blog: public posts on Revolut’s architecture and stack choices.
• Glassdoor, Revolut Interview Questions: candidate-reported round formats and prompts. Self-selected, so read it for pattern rather than precision.