Revolut Android and iOS Interview: Rounds, Tasks & Questions

Last updated: August 2026

Quick Answer

Revolut’s Android and iOS interview follows the same shape as its wider engineering process: a recruiter screen, a take-home build task with a walkthrough, one or two live coding rounds, a mobile architecture round, and a team fit conversation, typically over three to six weeks. The mobile-specific difference is what gets scrutinised: concurrency, offline and failure states, and how you structure a feature that touches money. Rehearse the coding and architecture rounds in OphyAI Coding Interview.

Element	What it looks like
Languages	Kotlin on Android, Swift on iOS
Take-home	A small feature built end to end, with tests and a README
Live coding	Working functionality, usually 2-3 sequential tasks
Architecture round	App structure, state, caching, offline behaviour
Timeline	Commonly 3-6 weeks; some locations run accelerated tracks

What Revolut Is Testing in This Round

Revolut is testing whether you write mobile code that survives a bad network and a real ledger. That is narrower than general Android or iOS competence, which is why strong UI developers sometimes fail here.

Four things carry the score. Correctness around state: what the screen shows when a request is in flight, fails, or returns after the user navigated away. Concurrency handled deliberately: coroutines and dispatchers on Android, structured concurrency or serial queues on iOS, with the races named rather than hoped away. Structure that survives change: a seam between feature logic and platform. Money handled correctly: integer minor units, no floating point, explicit rounding.

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

What to Expect

The recruiter screen comes first and is short. After it, most mobile candidates report the take-home task: 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 live coding round asks you to implement working functionality rather than solve a puzzle. Candidates commonly describe two or three sequential tasks where each new requirement stresses the design you chose for the first, with thread safety, SOLID structure and unit tests explicitly expected. Concurrency is a repeatedly reported filter for Kotlin and Java candidates, and the same expectation exists on the Swift side.

The architecture round is mobile-shaped: the local source of truth, caching, reconciling client and server state, and what happens to a request that succeeds on the server but never reaches the app. A team fit conversation then covers Revolut’s performance culture.

Example Questions and How to Answer Them

“Build a screen that shows transactions and works offline.” Name the source of truth first (the local store), then the sync strategy, the conflict rule, and what the user sees while stale data is on screen. An answer that starts with the view layer misses the question.

“How do you keep this thread-safe?” Be specific to the platform: which dispatcher, what is confined to the main thread, where mutable state lives, and whether you use a mutex, an actor, or immutable snapshots. Name the race you are preventing.

“The payment request times out. What happens?” This is the fintech question in mobile clothing. Answer with idempotency: the client-generated key, what the retry sends, and what the UI shows meanwhile. Never let the user double-submit.

“How would you structure and test this?” Answer with boundaries: what is injected, what is testable without a device, one test on the business rule and one on the failure path. “I would add tests” without specifics reads as a gap.

How to Prepare in 3 Days

Day 1: build a reference feature. Under a four-hour timer, build a small transactions screen end to end in your platform’s idiom, with a local cache, loading and error states, and tests. Note where you ran out of time; it is usually the tests.

Day 2: break your own design. Write down what happens on a dropped connection, a duplicate submit, a token expiry, and two concurrent writes to one balance. Fix what is cheap, document the rest.

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, and use OphyAI Interview Practice for the team fit round. Start practicing →

Common Mistakes

Answering with UI first. These rounds are about state, concurrency and correctness. Starting with the view signals where your attention goes.

Ignoring concurrency until asked. Bring it up yourself rather than waiting to be prompted.

Floating point for money. Use integer minor units. Reviewers read this as a proxy for financial systems experience.

No tests in the take-home. The most common rejection reason on the build task, on mobile as much as on backend.

Related Guides

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

Frequently Asked Questions

Does Revolut have a separate interview track for Android and iOS engineers?

Revolut publishes engineering role descriptions but not a platform-by-platform interview guide, so the honest answer is that the stages match the wider software engineering process while the content is platform-specific. Candidates on both platforms report the same shape: screen, take-home with a walkthrough, live coding, an architecture round and a team fit conversation. Ask your recruiter which rounds your loop contains, because it varies by team and seniority.

How long is the Revolut mobile take-home task?

Candidate reports consistently describe roughly four to eight hours of genuine work inside a five to seven day window, matching Revolut’s other engineering take-homes. Revolut has not published a limit, so treat that as typical rather than official. Budget the hours before accepting the brief, and finish a smaller scope completely rather than starting everything: a scoped submission with tests and a README outscores a broad one that is half-built.

How is the mobile architecture round different from a backend system design interview?

The scope is the app, not the fleet. Instead of sharding and load balancers, you are asked about the local source of truth, caching and invalidation, offline behaviour, background work, and what the user sees during each failure mode. Backend vocabulary in the wrong place reads as rehearsed. Our Revolut system design interview guide covers the backend version of this round.

Can I use AI tools during the Revolut take-home or interviews?

Revolut has not published a policy we could verify, and rules differ by employer and role, so ask your recruiter and follow what they say. The walkthrough is unchanged either way, because you defend every decision under questioning. Use Interview Practice and Interview Copilot to rehearse that defence beforehand, and never submit code you cannot explain line by line.

Sources and verification notes

Last reviewed August 2026. Revolut publishes engineering role descriptions and its hiring philosophy but not a mobile-specific interview guide, rubric or time limit, so the round content and effort ranges here describe what candidates consistently report. Direct first-party fetches were blocked by network policy where this post was written.

• Revolut Careers, Engineering: official mobile role descriptions and hiring stage language. Checked August 2026.
• QuantumLight and Revolut hiring playbook announcement: the structured interview framework and scorecards. Checked August 2026.
• InterviewQuery, Revolut Software Engineer interview guide: reported stage counts, live coding format and the concurrency emphasis. Checked August 2026.
• Glassdoor, Revolut Software Engineer interview reports: candidate-reported round formats and timelines. Self-selected sample. Checked August 2026.