1. Phone screen with reqruiter 2. Online coding challenge with Engineer 3. On-site interview On-site interview was kind of confusing afterall, since the questions was asked easy and not directly related to the desired position. The Job description that they have on the web side is misleading also. They are looking for Team Lead/Principal Engineer who know a lot and can inspire their Android team to work better and solve problems that tey can't solve. Having good background and different experience from what they need will still interest their reqruiter, but doesn't the team, so as a result you might just waste your time.

I applied online and received a call from a recruiter. After that, I scheduled a coding interview consisting of two rounds, each lasting one hour. The first round was a technical coding interview that focused on my Kotlin experience and data structures and algorithms (DSA) through a use case problem, rather than typical LeetCode-style questions. The second round focused on Android development coding to assess my knowledge in that area. I was surprised by this round because I hadn't been informed that it would involve Android; I had assumed it would be similar to the first round. Although I performed well in both rounds, I did not receive any response afterward, and they went silent. The recruiter was helpful, and my interactions with the interviewers were pleasant. I'm unsure where things went wrong, but overall, the experience was good.