Revolut interview, decoded.

Revolut has described its five stages itself; candidate accounts add the home task, which not every loop includes, and the bar raiser. Sequential rounds, one at a time, with the home task the most variable in timing.

Revolut publishes five values and says its behavioural interviews test them; its CEO has described Never Settle as the one that contains the other four.

• Never Settle: the overarching one, on problems, execution, team and output
• Get It Done: people who work get priority over people who talk, in the company's own phrasing
• Think Deeper: if the idea makes sense, title does not matter
• Dream Team: the bar raiser exists to protect it
• Deliver WOW: customer first, internal or external, and keep it simple

The reported questions are practical and financial in the technical rounds and values-shaped in the last one.

The home task is where most Revolut engineering loops are decided. Four to eight hours of real work on a small feature, a deadline of five to seven days, and an architecture review afterwards where the structure is questioned. The examples candidates report are the company's own products in miniature; the grading is on production readiness rather than cleverness. Here is what each reported task asks and the shape that passes the review.

• A currency exchange API: Endpoints to quote and to execute an exchange, a rates source behind an interface so it can be faked in tests, money as integers in minor units or a decimal type, never a float, and a ledger entry per execution. The review asks what happens if the rate moves between quote and execution; a quote with an expiry answers it.
• Transaction categorisation: A pipeline from raw transactions to categories with rules first (merchant, amount, description patterns) and a place for a model later, plus a way to correct a category and have the correction stick. Tests on the rules and on the correction path; the review asks how a wrong category gets fixed for one user without breaking everyone.
• A notification service: An API to enqueue a notification, a worker to deliver it over at least two channels behind one interface, retries with backoff, and idempotency so a retried delivery cannot send twice. The review asks about ordering and about what a user sees if a channel is down.
• Tests, or nothing: Every account agrees: no tests, no next round. Unit tests on the logic, one integration test per endpoint, and the tests run from a single documented command. Test-driven is not required, but the coverage has to exist and the README has to say how to run it.
• The README and the review: Write the decisions: the structure, the trade-offs, what you would do with another day, what you deliberately left out. The architecture review is a defence of those decisions, so put them where the reviewer reads first.
• The clock: Four to eight hours is the budget the reviewers assume. A small feature finished, tested and documented beats a large one half done; scope it to what you can complete with tests in a single evening and a morning.

Build one of the three before you are asked: the currency exchange API is the most reported and the easiest to scope. Do it in the language of the role with tests and a README, then do the architecture review on yourself: why this structure, where it breaks, what a real ledger would need.

Levels.fyi medians for Revolut software engineers in Greater London, updated 7 September 2026 and read on 22 September; the all-level median is pulled down by a large junior population, so the level figures are the ones to use. Equity is private stock with regular secondary sales, most recently at $75 billion in November 2025, and an IPO is expected within two to three years by most reports. Vilnius, Porto and Bucharest pay on local bands; ask for the hub's range.

1. 01Build the currency exchange API before the task arrives: quote and execute endpoints, a fakeable rates source, money in minor units, a ledger entry per execution, tests, a README. Then review it as if you were the interviewer.
2. 02Tests are the gate. Whatever you submit, make the test command the first line of the README.
3. 03Practise implementing a feature on a small existing service in your own IDE in 45 minutes, talking as you go; the live round is that.
4. 04Have the multi-currency ledger design ready: double-entry, idempotent postings, and what a failed card payment does to balances.
5. 05Prepare one STAR story per value, with the follow-up already answered: what you would do differently.
6. 06Ask at the screen whether your loop has the home task and when the bar raiser sits; both vary by team.

This guide covers Revolut's software engineering loop. Product, operations and compliance roles share the recruiter screen, a home task and the values round but not the coding rounds. For management and leadership roles the loop is similar but the bar shifts to people, delivery and strategy, so pair it with the leadership interview prep hub. The bar for your exact role comes from the role-by-role guides, and the prep that actually transfers is spoken, so run a mock interview before the real one.

• 01eFinancialCareers, Revolut reveals its five-stage interview process (5 April 2024)Revolut's own description of the five stages, the system design round as the boss level, and the team-fit round as a speed date with the head of the department.
• 02TechPrep, Revolut's interview process 2026the HackerRank assessment's contents and the named problems (Longest Common Prefix, Missing Number, Perfect Squares, Reverse Linked List II), SQL and logic puzzles; the optional home task of four to eight hours with an architecture review; live coding in your own IDE; the 60-minute design round; the bar raiser.
• 03OphyAI, Revolut interview process 2026 (September 2026)the home task's examples by role (currency exchange API, transaction categorisation, notification service), the five-to-seven-day deadline, production readiness and edge cases as criteria, rejection without tests, the fintech design prompts, the hubs, and the three-to-six-week timeline.
• 04Interview Query, Revolut software engineer interview guide 2026the emphasis on clean code, error handling and tests in the coding rounds, and ownership and bias for action in the values round.
• 05Revolut, our DNA journey: reinforcing our core valuesthe five values as named, when each was added, and the CEO's framing of Never Settle as the one containing the others.
• 06Design Gurus, Revolut behavioural interview questionsthe reported values questions (delivery with little time, failure, incomplete information, challenging the status quo) and the bar raiser from outside the team.
• 07Levels.fyi, Revolut software engineer, Greater Londonthe junior, all-level, senior and lead medians, updated 7 September 2026, read 22 September 2026.
• 08CNBC, Revolut acquires full UK banking licence (11 March 2026)the licence after the 2021 application, and the $75 billion November 2025 valuation.
• 09Revolut, annual report 2025£4.5 billion revenue for 2025, up 46 per cent, and the loan book.
• 10Revelio Labs, Revolut headcountabout 18,566 employees as of March 2026.

Interview processes change. This reflects widely-reported and sourced conditions as of 2026 — confirm specifics with your recruiter, and treat it as a map rather than a guarantee.