Books and interactive practice

Android interview prep

Senior Android loops go deep on the parts that break in production: a coroutine scope that outlives its screen, a Compose recomposition you did not expect, a process death that loses the user's work.

What the Android loop scores

RoundWhat the interviewer writes down
Kotlin and coroutinesStructured concurrency, cancellation, dispatchers and what you do with an exception in a child job.
Jetpack ComposeState hoisting, stability, recomposition scope and side effects, explained from a screen you built.
Lifecycle and process deathWhat survives configuration change and process death, and how you proved it.
ArchitectureLayer boundaries, where the source of truth lives, and how modules are split for a large team.
Android system designOffline-first data, WorkManager constraints, sync and battery, not only the server diagram.

Loops differ by company. This is the common shape of senior loops, not a promise about any one employer.

The second question

Follow-ups that decide the round

“The ViewModel collects a Flow in init. What happens on rotation?”

Tests whether you know which scope owns the collection and what restarts.

“The user backgrounds the app during an upload. Then the process dies.”

Tests whether your design survives the platform, not only the happy path.

“This composable recomposes on every keystroke. Why?”

Tests whether you can read stability and state reads, not guess.

Practice

Interview Runtime is the practice layer for Android: one book and a dashboard that asks the question, scores your answer against a rubric, and asks the follow-up. See Interview Runtime.