The interview consisted of multiple steps:

1. A first call to assess experience and willingness to work at booking.
2. An HackerRank test with 4 problems to solve in about 75 minutes. You don't need to pass every test to continue, as they thankfully look at the code instead of just the score.
3. A technical phone screen with 2 engineers, requiring you to write code on a site without running it. Two problems were asked, along with the time complexity of each solution. This lasted about 1 hour, with 10 minutes dedicated to asking questions to the interviewers.
4. An onsite interview comprised of 4 steps:
   • A first short talk with the initial recruiter (20-30 minutes).
   • A technical interview with 2 engineers. They ask 1-2 problems, and you have to write the solution on a piece of paper (about 1 hour).
   • A design interview. They present a general problem and ask you to design a possible solution, along with estimates so that you can scale the solution accordingly (about 1 hour).
   • A final behavioral interview with a team lead, mostly about your experiences, projects you worked on, and some general questions on how you work and relate with coworkers.

After each step, there was always a call with the initial recruiter to give feedback on how it went. The feedback given is quite detailed; they let you know exactly what they liked and disliked so you can work on improving it.

Overall, a really good experience. I didn't get an offer due to some uncertainties in the last few steps, but was told to try again a few months later.

Technical interviews focus on standard algorithmic problems that can be found on LeetCode, HackerRank, CtCI, etc.

Some examples include:

• A variation of matching parentheses in a string.
• A variation of determining if a string is an anagram of another.
• Determining if an integer list is sorted.
• The 2-Sum problem.

The onsite interview is generally harder than the previous ones.