Revolut Frontend Interview: Rounds, Take-Home & Questions

Last updated: August 2026

Quick Answer

The Revolut frontend interview follows the same spine as its wider engineering process: a recruiter screen, a take-home build task with a live walkthrough, one or two live coding rounds in TypeScript, a frontend architecture and skills round, and a team fit conversation, typically over three to six weeks. What is frontend-specific is what gets scrutinised: state and data flow, browser behaviour under a bad network, and whether a money-facing screen stays correct. Rehearse the coding and architecture rounds in OphyAI Coding Interview.

Element	What it looks like
Stack expected	ESNext, TypeScript, React and its ecosystem, styled-components, Webpack
Take-home	A small feature end to end, with tests and a README
Take-home walkthrough	45-60 minutes defending your architecture
Live coding	45-60 minutes, practical fintech-flavoured tasks
Timeline	Commonly 3-6 weeks

What Revolut Is Testing in This Round

Revolut is testing whether you can build a frontend that stays correct when the network and the ledger misbehave. That is narrower than general React competence, which is why engineers with strong UI portfolios still fail here. Four things carry the score. Data flow you can defend: where server state lives, what is derived, what is local, and why. Failure and loading states as first-class work: what the screen shows while a request is in flight, when it fails, and when a stale value is still on display. TypeScript used for safety rather than decoration: types that make an impossible state unrepresentable, not any sprinkled to silence the compiler. Money handled correctly: integer minor units, formatting at the edge, and no floating point in the client.

Revolut’s hiring approach, published with QuantumLight, leans on structured problem-solving where candidates get no extra information unless they ask, so an underspecified brief is part of the exercise. Our Revolut hiring playbook analysis covers that rubric.

What to Expect

The recruiter screen comes first and is short. After it, most frontend candidates report the take-home: a small feature built end to end with tests and a README, then a 45-60 minute walkthrough with a senior engineer. Revolut has not published a time limit, so treat effort estimates you read online as typical rather than official.

The walkthrough is an interrogation rather than a presentation. Candidates report questions of the form “why this architecture?”, “how would this scale ten times?”, and “where are the failure modes?”. The interviewer pushes past what you submitted, so a written list of what you left out, and why, is worth more than an extra feature.

The live coding round asks you to implement working functionality rather than solve a puzzle. Candidates describe practical fintech-flavoured tasks, sometimes in TypeScript in the browser: a transaction list, a currency conversion input, a debounced search over account history. Clean code and error handling matter more than algorithmic cleverness.

The skills and architecture round covers the frontend system: component boundaries, caching and invalidation, optimistic updates, validation, accessibility and rendering performance. The Revolut skills interview guide covers the general form of this round. A team fit conversation follows.

Example Questions and How to Answer Them

“Build a transaction list that stays usable on a flaky connection.” Name the source of truth first, then the caching and revalidation strategy, then what the user sees in each state: loading, stale-but-shown, empty, error, retrying.

“How do you manage server state here?” Distinguish server state from client state, say which pattern you would use and what it buys you, and describe cache invalidation on a write.

“The transfer request times out. What does the UI do?” Answer with idempotency: the client-generated key, what a retry sends, what the button does meanwhile, and how you make a double submit impossible rather than merely unlikely.

“What did you leave out of the take-home and why?” Have the answer written down before the call. Scope decisions defended calmly read as seniority; discovering the gap live reads as an oversight.

How to Prepare in 3 Days

Day 1: build a reference feature. Under a four-hour timer, build a small transactions screen in React and TypeScript end to end: fetch, cache, loading and error states, one form, and tests on the business rule and the failure path. Note where you ran out of time; usually it is the tests.

Day 2: break your own design. Write down what happens on a dropped connection, a duplicate submit, an expired token, and a stale cache after a write. Fix what is cheap and document the rest in the README, because that document is what the walkthrough follows.

Day 3: rehearse out loud. Present your build in ten minutes, then answer the questions above without notes. Use OphyAI Coding Interview to pressure-test the architecture and find the step your explanation skips, then present again unassisted. Use OphyAI Interview Practice for the team fit round. Start practicing →

Common Mistakes

Leading with the component tree. These rounds are about state, correctness and failure. Starting with the view layer signals where your attention goes.

No tests in the take-home. The most consistently reported rejection reason across Revolut’s engineering take-homes, frontend included.

TypeScript as decoration. Loose types and casts to silence errors undercut the main thing the language is being used for here.

Building broadly instead of finishing. A smaller scope with tests outscores a wider one that is half-built.

Related Guides

• Revolut interview guide (hub)
• Revolut software engineer interview
• Revolut build it interview round
• Revolut skills interview

Frequently Asked Questions

Does Revolut have a separate interview process for frontend engineers?

Revolut publishes frontend role descriptions but not a frontend-specific interview guide, so the stages match the wider software engineering process while the content is frontend-specific. Candidates report the same shape: recruiter screen, take-home with a walkthrough, live coding, a skills round and a team fit conversation. Ask your recruiter which rounds your loop contains.

What technologies does the Revolut frontend interview cover?

Revolut’s published frontend role descriptions name modern JavaScript (ESNext), TypeScript and browser APIs, React and its ecosystem, styled-components, and the Webpack module bundler, running against a Java and Kotlin backend. Interviewers probe underlying concepts rather than framework syntax, so expect questions about rendering, event handling and the browser platform alongside React specifics.

How long does the Revolut frontend interview process take?

Candidates commonly report three to six weeks from first contact to decision, with the take-home window and scheduling the walkthrough being where the time goes. Glassdoor’s candidate-reported average for Revolut front end roles is shorter than the company-wide average, though that sample is self-selected and small. Revolut has not published a target timeline, so treat both as reported rather than official.

Can I use AI tools during the Revolut take-home or live coding round?

Revolut has not published a policy we could verify, and rules differ by employer and role, so ask your recruiter and follow their answer. The walkthrough makes it partly moot: you defend every decision under questioning, so anything you cannot explain line by line is a liability however it was written. Use Interview Practice and Interview Copilot to rehearse that defence.

Sources and verification notes

Last reviewed August 2026. Revolut publishes frontend role descriptions but not a frontend-specific interview guide, rubric or take-home limit, so round content and effort ranges here describe what candidates report. Direct first-party fetches were blocked by network policy, so official pages were consulted through search summaries.

• Revolut Careers, Software Engineer (Frontend): published stack expectations.
• QuantumLight and Revolut hiring playbook: the structured framework and scorecards.
• Glassdoor, Revolut Front End Developer reports: round formats, TypeScript tasks, days to hire. Self-selected sample.
• Dataford, Revolut Frontend Engineer guide 2026: walkthrough length, architecture question pattern.
• InterviewQuery, Revolut Software Engineer guide: stage counts, fintech problem set.