InterviewPrepInterviewPrep· Job Insights

Android Developer Interview Preparation: Kotlin, Lifecycle and Architecture

Android interviews reward developers who understand the platform, not just the APIs: how the lifecycle really behaves, why configuration changes break naive code, and how coroutines, Jetpack and clean architecture fit together. This guide covers the recurring question themes, what interviewers probe about your production judgement, and how to prepare for coding, design and app-architecture rounds.

Start a free mock interview →

Question themes in Android interviews

Most loops touch these areas.

  • Kotlin fundamentals: null safety, data classes, extension functions, sealed classes, scope functions and higher-order functions.
  • Lifecycle and components: Activity and Fragment lifecycle, configuration changes, ViewModel and saved state, and why holding a Context reference leaks memory.
  • Concurrency: coroutines, structured concurrency, dispatchers, Flow versus LiveData, and handling work across configuration changes.
  • Jetpack and UI: Compose or XML, navigation, Room, dependency injection with Hilt, and lifecycle-aware components.
  • Architecture: MVVM, MVI, unidirectional data flow, and separating data, domain and presentation layers.

Expect a coding exercise plus an app-design discussion such as building an image-loading feed or an offline-first list.

What interviewers really probe

The platform punishes shortcuts, so interviewers test production instincts.

  • Memory and leaks: can you explain how a leaked Activity happens and how ViewModel and lifecycle awareness prevent it.
  • State survival: what happens on rotation, process death and back-stack changes, and how you preserve state correctly.
  • Threading discipline: keeping work off the main thread, cancelling coroutines, and avoiding jank.
  • Architecture reasoning: why you layer an app, how you make it testable, and where business logic belongs.
  • Compose versus View: if the team uses Compose, expect recomposition, state hoisting and side-effect questions.

Behavioural questions often cover a nasty production crash, an ANR you diagnosed, or a performance fix.

How to prepare effectively

Prioritise platform depth over memorising APIs.

  • Be able to draw the lifecycle and narrate exactly what runs on rotation and process death.
  • Rehearse a coroutine and Flow example, including cancellation and error handling.
  • Prepare one app architecture walkthrough: layers, data flow, DI and how you would test it.
  • Revise your UI toolkit deeply, whether Compose recomposition rules or View recycling in a RecyclerView.
  • Have a real story about diagnosing a crash, ANR or memory leak with tooling.

Explaining lifecycle and concurrency clearly under questioning is where interviews are won or lost. A free AI voice mock interview on InterviewPrep creates a session from your CV and a target Android job description, then scores your answers, pace and filler words, so your platform explanations stay confident and precise. Many Android engineers who love Compose polish also skim UI/UX Designer Jobs to find hybrid roles that reward that interaction craft.

Frequently asked

Is Kotlin mandatory for Android interviews now?
For most modern roles, effectively yes. Kotlin is the default Android language, so expect questions on null safety, coroutines and idioms. Java knowledge still helps for legacy codebases, but strong Kotlin fluency is what interviewers now look for first.
Do I need Jetpack Compose experience?
It depends on the team. Many have moved to Compose and will probe recomposition, state hoisting and side effects; others remain on XML views. Learn the team's stack from the job description, but understand the state and lifecycle concepts common to both.
What lifecycle question comes up most?
Configuration changes and process death. Interviewers love asking what happens on rotation and how you preserve state, because it reveals whether you understand ViewModel, saved state and the difference between them, rather than just memorising lifecycle callbacks.
How much system design is in an Android interview?
Usually app-level design rather than distributed systems: architecting an offline-first feature, an image feed, or caching strategy. Senior roles go deeper into modularisation, performance and testability, so scale your preparation to the level you are targeting.

Related prep

Nursing Interview Practice · Physician Interview Preparation · Medical Residency Interview Preparation · Teacher Interview Practice

Reading about it isn't practice.

Run a real AI mock interview built from your CV and a live job description — scored feedback on your answers, pace and filler words.

Start your free mock interview →