Revolut software engineer interview questions and preparation

A Revolut software engineering interview typically combines a technical screen or task, one or more coding and design conversations, and a values conversation focused on ownership and delivery speed. Expect to justify design decisions in terms of impact, not elegance.

Written by Ace Editorial · Published 23 September 2026 · Last updated 23 September 2026

What does the process look like?

Candidates commonly report a recruiter screen, a technical assessment or take-home, technical interviews covering coding and design, and a final interview with a senior engineer or manager.

The exact shape depends on the team and the level. Ask your recruiter which rounds are live coding and which are discussion.

What is assessed technically?

Practical coding fluency, system design appropriate to your level, and an understanding of reliability and correctness in a financial context.

  • Clean, testable code and clear reasoning while writing it
  • Data modelling and API design
  • Concurrency, idempotency and failure handling
  • How you would verify something is correct in production

What non-technical questions should you expect?

Ownership questions: what you shipped, how quickly, what broke and what you did about it.

  • Tell me about something you owned end to end
  • Describe an incident you handled in production
  • When did you push back on a requirement?
  • What have you shipped that you would build differently now?

How should you prepare?

Rehearse talking while coding, prepare two systems you have built in enough depth to defend the trade-offs, and prepare one incident story.

Example

"We needed idempotent payment retries. I keyed on a client-generated reference with a uniqueness constraint at the database level rather than in the service, because the service was already running three instances and I didn't trust an application-level lock."

What should you ask them?

Ask how code gets to production, what on-call looks like, how much autonomy an engineer has over technical decisions, and how quickly teams ship.

Frequently asked questions

Is there a take-home task?
Frequently for engineering roles. Timebox it, write tests, and include a short note on your trade-offs.
How hard is the technical bar?
Demanding but conventional — practical coding, design and reliability rather than puzzle questions. Confirm the format with your recruiter.
Which language should I use?
The one you are fastest in, unless the advert names a stack requirement.
Do engineers get behavioural questions?
Yes, and they carry weight — ownership and delivery speed are emphasised throughout Revolut's own hiring material.

Sources

Interviewing for this role?

Add the job advert and your CV. Ace shows the technical and behavioural questions you're most likely to face and which of your projects to use for each.

Build my interview pack

Free analysis first. You only pay once you've seen what we've found.

Keep preparing