Revolut Software Engineer mock interview

London fintech super-app with the most rigorous take-home filter in UK tech. The 4-8 hour take-home is the largest elimination stage. Live coding requires thread-safe, SOLID, unit-tested code — not whiteboard pseudocode.

  • 4
    Stages
  • 4-8 hr
    Take-home
  • 6-7 weeks
    Process timeline
  • Free
    First mock

Why Revolut's take-home filter is unusually rigorous

Per techprep.app's Revolut 2026 process guide and ophyai.com's Revolut 2026 interview guide, the 4-8 hour take-home is the largest elimination stage in Revolut's loop. More candidates are filtered here than at any other point. The walkthrough — where you defend your submission to a senior engineer — is where the real grading happens. Submissions that work but can't be defended (or that lack test coverage, ignore concurrency, or skip failure-mode reasoning) fail at the walkthrough stage even if the core code is correct.

The live coding rounds also require thread-safe, SOLID, unit-tested code — not whiteboard pseudocode. Concurrency is a known filter at Revolut, especially for Java/Kotlin candidates. Race conditions, lock granularity, and starvation are explicitly graded across multiple coding rounds.

Cultural fit also matters more here than at Wise or Monzo. Revolut's 'Dream Team' / Never Settle culture is intense — long hours, fast pacing, high churn historically. The trade-off: Revolut on your CV opens doors, growth opportunities are real, and compensation is competitive. Stories that lead with bias-for-action read as on-culture; stories that lead with careful pacing or risk-aversion flag misfit.

What the loop looks like

Round-by-round

  1. 01

    Recruiter screen

    Pre-onsite
    15-30 min

    Background, tech stack, motivation specifically for Revolut (not just fintech). Light on technical content; recruiter calibrates fit and timeline.

  2. 02

    Technical home assignment

    Pre-onsite
    4-8 hours (your timeline)

    The defining stage. Substantial project — typically a fintech-flavored backend service. Where the LARGEST number of candidates are eliminated. Walk through your submission with a senior engineer in the next round.

  3. 03

    Take-home walkthrough

    Onsite (virtual)
    60 min

    Senior engineer asks: 'Why this architecture?' 'How would this scale 10x?' 'Where are the failure modes?' Collaborative discussion that pushes you beyond what you submitted.

  4. 04

    Live technical interviews × 1-3

    Onsite (virtual)
    45-60 min each

    Practical fintech problems — transaction processors, currency conversion services, data pipelines. 2-3 sequential tasks. Your code MUST be thread-safe, SOLID, and include unit tests. Not optional.

  5. 05

    Hiring manager round

    Onsite (virtual)
    45 min

    Fit with Revolut's 'Dream Team' / Never Settle performance culture. Stories about pushing through obstacles, shipping fast, working in high-intensity environments.

Question bank

Real interview questions reported by candidates

  • Coding

    "Take-home: build a small transaction processor with multi-currency support, idempotency, ACID guarantees within a single account, and exposed REST API. Submit with tests, README, and architecture notes."

    Source · techprep.app Revolut interview process 2026, ophyai.com Revolut interview guide 2026
  • Coding

    "Live coding task 1: implement a thread-safe rate-limited API gateway. Lock granularity, fairness, and starvation prevention graded."

    Source · interviewquery.com Revolut SWE guide, virtyaluk/revolut_coding GitHub repo
  • Coding

    "Live coding task 2: implement a currency conversion service that handles concurrent requests with stale-rate fallback. Must include unit tests."

    Source · interviewquery.com Revolut SWE guide, applyo.co.uk Revolut SWE
  • Coding

    "Live coding task 3 (Java/Kotlin candidates): concurrent producer-consumer with backpressure. Discuss lock granularity, race conditions, and how you'd test concurrency bugs."

    Source · revolut.com/blog/post/how-to-ace-your-java-interview-at-revolut, jobmentis.com Revolut SWE 2026
  • System design

    "Take-home walkthrough: "Why did you choose synchronous vs async processing here?" "What's the failure mode if the FX provider returns 500?" "How would this work across 3 regions?""

    Source · techprep.app Revolut interview process 2026
  • Behavioral

    "Tell me about a time you shipped something fast under high pressure. What did you cut, and what did you learn?"

    Source · techprep.app Revolut interview process 2026, ophyai.com Revolut 2026
  • Behavioral

    "Describe a time you disagreed strongly with a teammate on technical direction. How did you handle it? (Never Settle culture)"

    Source · techprep.app Revolut interview process 2026
  • Behavioral

    "Tell me about a high-intensity work period. How did you manage your time and stay productive?"

    Source · interviewquery.com Revolut interview guide 2025
  • Behavioral

    "Why Revolut specifically? Generic 'I like fintech' answers fail. Recruiter and HM grade specific connection to Revolut's product, mission, or growth."

    Source · interviewquery.com Revolut interview guide 2025, ophyai.com Revolut 2026
