Android Developer Interview Questions and Evaluation Guide
Knowing Kotlin syntax isn't enough to call someone a strong Android developer. Good Android engineers understand lifecycle management, UI state, app architecture, networking, testing, performance, and debugging under real-world constraints.
This guide gives you 40 Android developer interview questions for junior, mid-level, and senior hiring, organized by skill area and experience level, plus a ready-to-use scorecard so every interviewer rates candidates against the same criteria.
What to Evaluate in an Android Developer Interview
Ten skill areas cover what separates a candidate who knows Kotlin from one who can actually ship reliable Android apps.
| Skill Area | What to Assess |
|---|---|
| Kotlin | Language fundamentals, null safety, coroutines, collections, code quality |
| Android Fundamentals | Activities, fragments, lifecycle, intents, services, permissions |
| UI Development | XML layouts, Jetpack Compose, state handling, navigation, accessibility |
| Architecture | MVVM, Clean Architecture, repository pattern, dependency injection, modularization |
| Networking and Data | REST APIs, Retrofit, JSON parsing, caching, Room, offline handling |
| Concurrency | Coroutines, Flow, threading, cancellation, background work |
| Testing | Unit testing, UI testing, mocks, testable code |
| Performance | Startup time, memory, battery, rendering, network efficiency |
| Problem Solving | Diagnosing issues, discussing trade-offs, handling ambiguity |
| Collaboration | Code reviews, cross-team communication, release ownership |
The 40 Questions
Pick a topic to open its questions. Each one includes a quick answer and what to listen for.
Questions by Experience Level
Same topics, different depth. Adjust what you ask based on seniority.
Junior Android developer questions: Foundations first
Kotlin basics, Android components, UI fundamentals, API integration, debugging, Git
- What happens when an Android device rotates?
- What is the purpose of a ViewModel?
- How do you call an API without blocking the UI?
- What's the difference between nullable and non-null Kotlin types?
- How would you show loading and error states on a screen?
- How do you debug a crash in Android Studio?
- How have you used Git branches or pull requests?
Mid-level Android developer questions: Independent delivery
Architecture, coroutines, Flow, testing, state management, offline handling, independent delivery
- How would you structure a feature using MVVM?
- How do you model UI state using StateFlow or LiveData?
- How would you implement offline caching for a frequently used screen?
- How do you test a ViewModel with asynchronous API calls?
- How do you prevent memory leaks in Fragments?
- What trade-offs would you weigh before adding a new dependency?
- How would you troubleshoot a slow or unresponsive screen?
Senior Android developer questions: System and team level
System design, modularization, performance, security, release strategy, mentorship, technical trade-offs
- How would you modularize a large Android application?
- How would you design an offline-first experience for a field-sales or logistics app?
- How do you decide whether a technical debt issue gets fixed now or scheduled later?
- How would you improve release quality and reduce production incidents?
- How do you balance performance, maintainability, and time-to-market?
- How would you guide a team migrating from XML layouts to Jetpack Compose?
- How do you set engineering standards that improve quality without slowing delivery?
Android Developer Interview Scorecard
Use this so every interviewer scores candidates against the same criteria instead of relying on gut feel.
| Evaluation Area | Weight | What Good Looks Like |
|---|---|---|
| Kotlin and Code Quality | 15% | Writes readable, safe, maintainable Kotlin |
| Android Fundamentals | 15% | Understands lifecycle, components, permissions, navigation |
| UI and User Experience | 10% | Builds responsive, accessible interfaces in XML or Compose |
| Architecture and Design | 20% | Makes sensible choices on MVVM, repositories, modularization |
| Networking and Data | 10% | Handles APIs, storage, errors, and offline requirements well |
| Testing and Debugging | 10% | Debugs systematically, writes useful tests for key flows |
| Performance and Reliability | 10% | Anticipates memory, startup, battery, and ANR issues |
| Communication and Ownership | 10% | Explains decisions clearly, takes responsibility for outcomes |
| Rating | Meaning |
|---|---|
| 1 · Weak | Cannot explain core concepts or apply them reliably |
| 2 · Below Expected | Knows some fundamentals but struggles applying them |
| 3 · Meets Expectations | Sound working knowledge, can contribute independently |
| 4 · Strong | Depth, judgment, clear problem-solving, reliable ownership |
| 5 · Exceptional | Expert-level depth, system thinking, strong technical leadership |
What Strong Android Candidates Demonstrate
Look for candidates who can:
- Explain Android lifecycle and UI state clearly
- Write maintainable Kotlin and use null safety appropriately
- Choose architecture based on product and team complexity, not habit
- Design for loading, error, empty, and offline states from the start
- Use coroutines and Flow without creating cancellation or lifecycle bugs
- Debug systematically instead of guessing
- Explain technical trade-offs in language product and design can understand
For senior roles, go deeper on system design, release engineering, security, and technical leadership.
Turn this into a structured interview
Turning a question list into a consistent, evidence-based interview process is the hard part. VProPle helps hiring teams build structured scorecards, guide interviewers with the right questions in real time, record and transcribe interviews, and compare candidate feedback objectively.
With VProPle, this Android question set becomes:
- A structured technical screening interview
- An expert-led Android developer assessment
- A role-specific scorecard for junior, mid-level, or senior hiring
- A recorded, transcribed interview for later review
- A consistent process across internal and external interviewers
Frequently Asked Questions
Common questions from hiring teams building an Android interview process.
Enough to assess the role without turning the interview into a checklist. Most structured interviews work well with 20 to 30 targeted questions across Kotlin, fundamentals, architecture, testing, and scenario-based problem-solving.
No. Coding matters, but Android developers also need to be evaluated on lifecycle knowledge, architecture, UI state, networking, debugging, performance, and collaboration.
Kotlin is the primary language for modern Android development, but candidates also need practical understanding of platform concepts, architecture, UI development, asynchronous programming, and debugging.
Ask about modularization, performance optimization, offline-first design, release reliability, security, technical debt trade-offs, and mentoring.
Yes, adjust the depth. Junior interviews should focus on fundamentals and practical implementation. Senior interviews should weigh architecture, system design, performance, and technical leadership more heavily.
VProPle helps teams standardize Android interviews with structured scorecards, expert interviewers, AI-supported interviewer guidance, recorded conversations, and evidence-based evaluation. Learn more about Interview as a Service.