answer-card
Senior Android interview answer card
A speakable answer format for senior Android questions: the opening claim, ownership boundary, lifecycle risk, production tradeoff and recovery line.
Use this in practice
Use one card per Android question. The aim is to move from naming an API to explaining who owns the work, when it stops and how the design fails under real lifecycle pressure.
Fill the card in this order
- Question: copy the exact wording you expect to hear.
- Short answer: give the decision in one sentence before adding implementation detail.
- Ownership: name the component that owns the state, coroutine or side effect.
- Lifecycle boundary: explain what happens when the screen, process or user session ends.
- Failure mode: name stale state, duplicated work, cancellation loss, memory pressure or recovery behavior.
- Production tradeoff: explain why the chosen approach fits this product and constraint.
- Interviewer push: write the follow-up that would expose a memorized answer.
- Recovery line: prepare the sentence you use to narrow or correct an overclaim.
Worked example
- Question: Where should a long-running operation started from a Compose screen live?
- Short answer: the operation should live with the owner of the business state, not with a disposable composition.
- Ownership: a ViewModel can own screen-level work, while durable work that must survive process death belongs in a persistence-backed queue such as WorkManager.
- Lifecycle boundary: leaving the composition can cancel UI observation without necessarily cancelling business work.
- Failure mode: launching directly from composition without a stable effect key can duplicate requests during recomposition.
- Production tradeoff: ViewModel ownership is simpler for active screen work. WorkManager adds persistence and scheduling cost, so I reserve it for work that must complete later.
- Interviewer push: What changes if the user signs out while the work is queued?
- Recovery line: I would bind the work to an account identifier and revalidate authorization before execution or delivery.
Rehearsal check
- Keep the first sentence under 12 seconds.
- Name one lifecycle boundary in every answer.
- Explain one failure mode before discussing abstractions.
- Prepare one pushback question and answer it without changing your original ownership model.
Go deeper
The senior signal
Prepare for senior Android interviews with current reasoning across Kotlin, Coroutines, Flow, Compose, architecture, performance, security and system design.
The 24-hour Android interview answer book
Review the senior Android questions most likely to decide the loop and rehearse answers, pushes and recovery lines you can say out loud.
Use this resource inside a path.
The free tools are designed to plug into the larger Salari career system.
