The first round was with a hiring team member who asked about my current job, challenges, problems I have solved in the past, and experience in the relevant areas to their project.

The second round was a two-hour coding challenge on HackerRank. I really liked the problem and its scope.

Then there was an onsite interview, which had about six rounds.

• The first was a whiteboard coding and API design round. Questions were very relevant to the project.
• The following round was about my experience, roles and responsibilities, technical skills, and challenges from recent projects.
• Then there was lunch, which I believe was a cultural fit sort of discussion.
• After that, there was a coding round that was again highly relevant to the project and focused on hardcore computer science distributed systems fundamentals.
• The architect round involved solving distributed systems design challenges and discussing distributed problems from my recent projects and how they were solved.
• The final round was a problem-solving round, also relevant to the project. I believe it involved brainstorming solutions to some of their existing challenges.

Overall, it was one of the best interview experiences I had. The problems, discussions, and assessments were highly relevant to the projects and problems at hand, rather than random template-based or LeetCode questions.

All my interactions with individuals were warm and enjoyable.

Have you ever built a distributed database?

How would you implement a read/write lock for a table in a database?