Common signals to fix

What gets you rejected at this level

  • Take-home that doesn't include unit tests

    #1 take-home failure mode. Revolut explicitly requires tests. Submissions without test coverage — even if the core code is correct — typically don't advance. Treat the test suite as part of the deliverable, not an afterthought.

  • Code that isn't thread-safe

    Concurrency is a known filter at Revolut, especially for Java/Kotlin. Live coding tasks where you ignore thread safety, race conditions, or lock granularity flag senior-engineer signal as missing. Even at mid-level, expect to discuss concurrency in every coding round.

  • Not defending take-home choices in walkthrough

    The walkthrough is where take-home grading really happens. If you can't articulate WHY you chose architecture X, what would break under load, or how you'd handle failure modes, the submission alone doesn't carry you. Practice defending your decisions out loud before the call.

  • Cultural fit gaps in Dream Team round

    Revolut's Never Settle / Dream Team culture is intense. Stories that lead with work-life balance prioritization, careful pacing, or risk-aversion read as off-culture. Revolut grades for bias-for-action and high-intensity comfort — not because everyone has to grind, but because culture-fit signal is real here.

  • Generic 'I like fintech' answer

    Recruiters and HMs explicitly grade Revolut-specific motivation. Generic answers about wanting to work in fintech or admiring the company lose signal. Reference specific Revolut features, growth milestones, or mission elements that resonate with your background.

How Applr's AI mock interview tracks Revolut's rubric

Applr's Revolut mock simulates the take-home walkthrough format — defending architecture choices, articulating failure modes, and pushing your submission's reasoning beyond what you submitted. Live coding tasks include concurrency primitives (locks, atomics, race-condition handling) graded explicitly.

The Dream Team behavioral round prompts bias-for-action stories and grades cultural-fit signal. Generic 'I like fintech' answers get flagged with rewrites that surface Revolut-specific motivation.

Adjacent loops

Related practice

FAQ

Is the 4-8 hour take-home really the largest filter?

Yes per multiple 2025-2026 sources (techprep.app Revolut process, ophyai.com Revolut 2026 guide): the take-home eliminates more candidates than any other stage. Submissions are graded on code quality, architecture decisions, test coverage, and ability to defend choices in the walkthrough. Treat it as the most important assessment in the loop, not a screening.

What language should I prep for Revolut?

Java and Kotlin are the most common per Revolut's own engineering blog (revolut.com/blog/post/how-to-ace-your-java-interview-at-revolut) and 2025 candidate reports. The take-home accepts most modern languages, but the walkthrough engineers will be more familiar with Java/Kotlin. Concurrency primitives in your chosen language — locks, semaphores, atomic ops — must be fluent.

How intense is Dream Team culture really?

Per efinancialcareers.com's London fintech comparison and 2025 Glassdoor reviews: Revolut's work-life balance score is 3.1/5 vs Monzo's 3.9/5. Intensity is real — long hours, fast pacing, high churn historically. The trade-off: Revolut on your CV opens doors, growth opportunities are real, and compensation is competitive. Stories that lead with bias-for-action read as on-culture; stories that lead with careful pacing flag misfit.

Does Revolut sponsor Skilled Worker visas?

Yes for software engineering roles in London. Revolut sponsors UK Skilled Worker visas; international candidates with UK eligibility have a clear path. Also has offices across Europe (Vilnius, Berlin, Amsterdam) which can offer alternative visa pathways depending on your situation. Confirm with recruiter early.

How does Revolut compare to Wise and Monzo for international students?

Three London fintechs, three cultures. Revolut: highest CV value, most intense (4-8 hour take-home, Dream Team), 6-7 week timeline. Wise: product-engineer mindset, conversational SD, 24-25 day timeline, more sustainable pace. Monzo: most engineer-friendly (no whiteboard, async take-home), best work-life balance, ~75% retention at 3+ years. All three sponsor visas. For maximum learning intensity + brand prestige: Revolut. For balance: Monzo. For product-thinking emphasis: Wise.

What's the salary band for Revolut SWE in London?

Per Glassdoor 2025 Revolut SWE reports and London fintech salary data: Mid-level SWE roughly £65-95K base + stock + bonus. Senior SWE £95-140K base + significant equity. Above Wise/Monzo bands but with the intensity trade-off. Equity has been substantial as Revolut has grown (per efinancialcareers fintech reporting); cash compensation alone trails US FAANG numbers as expected for London.

Ready to practice for Revolut?

Start free →