What decides a senior mobile interview.
Written by Mike Salari after 500+ technical interviews: the follow-up questions, the system design and architecture rounds, and the leveling that sets the offer.
The follow-up decides the senior mobile interview
An interviewer's view of the moment one fact changes, and why that moment carries the offer.
Senior vs staff mobile interview: the signals that set level
The same correct answer can be scored at senior or at staff; the difference is scope, trade-off ownership and what you say you would measure.
Swift concurrency interview questions where answers break
The six Swift concurrency questions senior and staff iOS loops keep asking, the answer that sounds right, and the follow-up that decides the score.
Swift 6 strict concurrency migration: what breaks first and the fix
The order I migrate targets in, the six kinds of errors every existing iOS app hits, and the fix for each one, checked against the Swift 6.3 compiler.
Kotlin coroutines interview questions: where answers break
An interviewer's view of the coroutine and Flow questions in senior Android loops, and the follow-up that separates a memorized answer from a reasoned one.
Android system design interview: offline sync at staff level
The offline notes app is the most common mobile design prompt in senior and staff Android loops, and the diagram is the easy part.
Mobile architecture interviews: modularization that holds up
An interviewer's view of the architecture round, where "modularize everything" is the answer that ends the conversation early.
How senior mobile take-home assignments are actually graded
A reviewer's view of the senior take-home, where the README is read before the code and the most patterns rarely wins.
runCatching swallows cancellation, and code review rarely catches it
A reproducible write-up of the runCatching CancellationException bug: the test that proves it, the shapes it hides in, and what each fix costs you.
A 14-day prep plan for a senior iOS or Android interview
Two weeks is enough if you spend them on the one gap that would cost you the point, not on reading more answers.