The interview process consisted of:

• A HackerRank coding challenge. It was fairly straightforward, nothing like LeetCode; just some basic solutions pertaining to a business requirement. I didn't pass all the test cases, but I still got a callback, so don't worry, just do your best.

• An initial recruiter call where we had a general introduction and discussion. My recruiter asked me things such as why I am leaving my current job and what my expected salary was. (Good to do research on levels.fyi prior to get a better idea of salaries.) This was a 15-minute call.

• A 45-minute call with one of their engineers. In my case, this was mostly behavioral questions, but I've heard you can get technical questions as well, depending on your position and the engineer interviewing you. He asked me typical "tell me about a time" questions (which you can find elsewhere on Glassdoor) which I answered comfortably. The key is to just be yourself and answer things truthfully. The engineer asked me about a time I had to work on a difficult feature/product, and I gave my answer and then said my solution was absolutely horrible, after which we both laughed together. So don't be uptight and pretend you have never messed up anything; just be honest. Also, make sure you do some technical prep as well, related to your field. Think bigger picture, get out of the coding/programming mindset and get into an "owning the product" mindset, and think about architecture, scalability, maintenance, testing, etc., when answering the questions.

• Four back-to-back interviews on one day. This was the toughest part of the interview process. It consisted of one design interview, one behavioral interview, and two technical interviews.

  • For the design interview, I suggest you watch a few YouTube videos. When you're with the engineer, communicate clearly, don't fumble, and if you need some time, just let them know you're thinking this or that. Don't assume; clarify the scope of the question and walk them through your approach. No coding was required.
  • The behavioral interview was typical with "tell me about a time" questions. I suggest you prepare them beforehand instead of saying "umm, umm, umm" on the spot and thinking. Just write down the answers truthfully somewhere and somewhat keep them in mind during this interview.
  • The two technical interviews were easy-to-medium. It was a bit of an advanced form of the initial HackerRank question, maybe tougher than that. Just make sure you're well-versed with Kotlin/Java (assuming you're interviewing for Android), and things will fall into place. It wasn't LeetCode; it was more about coming up with an algorithm to solve a particular business requirement. I enjoyed doing the questions.

1. Tell me about a time you failed to complete a task.

2. Tell me about a time you had a conflict with a team member. How did you solve it?

3. How do you improve yourself?

4. Which coworker do you get on with the most, and how is your relationship with them?

5. Design a system that fetches data from a server and displays it on a mobile app.

6. Write an algorithm for sorting businesses according to their ratings.