← Back to Directory

Revolut

Large Enterprises

Screna has 19 Revolut interview write-ups. The most reported round is the product sense round (7).

19 interview notes · updated Jul 2026

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·Product Manager·Onsite - Product Sense / Strategy

Jul 2026
PM interview at Revolut for the stock trading product. One case question about a revenue metric drop, pretty open-ended, felt like a diagnostic exercise more than anything else.
  • You're the PM for Revolut's stock trading product. Gross profit has dropped significantly over the past month. How do you approach this?

“I went straight into segmentation mode: is it volume, margin, user mix, something in fees.”

View Post

Revolut·Backend Engineer·Technical Phone Screen

Jun 2026
Backend-focused Q&A round at Revolut covering distributed systems, database internals, and architecture patterns. Pretty dense session, felt like they were stress-testing breadth more than depth on any single topic.
  • How does a global bank keep its databases synchronized across multiple regions? Think about replication strategies, consistency guarantees, and what happens when data conflicts arise.
  • Walk me through how a database manages concurrent transactions. Cover isolation levels, MVCC, and locking mechanisms.
  • A user reports the service feels slow. How do you investigate that end-to-end?
  • What is Domain-Driven Design and how does it differ from CQRS?

“This one took me a second to get traction on.”

View Post

Revolut·Backend Engineer·Technical Phone Screen

Jun 2026
Revolut backend interview that went straight into concurrency territory. The transfer function problem sounds deceptively manageable until you're actually in the room trying to remember why naive locking blows up.
  • Implement a transfer(from, to, amount) function that moves money between two accounts in a multithreaded environment. How do you guarantee correctness without introducing deadlocks?

“I started with the obvious read-write lock approach and the interviewer just kind of waited.”

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·Backend Engineer·Technical Phone Screen

May 2026
Revolut backend screen, one coding question about building a load balancer class from scratch. Pretty focused session, no fluff, they just wanted to see if you could handle the edge cases cleanly.
  • Design and implement a fixed-capacity load balancer that supports registering nodes, deregistering nodes, and randomly selecting an active node to route a request to. Make sure to handle cases like an empty pool, a full pool, and duplicate registrations.

“My first instinct was to just use a list and call it a day, but the random pick with removal efficiency started nagging at me pretty quickly.”

View Post