Android Interview Questions
Android interview questions
Android interview questions for mobile developers: Kotlin, lifecycle, Jetpack Compose, architecture, performance and testing.
Short answer: Strong Android candidates know Kotlin, the activity and fragment lifecycle, Jetpack Compose and an architecture such as MVVM. Seniors should cover coroutines, offline data, performance, modularisation and testing, and explain how they ship safely to the Play Store.
How to Use These Questions
Pick 6 to 8 questions that match the role level. Ask follow-ups on real trade-offs, not definitions. Score each answer from 1 to 4 against the “strong answer” column.
Android Interview Questions by Level
Junior
| Question | What a strong answer covers |
|---|---|
| Explain the activity lifecycle. | onCreate to onDestroy, configuration changes and saving state. |
| What is a ViewModel for? | Holding UI state across configuration changes, separate from the view. |
| Kotlin null safety: how does it work? | Nullable types, safe calls, the Elvis operator, avoiding !!. |
Mid-level
| Question | What a strong answer covers |
|---|---|
| How do coroutines and Flow work? | Scopes, dispatchers, cancellation, cold vs hot flows. |
| Compose vs XML views? | Declarative UI, state hoisting, recomposition and interop. |
| How do you store data offline? | Room, DataStore, caching and sync strategies. |
Senior
| Question | What a strong answer covers |
|---|---|
| How would you modularise a large app? | Feature modules, clear dependencies, faster builds and ownership. |
| How do you find performance problems? | Profiler, startup time, jank, memory leaks with LeakCanary. |
| How do you release safely? | Staged rollouts, feature flags, crash monitoring and quick rollback. |
A Practical Android Task
Ask the candidate to build a small Compose screen that loads a list from an API with loading, error and empty states, using a ViewModel and coroutines. Review state handling and tests.
Red Flags in a Android Interview
- Does long work on the main thread
- Ignores configuration changes
- Uses !! everywhere
- No tests at all
- Cannot explain their own architecture choice
Interview Scorecard
| Area | 1 β weak | 4 β strong |
|---|---|---|
| Kotlin | Java-style Kotlin | Idiomatic, null-safe Kotlin |
| Architecture | Logic in activities | Clear MVVM layers |
| Async | Callbacks, no cancellation | Structured coroutines |
| Quality | No tests, no monitoring | Tests plus crash tracking |
Hire Vetted Android Talent Without Running Every Interview
Staffenza runs five vetting steps for you: CV and portfolio review, technical assessment, live technical interview, English check and references. Remote engineers from India or Pakistan cost USD 225 a month on top of salary. In the UAE and Saudi Arabia, direct hire costs 15β20% of the first-year package, with a 3-month replacement guarantee.
The Bottom Line
Test Kotlin, lifecycle and state handling first. Seniors should show architecture, performance and safe release habits.
Related: hire Android developers, Java interview questions, system design interview questions, all interview question guides.
Ready to hire? Email [email protected] or use our contact page.
Android Interview FAQs
Should Android developers know Compose?
Yes for new work. Older apps still use XML views, so both help.
Kotlin or Java?
Kotlin is the standard for new Android code.
How senior should my first Android hire be?
For a new app, mid-level or senior, so architecture decisions are sound.
What task works for Android interviews?
A small list screen with API calls and state handling, under two hours.


















