The Interview process consisted of 1) A hackerrank coding challenge. It was fairly straightforward, nothing like leetcode, just some basic solution 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. 2)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, what's my expected salary (Good to do research on levels.fyi prior to get a better idea of salaries). This was a 15 minutes call 3) A 45 mins call with one of their engineers. In my case this was mostly behavioural 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 in the interviews 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 know do some technical prep as well related to your field. Think bigger picture, get out from coding/programming mindset and get into "owning the product mindset" and think about architecture, scalalibity, maintenance, testing etc when answering the questions. 4) 4 back to back interviews on one day. This was the toughest part of the interview process. It consists of one design interview, one behavioral interview, 2 technical interviews. For design interview, I suggest you watch a few youtube videos for that. 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 required. Behavioural interview was typical with tell me about a time questions. I suggest you prepare them beforehand instead of saying "umm umm umm" on the stop and thinking. Just write down the answers trutfully somewhere and somewhat keep them in mind during this interview. The 2 technical interviews were easy-to medium. It was a bit of a advanced form of the initial hackerrank question. Maybe more tougher than that. Just make sure you're well versed with Kotlin / Java (assuming ur interviewing for Android) and things will fall into place. It wasn't leetcode, it was more of a coming up with an algorithm to solve a particular business requirement. I enjoyed doing the questions.