Revolut Strategy and Ops Manager (Revenue Team) Interview Experience
Revolut · Mid level · BizOps & Strategy
They gave me just raw CSAT numbers and basically asked, what is wrong with this data. I kept reaching for the nice rich consulting style dataset, and only later realized that was the whole test.
Interview process
I went through a recruiter screen, then a 45 minute aptitude test, and then a case or problem solving round where I got rejected before the take-home and later interviews. The big thing that threw me was that it did not behave like a standard consulting case where you can pull out a set framework and run with it. It leaned much more product than I had anticipated. In the main case they focused on CSAT, gave me sparse raw numbers, and wanted me to figure out what was wrong with the data and what I could infer from it.
Interview rounds · 3
- 1
Recruiter screen
I had a screening call with the recruiter where she walked me through the role, the process, location flexibility, and compensation, and she was very helpful about what to expect.
- 2
Online assessment
AnalyticalAfter that I did a 45 minute aptitude test with simple math questions, and it felt pretty straightforward.
- 3
Technical round
AnalyticalProduct StrategyData AnalysisThe case round felt less like a classic consulting case and much more product and data focused. I got pushed away from high level strategy answers and toward concrete inferences from a small set of numbers and recommendations tied to KPIs.
Q1. Think about the CSAT scores and the distribution. What's wrong with the data here, and what all can you infer from the data we've just shared with you?
How they answeredI started treating it like a consulting case and went toward broad, longer term fixes, like you could do A, B, or C to improve satisfaction. The interviewer kept nudging me back to the data. They had only given raw CSAT numbers, and I kept feeling like I needed more segmentation, more KPIs, a richer dataset. In hindsight that was the point. They wanted very targeted inferences from sparse data and recommendations tied to a metric and goal, and I was caught off guard because I hadn't interviewed for product roles before.
Follow-up questions- Can you think about this from the perspective of data and not from the perspective of solving it in a long term way?
Tips from the candidate
If you're coming from consulting, I would not go in thinking a profitability framework or some neat structure is enough. They want you to put a KPI against every recommendation and say what goal it moves. Also be ready to work with incomplete data, because I kept feeling like I needed more segmentation and more metrics, and that instinct kind of hurt me. Sometimes the test is just what you can infer from the raw numbers they already gave you.
Company culture
The process felt pretty seamless to me. The recruiter was very helpful the whole way, answered my questions about what to expect, shared notes and prep resources, and even sent pretty comprehensive feedback at the end on what worked for me and what did not. Both interviewers came across good to work with, and it gave me the sense that they do try to support people in growing into areas they do not fully understand yet.