Career path
Pass interviews
Turn real iOS knowledge into answers interviewers can reward.
Swift, SwiftUI, concurrency, architecture, mobile system design, live coding and behavioral answer systems.
iOS developers preparing for mid, senior, lead, staff or architect interviews under pressure.
Are you on this path?
Signs you are here
- You know the topic, but your spoken answer comes out scattered.
- You pass early rounds and stall at onsite or system design.
- Interviewers push on trade-offs and you lose the thread.
- You are answering one level below the role you want.
The interview path is built for pressure.
When the interview is close, you do not need another broad tutorial. You need high-frequency topics, senior wording, traps, follow-ups and a way to recover when pushed.
- 01
Audit the topics that can cost you points: Swift, ARC, concurrency, SwiftUI, architecture, system design, testing and behavioral.
- 02
Use answer cards to compress each topic into wording you can actually say out loud.
- 03
Practice follow-ups before the interviewer asks them.
- 04
Use the Blueprint for deep prep, then the 24-hour Answer Book for final rehearsal.
Books for this path
iOS developers preparing for mid, senior, lead, staff or architect interviews under pressure. Swift, SwiftUI, concurrency, architecture, mobile system design, live coding and behavioral answer systems. Every book here is written from the hiring side, from 500+ technical interviews, and each book page shows what is inside and who it is for.
Free resources
Free checklists, cards and templates for the pass interviews path. Each one is short enough to use on the problem you have this week, and each works on its own, before or without a book.
answer-card
Senior iOS interview answer card
A speakable answer format for senior iOS questions: the first sentence, the production answer, the trap, the pushback and the recovery line.
checklist
Swift concurrency interview checklist
A senior-level Swift concurrency audit for cancellation, task ownership, actor reentrancy, MainActor boundaries, Sendable and flaky async tests.
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.
checklist
Kotlin coroutines and Flow interview checklist
A senior Android checklist for coroutine ownership, structured concurrency, cancellation, Flow collection, state sharing and deterministic tests.
checklist
Live coding evidence checklist
A rehearsal card for the evidence interviewers can record while you frame, build, verify and recover during a shared-screen round.
answer-card
Senior SDET decision card
A scenario card for answering senior SDET questions through risk, evidence, investigation cost and operational ownership.
Writing for this path
Engineering Interviews
Senior Android interview questions: the 5 follow-ups that decide the loop
Your first answer rarely decides a senior Android interview. The follow-up does. Five follow-ups, the answer that loses the point, the one that earns it, and what to say when you wobble.
6 min read
Engineering Interviews
Senior iOS interview questions: the 5 follow-ups that decide the loop
Your first answer rarely decides a senior iOS interview. The follow-up does. Five follow-ups, the answer that loses the point, the one that earns it, and what to say when you wobble.
6 min read
Engineering Interviews
iOS coding interview: what the live round actually tests
The iOS coding interview is rarely a puzzle. It is a small app task under a clock, and the score comes from how you build it, not whether it compiles on the first try. The five common tasks, what gets scored in each, and what to say when it breaks.
6 min read
Engineering Interviews
Kotlin coroutines interview questions senior Android loops ask
Ten coroutines and Flow questions senior Android loops ask, what each one tests, the follow-up that decides the score, and four short bugs worth practising until you can fix them out loud.
7 min read
Engineering Interviews
Reading the answer is not the same as giving it.
Most interview preparation stops at recognition. Loops score what you can produce once the question changes. Why I built Interview Runtime, and what it asks you to do.
4 min read
Engineering Interviews
You have 40 interview tabs open and still don't know what to study.
Interview preparation gets worse when everything looks important. The closer the interview gets, the more your calendar should force you to cut.
5 min read
Engineering Interviews
You watched the solution. Then you opened an empty editor.
Watching someone code can make you feel ready. Live coding exposes the gap between recognition, retrieval, and making your judgment visible under pressure.
6 min read
Engineering Interviews
AI can pass the assessment. You still have to survive the interview.
AI can produce a polished assessment. The harder part starts when a Senior engineer asks why the code exists and whether you own the decisions behind it.
5 min read
Interviews
A correct Android answer can still fail the interview
Two answers to the same Android question, both correct, scored completely differently. What senior loops are measuring once you clear the knowledge bar.
6 min read
Swift concurrency
Swift concurrency bugs that pass code review
Four Swift concurrency bugs that survive code review at good companies: actor reentrancy, leaked tasks, ignored cancellation, and the onAppear trap. With fixes.
7 min read
Interviewing
Senior iOS interviews are about risk
The strongest candidates do not just answer the question. They show how they think about production risk, tradeoffs and recovery.
3 min read
Swift concurrency
A modern Swift concurrency interview map
A senior interview map for async/await, actors, cancellation, task lifetime, Sendable and the bugs hidden around awaits.
6 min read
Interviews
What interviewers score while you share your screen
The code is only one part of a live round. The interviewer is also recording how you frame, choose, verify and recover while the screen is shared.
4 min read
Interviews
React Native interviews happen at the boundary
The framework answer is only the surface. Senior judgment appears where JavaScript, native work and product constraints meet.
4 min read
Interviews
Test automation is not the senior SDET answer
The tool is not the decision. Senior test engineering begins with what failure costs, what evidence is trustworthy and who owns the response.
2 min read
