Anyone that has done the problem solving interview with Revolut, could you share some insights on the type of case you received and any other advice?
Revolut problem solving interview


Hey there!
Revolut’s problem-solving interviews often feel different from traditional consulting cases. They tend to be open-ended and based on real business situations. For example, "What would you do if user engagement dropped?" or "How would you approach launching a new product?"
You likely won’t be given much data, so it’s less about calculations and more about how you think through a problem. The interviewers want to see if you can structure your thoughts, make reasonable assumptions, and communicate your reasoning clearly.
The goal isn’t to find the perfect solution, but to show that you can stay calm, think logically, and focus on what really matters. Being comfortable with ambiguity and prioritizing well makes a big difference.
To prepare, it can help to practice simple, business-style case questions, especially from tech or startup contexts, and get used to thinking out loud and structuring your answers clearly.
You've got this! Good luck!
Rita

From what I've seen Revolut’s problem-solving interview is usually a mix of business sense + data + logic, often framed like a mini case study.
Typical themes include:
- Market sizing (e.g., how many users might adopt a new feature)
- Profitability (e.g., why a product’s margins are declining)
- Operational decisions (e.g., how to improve a process or scale a team)
- Product trade-offs (e.g., choosing between growth levers with limited resources)
My advice:
- Be super structured. Start with a clear framework before diving into numbers.
- They love metrics! Be comfortable working with basic math, percentages, and interpreting charts.
- Think like a PM meets an analyst: they want sharp logic and practical judgment.
- Talk through your reasonin. Revolut values speed, but not at the cost of clarity.
And don’t stress if it feels open-ended—that’s part of the test. They want to see how you handle ambiguity.






