The interview process was long; it took me six weeks and involved seven recruitment meetings in total, not counting the 'prep calls' with the recruiter. I believe this is too much time and resources spent deciding whether to hire me, especially for a company that everywhere describes itself as a 'fast-paced environment'.

The prep calls with the recruiter (Talent Acquisition Specialist) were very helpful. I felt like she genuinely wanted me to get the job. She provided a list of all topics I could expect to be asked about during every stage and offered tips on how to succeed.

The interview scheduling process was pleasant for the initial stages. I could simply choose a time from a calendar with available slots. However, in later stages, it became less straightforward. I had to provide my availability windows for the next few days and then wait up to two days for confirmation of the chosen slot. Interviews were often postponed at the last minute, and interviewers were frequently a few minutes late for meetings.

I passed the first four technical stages, which I would describe as having average difficulty. Knowing the topics beforehand, either from the recruiter or external sources, significantly eased preparation. System design was likely the most challenging, but I received very positive feedback. Up to this point, everyone was genuinely pleasant, and interviewers dedicated ample time to answering my questions.

The recruiter informed me that only a 30-minute team fit interview remained, and if there were no red flags, I would be hired. This seemed straightforward but proved otherwise.

I had three team fit attempts in total. The engineering managers did not find my experience particularly impressive. I described projects that led to my promotion in my previous company, but they either deemed them too simple or not sufficiently technical. Some managers appeared rather blunt, making those conversations an unpleasant experience.

Ultimately, I received feedback, which I believe was primarily based on the last team fit, stating that while my technical skills were adequate, I was not enthusiastic enough about joining the company. This feedback seems somewhat contradictory after investing so much time in the recruitment process. However, I acknowledge that I am not a naturally effusive person, so perhaps they made an appropriate decision.

I think Revolut attracts many exceptional candidates due to its fully remote work policy and impressive salary range. Consequently, they can afford to reject candidates based on seemingly superficial reasons, knowing that more candidates will follow, and it's preferable to avoid a mis-hire.

Create a system design for a hotel reservation system. A mobile app wants to book a room. To do this, you need to call a third-party API, which may not be reliable.

Discuss various relational database-related questions, including ACID and transactions, and optimistic locking.