← Back to Directory

Revolut

Large Enterprises

Screna has 3 Revolut interview write-ups. The most reported round is the technical phone screen (3).

3 interview notes · updated Jun 2026

Revolut·Backend Engineer·Technical Phone Screen

Jun 2026
Revolut backend interview that went straight into concurrency territory. The transfer function problem sounds deceptively simple but they really want to see if you've thought through what happens when two threads hit the same accounts at the same time.
  • Implement a transfer(from, to, amount) function that moves funds between two accounts in a multithreaded environment. How do you ensure correctness without introducing deadlocks?

“The naive version with two locks feels obvious until you realize thread A locks account 1 then waits for account 2 while thread B does the exact opposite.”

View Post

Revolut·Backend Engineer·Technical Phone Screen

May 2026
Backend-heavy Q&A round at Revolut covering distributed systems, database internals, and some architecture design. The questions were meaty and ranged from very practical to pretty theoretical. Not a lot of coding, mostly talking through how things work under the hood.
  • How does a global bank like Revolut keep its databases consistent across multiple geographic regions?
  • Walk me through how a database handles multiple concurrent transactions without corrupting data.
  • A user is reporting that the app feels slow. How do you investigate that end to end?
  • What is domain-driven design and how does it differ from CQRS?

“This one went longer than I expected.”

View Post

Revolut·Backend Engineer·Technical Phone Screen

May 2026
Revolut backend interview, got a load balancer design question that looked straightforward but had enough edge cases to trip you up if you weren't careful. Pretty standard technical screen format.
  • Design and implement a fixed-capacity load balancer that supports registering nodes, deregistering nodes, and randomly selecting a live node to route a request to. Make sure to handle edge cases like an empty pool, a full pool, and duplicate node registrations.

“The random selection part is easy enough, but I underestimated how much time the edge cases would eat up.”

View Post