Technical screening questions
Ask for one example per question and listen for specifics.
- How do you handle the Android lifecycle? A good answer: Activity and fragment lifecycle and ViewModel to survive changes.
- How do you do background work? A good answer: WorkManager, coroutines and constraints.
- How do you structure an app? A good answer: MVVM, a repository layer and dependency injection.
- How do you reduce app crashes? A good answer: Crash reporting, testing and handling edge cases.
- Describe a release you managed. A good answer: Signing, staged rollout and monitoring.
Quick screening questions
Use these when you have only a few minutes.
- Compose or XML views?
- Which apps did you ship?
- How do you handle configuration changes and lifecycle?
What separates the levels
Match the level to the requirement before you submit.
- Junior: builds screens and fixes bugs.
- Mid: owns features and releases.
- Senior: sets architecture and performance standards.
Red flags
Any of these is a reason to probe further.
- No published app.
- Java only with no Kotlin for a Kotlin role.
- Cannot explain lifecycle.
Tools you should hear mentioned
An Android developer with real experience usually names several of these without prompting.
- Kotlin
- Jetpack Compose
- Android Studio
- Room
- Coroutines and Flow
- Gradle
Run the call well
Ask for the last project first, then dig into the second or third question. Take notes on versions, team size and outcomes, and record them with the submission so the vendor’s later technical interview does not surprise you.
Frequently asked questions
How long should an Android developer screening call take?
Fifteen to twenty minutes is enough to cover the project, three technical questions and availability, rate and work authorization.
Do recruiters need to know the technology?
Working vocabulary is enough. Use the sourcing guide for the role and listen for specifics instead of judging technical depth yourself.