The interview process consisted of a technical debugging round where I was given a small Android project with multiple issues to identify and fix. The task required understanding the codebase, tracing the flow between components, and resolving bugs within a limited time. The interviewer evaluated problem-solving skills, code navigation, and debugging approach. Overall, the experience was structured and focused on real-world scenarios, especially around debugging and state handling in Android applications.

I did a ton of searching about Android Engineer interviews but couldn’t find much info, so I figured sharing my experience might help someone else. The whole process took around two weeks. After I applied online, a recruiter got in touch and set up a call with the hiring manager. It was a good chat—we went over my background and my experience with Android development, and the manager shared some details about the team. Next up was my first technical coding interview, which lasted 60 minutes. It wasn't the typical leet code drill; instead, it was live coding in Android Studio. About an hour before the call, I got an Android project with some code pre-written and some features that needed to be finished. During the interview, the interviewer asked me to do things like set up a ViewModel, use it to pull data from an existing repo, and send data back to the repo and more questions like that. The interviewer was really helpful throughout the process, but I felt like I didn’t nail it. In the end, the recruiter let me know they weren't moving forward with my application. All in all, it was a pretty pleasant experience, and everyone I interacted with was really nice.