Revolut interview questions fall into five groups matching its five rounds: motivation questions in the recruiter screen, an ambiguous business case in the problem-solving round, craft-specific questions in the skills round, collaboration and conflict questions in team fit, and depth-probing ownership questions in the bar raiser.
Last verified: August 2026
The useful thing to understand about a Revolut loop is that the rounds are not interchangeable. Each one is looking for something different, and an answer that scores well in one round can actively hurt you in another. A crisp, structured answer is exactly right in the problem-solving round; the same delivery in the bar raiser, where they are probing for depth, reads as rehearsed. Below is what comes up where, and what it's really for.
Motivation and logistics
- Why Revolut, and why now?
- Walk me through your background.
- What are you looking for in your next role?
- What's your notice period and salary expectation?
Low stakes, but not zero. This round is a filter for basic fit and logistics rather than a real assessment — the failure mode is a vague answer to "why Revolut" that would apply equally to any fintech.
An ambiguous business problem
There's no question list for this round, because you get one problem and spend 45–60 minutes on it. Publicly reported examples in this style include evaluating the trade-offs of offering a higher savings rate to attract deposits, and diagnosing a drop in card usage.
This is the round that decides most loops. Rather than list prompts, it's more useful to see one worked all the way through — the clarifying questions, the data that came back, and the final recommendation:
Depth in your actual craft
This round is role-specific, so the exact questions vary more than any other stage. What stays constant is the shape: it starts from work you've genuinely done and follows up until it finds the edge of what you actually know. For a product manager the ground it covers is:
- Metrics — which ones you chose, why those and not the obvious alternatives, and what they missed.
- Trade-offs — a decision where you gave something up, and what it cost.
- Prioritisation — how you chose between things that were all defensible.
- Execution — what actually shipped, and what happened to the numbers afterwards.
- Failure — something that didn't work, and what you concluded from it.
The thing being tested underneath all five is whether you personally made the decisions you're describing. Specificity is the tell: real owners remember the number, the date and the person who disagreed, while borrowed stories get vaguer the deeper you go.
How you work with people
| Question | What's being assessed |
|---|---|
| Tell me about a time you disagreed with an engineer or designer. | Whether you engage with the substance or pull rank |
| How do you handle conflicting priorities from two stakeholders? | Whether you decide, or escalate everything upward |
| Describe a project that failed. What did you do? | Whether you own your part of it |
The reliable way to fail this round is blame — not dramatic blame, but the quiet kind where every story has a clear villain who isn't you. Each story might be true on its own. The pattern across four of them is what disqualifies people.
Ownership, probed several layers deep
- Tell me about a time you took ownership of something with no clear path to resolution.
- What's the hardest decision you've made with incomplete information?
Only a couple of questions, but each one is explored much further than in any other round. You give an example; they ask what you specifically did, then who disagreed, then what you'd do differently, then what happened afterwards. Four or five layers into one story is where this round is decided — prepare three examples deeply rather than ten at surface level.
A note on where these come from
These are the questions I was asked or saw asked, written from my own loop rather than collected from elsewhere. Where a question is a well-known public example rather than one I was personally given, I've said so. I'd rather this list be shorter and accurate than long and padded with plausible-sounding questions nobody actually asked.
Want the complete solution for 5 problem-solving cases?
You've seen how the structure works. The full breakdown shows exactly how each case plays out:
- ✓ 5 different cases
- ✓ The exact questions I asked in each MECE bucket
- ✓ What data the interviewer revealed (and what it meant)
- ✓ How to avoid the timeline trap
- ✓ My final recommendation with prioritization
Instant PDF download · money-back guarantee
Frequently asked questions
What questions does Revolut ask in interviews?
Questions vary by round: motivation and logistics in the screen, an ambiguous business case in the problem-solving round, craft-specific questions in the skills round, collaboration and conflict scenarios in team fit, and ownership questions probing for depth in the bar raiser.
Does Revolut ask behavioural questions?
Yes, mainly in the team-fit and bar-raiser rounds. They focus on disagreement, ownership and decisions made without complete information, and interviewers probe several layers deep on a single example rather than moving quickly between topics.