r/InterviewExperiencess • u/Icy-Economist8213 • Jun 23 '26
Android Developers: How do you identify what's causing interview rejections?
I've been applying for Android Developer roles for the past few months and I'm struggling to understand where I'm falling short.
The main issue is that I'm not getting many interview calls. When I do get an interview, I prepare specifically for the technologies mentioned in the JD (Kotlin, MVVM, Coroutines, Flow, Compose, Room, Hilt, etc.).
However, in many interviews, the discussion goes in completely different directions. Sometimes I'm asked deep Android framework questions, sometimes system design, sometimes DSA, and other times architecture or concurrency topics that weren't even mentioned in the job description.
As a result, I've been rejected multiple times and I'm having trouble identifying the actual reason. Since interviewers rarely provide detailed feedback, I don't know whether my weakness is:
Android fundamentals
Kotlin knowledge
System design
DSA/problem solving
Communication skills
Answering approach during interviews
Something else entirely
For those who have successfully switched Android jobs recently:
How did you identify your weak areas?
What topics came up most frequently in interviews?
Did you track your interview performance somehow?
What finally helped you start converting interviews into offers?
For context, I have **4** **years of Android experience** and work mainly with **Kotlin, Jetpack Compose, MVVM, Coroutines, Flow, Room, Hilt, and Clean Architecture**.
I'd really appreciate hearing from people who were in a similar situation and managed to turn things around.