They reached out to me on LinkedIn, and I was told another person would reach out to me.

Soon after, I had the first phase of the interview with HR. It covered ordinary topics about myself, as well as things and technologies used by Revolut. At the end, there were some technical questions, I think just for a brief check of the candidate.

Then, I was recommended for the second phase of the interview: live coding. Before that, I was told that solutions should be simple and easy, so I kept that in mind.

On the live coding session, there was me and an amicable developer. I was sharing my IDE and talking while resolving "incremental" tasks. The developer sent requirements on chat incrementally, so at the beginning, there was one task, and later, additional "features" arrived as well.

At the end, after a few days, you receive an answer with feedback (in short): "YOU SHOULD USE STRATEGY DESIGN PATTERN AND TDD AND INJECT SEOKEYWORD BY CONSTRUCTOR" xD

So, I suggest you all not to take it easy and simple as I did. Obviously, you need to align with the interview answer key.

1st phase: ACID, event sourcing, optimistic lock, pessimistic lock, data structures, transaction.

2nd phase:

1. Given a long URL and an SEO keyword, return a short URL consisting of a constant short URL string plus the SEO keyword.
2. Given a long URL, return a short URL consisting of a constant short URL string plus four random alphanumeric characters.
3. Given two instances of the same service/application, how do you secure that one instance will use the solution from point 2, and the other instance will use yet another function for shortening URLs consisting of a short URL plus some number from 1 to n?