
Revolut Product Analyst interview typically runs 3–6 rounds: recruiter screen, SHL/logic test, problem solving, case study, team fit, and bar raiser. The process spans one week to two months and is distinguished by its structured but often opaque communication.
$100K
Avg. Base Comp
$154K
Avg. Total Comp
5-6
Typical Rounds
2-8 weeks
Process Length
We've seen Revolut lean hard on structured problem solving under time pressure for Product Analyst candidates. Multiple candidates describe case-style prompts that start deliberately open-ended and only become solvable once you ask for the right data — one candidate was given a CSAT improvement problem and had to extract process and data breakdowns by asking the right questions before any analysis was possible. The pattern is consistent: Revolut is not looking for a polished answer upfront, but for a candidate who can frame the problem, identify missing inputs, and narrow to the real driver. Critically, one candidate flagged that the recommendation and prioritization portion carried the heaviest weight — which tells us the interview is ultimately testing how you convert analysis into a defensible action plan, not just whether you can diagnose correctly.
A recurring theme across experiences is that Revolut cares as much about product judgment and cross-functional credibility as analytical technique. Candidates were asked how they'd worked with Product before, how teammates would describe them, and what their responsibilities looked like across prior roles. We've also seen the company probe for a clear, convincing answer to why Revolut specifically — multiple candidates across different languages and markets flagged this as a meaningful evaluation point, not a throwaway opener. That combination suggests they want analysts who can influence product direction and operate across teams, not just pull metrics.
The less obvious signal is how much the process rewards composure under ambiguity. The logic test is fast and penalizes incomplete answers, the case rounds are interviewer-led with no pre-loaded data, and communication from recruiting can be slow or inconsistent. Candidates who struggled often cited losing control of the conversation or running out of time before reaching recommendations. Going in, the priority should be managing your own pacing — especially reserving enough time for the solution and prioritization portion, where Revolut appears to make its final call.
Synthetized from 5 candidates reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Revolut process.
So there were around six rounds. I got rejected in round three.
The first round was a recruiter screen.The second round was the SHL test, and the third round was problem solving.
After that, if you clear the problem solving round, there is: • Bar raiser • Product thinking round • Team fit round
Okay, so the screening round was pretty simple. They want to know if you are a good fit, and they ask about experience.
I would want to avoid any red flag questions or question-answers, such as, "Do you have any competing offers?"Okay, after that problem-solving part, the SHL test was easy, I think. But there is a time crunch pressure in it, so you want to answer questions as fast as possible, and you have to finish the test to avoid score reduction.
Questions are pretty easy, so if you just focus, type in, and do it, it will be fine.
Apart from that,The first question was an easy one, but there was huge time pressure: you have to do the whole question—the whole RCA—in essentially 30-35 minutes.
I think structure is very important in this question, where you have to structure your thoughts very clearly. It was purely interview-led, so you had to ask questions to get the data and then do the RCA.
There were huge marks for the recommendation, solution, and prioritization, so keep that in mind and keep aside at least 20 minutes for that later part of the problem.
Questions asked: The interview questions in the screening round were around:
The next round was the problem-solving round. The actual interview question asked was to increase the CSAT score of the airport.
In this question, you have to ask for data to map out the whole process of the CSAT scoring. They will give you a process breakdown and a data breakdown only if you ask the right questions.
From there, you have to solve where the CSAT is dropping and how to improve it. The latter part of the problem was around giving recommendations and prioritizing solutions to increase those CSAT scores.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Revolut
Write a query to get the total three-day rolling average for deposits by day
| Question | |
|---|---|
| Last Transaction | |
| Top Three Salaries | |
| Button AB Test | |
| Experiment Validity | |
| Like Tracker | |
| Month Over Month | |
| Daily Logins | |
| Google Maps Improvement | |
| Top 3 Users | |
| Declining Applicants | |
| Third Purchase | |
| Time on FB Distribution | |
| Total Spent on Products | |
| Rolling Average Steps | |
| Hurdles In Data Projects | |
| Cumulative Reset | |
| Size of Joins | |
| Post Composer Drop | |
| Assumptions of Linear Regression | |
| Testing Price Increase | |
| Daily Retention Summary | |
| Subscription Retention | |
| Payments Received | |
| Duplicate Rows | |
| Count Transactions | |
| Sample Size Bias | |
| Facebook Story Success | |
| Approval Drop | |
| Duplicate Product Names |
Synthesized from candidate reports. Individual experiences may vary.
An initial HR/recruiter call focused on your background, experience, motivation for the role, and why you want to join Revolut. Candidates reported standard introductory questions like 'tell me about yourself,' past responsibilities, career switches, and why this specific role, with little to no technical depth.
A timed aptitude assessment with around 40 questions in 20 minutes. The test is described as straightforward but very time-pressured, so speed and accuracy matter more than deep technical knowledge. Leaving questions unanswered can reduce your score, so pacing is critical.
An interview-led problem-solving round where the interviewer provides data only if you ask the right questions. Candidates described a structured RCA-style case, such as improving airport CSAT, with heavy emphasis on diagnosing the issue and spending significant time on recommendations and prioritization.
A deeper discussion with the hiring team or team lead about your experience, how you work, and how you fit the role. This round can include a case study or whiteboard-style discussion, along with questions about prior projects, team structure, and cross-functional collaboration.
A product-sense focused round with a senior leader centered on how you approach product decisions and explain your thinking clearly. Candidates reported questions about proposing features, product judgment, and broader product thinking rather than purely technical analysis.
Later-stage interviews focus on behavioral fit, collaboration, and alignment with Revolut's standards. Reported questions include how your manager and colleagues would describe you, examples of successful projects, and how you work with teams.