Android interview preparation
Senior Android Interview Preparation
A senior Android preparation map built around lifecycle, state, concurrency and production decisions.
Short answer
What matters most
Senior Android interview preparation should connect Kotlin, coroutines and Flow, Jetpack Compose, lifecycle, persistence, testing and mobile system design. Interviewers want to see how you handle cancellation, process death, configuration change, stale data, offline writes, UI state and backwards compatibility. Prepare each topic as a decision with alternatives and constraints, not a definition. Build production stories around an incident, migration, performance problem, architecture change and disagreement. For coding rounds, communicate invariants and tests before optimizing. For system design, begin with the user journey and device constraints, define the source of truth, then cover sync, failure, observability and rollout.
The Android depth map
A credible plan covers the language, runtime and platform together.
- Kotlin semantics and collections
- Structured concurrency, Flow and cancellation
- Compose state and recomposition
- Lifecycle, process death and saved state
- Room, networking and offline synchronization
- Testing, performance and release safety
Prepare lifecycle-aware answers
Android work is shaped by ownership over time. Explain what survives navigation, configuration change and process death. Name which state can be reconstructed and which must be persisted.
Do not use ViewModel as the answer to every lifetime question. Explain the responsibility and the boundary.
Practice with production constraints
Design feeds, messaging, checkout and upload flows under poor connectivity. Trace pending mutations and background work. Then explain how metrics distinguish device, network and backend failures.
That practice makes platform knowledge useful during both architecture and behavioral rounds.
