Real Interview Experiences

RevolutStrategy and Ops Manager (Revenue Team) · L4

Verified

“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.”

RevolutProduct Manager · L5

“This was a problem-solving round of about 35 minutes with a product owner. At the start he explained the format: the case is specific to Revolut, no prior Revolut knowledge is needed, and the most important thing is to ask clarifying questions. The case: to grow Revolut for Business revenue over 12 months while at least keeping the current gross profit margin. He gave data when I asked (revenue by country, by segment and by revenue source) and said openly when he didn’t have something, asking me to make assumptions. At the end I had to give a short update. What went well: the atmosphere was relaxed and my questions got useful answers. What didn’t go well: I listed many levers without sizing gap or checking each idea against the margin constraint”

RevolutProduct Owner (Technical) · Intern

“Interviewer was quite curious about why Fintech specifically and why Revolut. Also asked about a project I had ownership in, and went quite deep into my role, and the whole product building process.”

RevolutBizOps & Strategy · L5

“This kind of interview is new to me as I don't have a tech background. The screening call was to make sure I matched the requirements. The CCAT/UCAT test wasn't too difficult but it is best to practice using examples on udemy so you can answer all 40 questions in 20 mins. The take home task took most of the week. I am new to SQL so there was a learning curve to try and get over.”

RevolutSenior Backend Engineer - AI Platform · L5

“Revolut processes are similar for all tracks. I was interviewing for AI platform but was given traditional Backend engineering questions: DB scale and concurrency, isolations levels, and multithreading. Things didn't go well because the interviewer was expecting a Product minded engineer when the role was about an AI platform engineer.”

RevolutProduct Manager · L4

“I think it went well, you need to know how to read the recruiter. He was very energetic. I prepared answers to typical questions”

RevolutSoftware Engineer · L3

“Its good, but I was bad and dont really remember much. But all rounds was good. HR was nice. Tech guy on tech interview was nice too.”

RevolutProduct Manager · L4

“Its moderate if you have prepared enough. Be ready with introduction and experience on your projects you have worked on process improvement and team management”

RevolutData Analyst · L5

“After a live coding round, I had a "Data Analysis" interview: 5 case studies built around one product scenario — an in-app ads widget for partner offers. Cases covered probability (joint + conditional/Bayes), funnel and metrics design with limited tracking, dashboard design, and A/B testing including quasi-experiment alternatives. It felt more like a structured conversation than an exam: we ran over time on some cases and the interviewer was fine with it, asked guiding questions when I got stuck, and cared more about reasoning than polished delivery. What didn't go well: explaining specific concepts precisely under time pressure was harder than expected, especially as a non-native speaker — but the interviewer worked with that rather than against it. ”

RevolutSoftware Engineer · L5

“Revolut focuses on postgres a bit too much. Technical screen included questions about postgres tuning and what work you're currently doing. I mentioned work around the big technical initiatives I'm running, but they were more interested no what I'm doing hands-on. I wasn't expecting questions on postgres, that ended up hitting me bad.”