Android Lead Interview Questions

10,452 android lead interview questions shared by candidates

Round1: (Machine Test): Simple DSA, Apti, Android questions (MCQs) Round2(technical): easy DSA coding question, coding approach, then to write it. Then, android skills that we have on our resumes were discussed. Round3(technical/leadership): There will be some leetcode questions for coding, but highly optimized solutions are expected. (For example, O(n) ). There were no questions about approaches or attempts you were trying to solve. After 20 minutes of coding, a few Android questions about DI, Coroutines, CI/CD, etc. Leadership skills were then tested.
avatar

Senior Android Developer

Interviewed at JLR

3.9
May 29, 2025

Round1: (Machine Test): Simple DSA, Apti, Android questions (MCQs) Round2(technical): easy DSA coding question, coding approach, then to write it. Then, android skills that we have on our resumes were discussed. Round3(technical/leadership): There will be some leetcode questions for coding, but highly optimized solutions are expected. (For example, O(n) ). There were no questions about approaches or attempts you were trying to solve. After 20 minutes of coding, a few Android questions about DI, Coroutines, CI/CD, etc. Leadership skills were then tested.

HR round was good and was a basic discussion about my experience and what they are looking for. Technical round was really a good discussion, with MPM good and helpful in discussions, we touched on Java and Android topics (static, Interface vs Abstract classes, Android components, Threads vs Asynctasks etc), no coding involved at this point of time. Next round was a video onsite marathon for 4.5 hours. It started with me designing an Android App by fetching JSON data using HTTPUrlConnection (I asked for Retrofit but interviewer declined altogether), my computer was an issue at this point of time, so I had to work on her MAC PC remotely which was very uncomfortable (imagine writing code on a PC remotely you are not used to!!), I did just fine I guess, fetched the data and wrote some code but could finish it in time. Second round was cultural, went well. Third round was with the MPM again, went well. Fourth round was with another technical guy and he presented me a TRIE looking question (Of all my topics, this was the once I was least prepared, so I screwed up here), I told him my approach and was trying to get to a solution, but he made up his mind I guess. Next up was a system design round, went great and the final round was a design problem. It consisted of creating an android app while designing the underlying architecture(MVP), the model class, UI design, fetching web services and other stuff. I did fine in 5 rounds, but screwed up in one and that was the deal breaker. Overall a positive experience, only thing I didn't like was the marathon interview rounds, it really takes a toll on your body.
avatar

Android Developer

Interviewed at Life360

3.9
Feb 10, 2018

HR round was good and was a basic discussion about my experience and what they are looking for. Technical round was really a good discussion, with MPM good and helpful in discussions, we touched on Java and Android topics (static, Interface vs Abstract classes, Android components, Threads vs Asynctasks etc), no coding involved at this point of time. Next round was a video onsite marathon for 4.5 hours. It started with me designing an Android App by fetching JSON data using HTTPUrlConnection (I asked for Retrofit but interviewer declined altogether), my computer was an issue at this point of time, so I had to work on her MAC PC remotely which was very uncomfortable (imagine writing code on a PC remotely you are not used to!!), I did just fine I guess, fetched the data and wrote some code but could finish it in time. Second round was cultural, went well. Third round was with the MPM again, went well. Fourth round was with another technical guy and he presented me a TRIE looking question (Of all my topics, this was the once I was least prepared, so I screwed up here), I told him my approach and was trying to get to a solution, but he made up his mind I guess. Next up was a system design round, went great and the final round was a design problem. It consisted of creating an android app while designing the underlying architecture(MVP), the model class, UI design, fetching web services and other stuff. I did fine in 5 rounds, but screwed up in one and that was the deal breaker. Overall a positive experience, only thing I didn't like was the marathon interview rounds, it really takes a toll on your body.

Viewing 8351 - 8360 interview questions

Glassdoor has 10,452 interview questions and reports from Android lead interviews. Prepare for your interview. Get hired. Love your job.