◆ Sparround

Top questions & how to structure answers

With your profile (strong practice, theory gaps) the biggest risk is selling what you know badly. Answer structure fixes that:

For definition questions ("what is X?") — the three-sentence rule:

1. One precise definition (with the term) 2. What problem it solves / why it exists 3. One example from your own project

For comparison questions ("X vs Y?") — a criteria table: pick 2-3 axes (performance, lifecycle, testing), then a decision: "I choose X in this case".

For experience questions ("how did you...?") — technical STAR: context (1 sentence) → problem → your decision and why → outcome (with a number: crashes 2%→0.4%).

For questions you don't know — the most important skill: don't invent. "I haven't used that exact API, but in principle it should work like..." + show your reasoning. Interviewers catch invention instantly and value reasoning.

Question (by frequency)Answer's key points
Activity lifecycle + rotationCallback order, recreation, the ViewModel/SavedStateHandle split
launch vs async, what suspend issuspend ≠ thread; the exception difference; structured concurrency
StateFlow vs SharedFlow vs LiveDatahot/cold, state vs event, repeatOnLifecycle
The MVVM flow + whyOne-way dependency, testing, config changes
Retrofit error handlingHttpException/IOException, sealed results, the error body
RecyclerView optimizationThe recycling mechanism, DiffUtil, onBind don'ts
Compose recompositionUI=f(state), skip conditions, remember/hoisting
Memory leak sourcesStatic contexts, fragment bindings, listeners, LeakCanary

The 1-4 week prep plan: cover one stage's topics daily + practice answers aloud (talk through 2-minute answers — speaking, not writing). Final week: cycle the 8 questions in this table + the security stage's questions (the bank!) once a day. If mock interviews are possible, do at least 2 — talking under time pressure is its own skill.

🛠 Practice task

Speak, don't write — record yourself:

  • Give a 2-minute spoken answer to each of the 8 questions in the table, recorded on your phone.
  • Listen back and check three things: did you define it, did you give an example, did you exceed 2 minutes?
  • Record your "tell me about yourself" answer too and fit it into 90 seconds.

Done when: every answer contains a term + the problem + your own example.

📚 Sources and documentation