The interview process is unnecessarily long, making one question if the company has a clear idea of what it wants.

It begins with an HR interview where the recruiter asks technical questions. However, as the recruiter is not a developer, they seem to be merely seeking buzzwords. This is followed by a coding exercise consisting of four LeetCode-style questions (two easy, one medium, one hard) to be solved within 70 minutes.

The next phase involves an interview with their engineers, who present another LeetCode-style question. If you pass this stage, congratulations – you're not even halfway through!

Four more interviews await: one with the hiring manager (focusing on behavioral questions and explanations of past projects), two system design interviews, and a final LeetCode-style interview (as if the previous five LeetCode questions were insufficient).

1. HR asks: a) What is the time complexity of finding a number on an unsorted array? b) What are the advantages of using SQL or NoSQL? c) What would you do if you notice a query on your database is taking too long?

2. Number of steps in a grid DFS from a start node to a target node where you can only walk in one direction, incrementing both your coordinates or bouncing on the grid wall if not possible to do so.

3. Build a BST from a sorted array of numbers.

4. LeetCode Bus Routes problem.

5. LeetCode K Closest Points to Origin.

6. Design Google Maps.