I went through two steps in their interview process.

1. HR call: The HR person was very nice, and we had a good conversation. They asked common HR questions, plus a bunch of theoretical technical questions for screening purposes.

2. Live coding session: The task for live coding was quite interesting, but the requirements were really confusing. Basically, they wanted me to implement something using best OOP practices and TDD in 45 minutes (considering approximately 35 minutes, since time had to be spent on introduction and requirements clarification). The task consisted of three parts, but they didn't tell me about that upfront; they asked me to implement only the first part and then requested improvements if I managed to finish it. For 35 minutes, I managed to implement only the first part, using canonical TDD and spending time on proper design. Afterwards, I received feedback that I was spending a lot of time on what TDD is about (designing your implementation from tests, making them fail, making them green, refactoring, etc.).

So, I didn't even get what TDD meant to them then. Just writing some unit tests?

From this second interview step, it seemed to me that the rumors about work/life balance at Revolut were kind of true. Maybe they are looking for people who can do speed coding during their eight working hours and, if they can't finish something on time, have to work extra hours.

Different OOP design principles.