Career path
Pass interviews
Turn real iOS knowledge into answers interviewers can reward.
Swift, SwiftUI, concurrency, architecture, mobile system design, live coding and behavioural 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.
- 1
Audit the topics that can cost you points: Swift, ARC, concurrency, SwiftUI, architecture, system design, testing and behavioural.
- 2
Use answer cards to compress each topic into wording you can say out loud.
- 3
Practise follow-ups before the interviewer asks them.
- 4
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 behavioural 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.
7 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.
7 min read
Engineering Interviews
iOS coding interview: what the live round 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.
10 min read
Engineering Interviews
Kotlin coroutines interview questions that 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.
9 min read
Engineering Interviews
The STAR method for senior mobile engineers: what the interviewer scores after the R
Every senior mobile candidate knows STAR. Most still give answers that cannot be scored, because the situation is long, the action is "we" and the result is "it shipped". A weak and a senior answer to the same migration story, the follow-ups that come next, and the "we" versus "I" trap, from the hiring side.
11 min read
Engineering Interviews
Merge intervals in a mobile coding interview: the calendar version
Merge intervals is the algorithm question that keeps arriving dressed as a calendar. A worked answer from the hiring side: what to ask first, the brute force, the insight, the code in Swift and Kotlin, and the follow-ups that separate levels.
12 min read
Engineering Interviews
Tell me about a production incident you owned: the senior mobile answer, scored
"Tell me about the worst bug you shipped" is scored on what you did between the first signal and the last change, on a platform where you cannot take a binary back. The structure, the follow-ups and the recovery lines, from the hiring side.
14 min read
Engineering Interviews
Tech lead interview questions: what each one scores, from the hiring side
Most lists of tech lead interview questions stop at the question. The loop does not. Eleven questions a tech lead round asks, what each one is scoring, the weak answer and the strong one side by side, and the follow-up that checks whether the strong one was yours.
20 min read
Engineering Interviews
Tell me about a time you influenced a decision without authority: the senior and staff answer, scored
"Tell me about a time you influenced a decision without authority" is scored on whether you found the decision under the problem, moved it before the room and kept it closed afterwards. Persuasion is the smaller part. The structure, the follow-ups and the recovery lines, from the hiring side.
14 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 judgement 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.
6 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.
7 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.
5 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.
8 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 judgement appears where JavaScript, native work and product constraints meet.
7 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.
3 min read
Mobile system design
A UIKit scene migration can launch and still lose its first link
The migrated app opens from its icon and handles links while it runs. Then a link arrives while the process is stopped and the app shows its home screen. The cause is one omitted line, and the test that catches it.
5 min read
Mobile system design
AGP 9 changed a default. Release unit tests stopped running.
The AGP 9 migration looked finished when Gradle help succeeded. Then the verification command asked for testReleaseUnitTest and Gradle could not find it. A small fixture shows the setting behind it and what to verify.
5 min read
Mobile system design
Target SDK 37 changes what a successful network check proves
On Android 17, an app targeting API 37 can reach the cloud while every local socket fails. A seven-scenario test separates app guards from OS enforcement and shows what each result proves.
6 min read
Engineering Interviews
The senior engineer who never asked a single question
What a simple coding exercise showed me about assumptions, speed and engineering judgement.
5 min read
