First stage was a HackerRank with two LeetCode-medium questions (one was Longest Consecutive Sequence) and an SQL question. Then an HR call with standard behavioural questions (motivation, why Revolut, etc.). The technical interview was 1 hour. First 30 minutes: coding task — implement a set without using hash tables, trees, or the built-in set. Second 30 minutes: general software engineering questions (SOLID, decorators, generators, OOP, database transactions, concurrency/race conditions). HR mentioned beforehand that test cases were expected. Writing unit tests during the interview took a fair amount of time, so time management is important. Previous interview cycle: Earlier year I had a URL shortener task (simplified, hashmap-based) with tests, which I passed. The following round involved designing a class for handling currency transfers between bank accounts (precision matters — decimals vs integers), followed by deeper questions on databases and locking/concurrency. Overall: The questions themselves aren’t unusually hard, but the interviews are very time-pressured. You need to code quickly and explain decisions clearly. Pay is competitive for grads, but the interview pace reflects a high-intensity environment.

The interview process mainly revolves around key 5-7 questions that they ask: TinyURL, Ledger etc. They want you to write a basic solution and then build on top of it. Scalability is the key factor that will be challenged. Make sure you understand how locks in DBs and distributed systems in general work before applying.