Revolut Software Engineer interview questions

10 Software Engineers have shared notes from their Revolut interviews, with the questions they were asked in each round. That is 53% of the 19 Revolut interview notes on Screna AI.

10 Software Engineer interview notes

Revolut·Software Engineer·Hiring Manager Screen

Jul 2026
Interviewed for a bizops role at Revolut. Two questions, both focused on people/org health and how you'd back your decisions with data. Pretty conceptual, no case math or SQL.
  • How would you go about reducing attrition in a team or organization?
  • What data points would you use to support that decision?

“I went straight to the usual suspects: comp, growth, manager quality.”

View Post

Revolut·Software Engineer·Technical Phone Screen

Jul 2026
Did a technical phone screen for a Software Engineer role at Revolut. One coding problem, design-flavored, not a pure leetcode grind. Left feeling okay about it but not sure I nailed all the edge cases they were probably looking for.
  • Design and implement a minimal in-memory load balancer that routes requests to backend nodes chosen uniformly at random, supporting add, remove, and route operations with a fixed capacity cap.

“My first instinct was to use a HashSet for O(1) add/remove, but then I realized route() needs random access by index and a HashSet doesn't give you that cleanly.”

View Post

Revolut·Software Engineer·Hiring Manager Screen

Jul 2026
Interviewed for a bizops role at Revolut, just the one question I can recall but it was a meaty one that took up most of the conversation.
  • Walk me through a complex project you led that had significant delivery pressure.

“I had a decent example but I rambled way too much on the context and ran out of time to actually explain what I did.”

View Post

Revolut·Software Engineer·Technical Phone Screen

Jun 2026
Revolut backend interview covering some pretty dense fundamentals. Three questions, all technical, no fluff. The concurrency one went okay but I fumbled parts of the performance investigation and honestly blanked on some CQRS specifics.
  • How do databases handle concurrency, and how do isolation levels map to anomalies like dirty reads, non-repeatable reads, and phantom reads?
  • A service is running slower than usual. Walk me through how you'd investigate and isolate the bottleneck.
  • What are DDD and CQRS? When would you actually use them, and what are the common mistakes teams make?

“This one I actually felt decent about.”

View Post

Revolut·Software Engineer·Hiring Manager Screen

Jun 2026
Interviewed for a bizops role at Revolut. One question, pretty standard culture-fit territory, nothing too wild.
  • What kinds of people do you find it difficult to work with?

“Tricky because you can't just say 'nobody, I love everyone' but you also don't want to sound like a nightmare colleague.”

View Post

Revolut·Software Engineer·Technical Phone Screen

May 2026
Revolut technical screen for a software engineer role. The whole thing was basically one meaty concurrency problem about bank transfers, which makes sense given what they do. Not a bad experience but it definitely tests whether you actually understand locks or just know the buzzwords.
  • Design and implement a thread-safe bank transfer function that moves money between accounts atomically, handles concurrent calls correctly, and avoids deadlocks.

“This is the whole interview basically.”

View Post

Revolut·Software Engineer·Hiring Manager Screen

May 2026
Bizops interview at Revolut with a question focused on improving the recruiting funnel. Pretty operational and data-heavy, felt more like a mini consulting case than a typical behavioral screen.
  • How would you improve hiring conversion rates and reduce time-to-offer across the recruiting pipeline?

“I went straight to metrics first, which I think was the right call.”

View Post

Revolut·Software Engineer·Onsite - System Design / Architecture

May 2026
System design round at Revolut for a software engineering role. The whole thing was one long question about distributed data consistency across regions for a global banking product. Dense topic and the scope kept expanding as we talked.
  • Design a data architecture for a global digital bank that keeps customer and account data consistent across multiple geographic regions, while supporting balance checks, transfers, and card payments from anywhere in the world.

“This is the kind of question where you can talk for an hour and still feel like you barely scratched the surface.”

View Post

Revolut·Software Engineer·Onsite - Product Sense / Strategy

May 2026
Interviewed for a bizops role at Revolut, got a product improvement question focused on the cross-border payments feature. Pretty standard for fintech ops interviews but still caught me thinking harder than I expected.
  • How would you improve Revolut's cross-border payment feature?

“I went straight into user pain points, fees, FX rate transparency, transfer speed.”

View Post

Revolut·Software Engineer·Hiring Manager Screen

Apr 2026
Bizops interview at Revolut with a classic estimation question. Pretty standard case-style round, nothing too wild, but the question itself has more moving parts than it looks.
  • Estimate how long it would take for 100 cars stopped at a red light to all clear the intersection once the light turns green.

“I started with reaction time per driver, then added acceleration lag, and tried to estimate the time gap between each car moving.”

View Post