All resources
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.
Use this in practice
Use this when you know the topic but your spoken answer comes out scattered. Fill one card per question, then rehearse it out loud until it sounds natural.
Fill the card in this order
- Question: write the exact wording you expect to hear, for example, What is the difference between weak and unowned?
- Short answer: one clean sentence you can say in the first five seconds. No history lesson, no wandering.
- Senior answer: add the lifetime rule, the failure mode, the production example and the tradeoff you would use in real code.
- Why they ask it: name the signal. For ARC questions, the signal is whether you understand ownership, object lifetime and crash risk.
- Common trap: write the answer that sounds confident but loses points. This becomes your warning label during rehearsal.
- Interviewer push: write the follow-up that would expose shallow knowledge.
- Recovery line: prepare the sentence you say if you overclaim, miss a caveat or need to narrow the answer.
- What earns the point: define the exact thing the interviewer should trust after hearing you.
Worked example
- Question: What is the difference between weak and unowned?
- Short answer: weak references become nil when the object is deallocated; unowned references assume the object still exists and will crash if that assumption is wrong.
- Senior answer: I use weak when the referenced object may disappear first, such as delegates or closure captures where the owner can be released independently. I use unowned only when the lifetime relationship is guaranteed by the design. In production I prefer weak unless I can prove the invariant, because an optional is easier to handle than a crash.
- Why they ask it: they are checking whether I reason from object lifetime, not from syntax or folklore.
- Common trap: saying unowned is basically weak but faster. That skips the crash behavior and makes the decision sound like a micro-optimization.
- Interviewer push: Would you ever use unowned in a closure capture list?
- Recovery line: I would use it only if the closure cannot outlive the object. If there is any async work, storage, retry, timer or escaping callback involved, I would default to weak and handle nil explicitly.
- What earns the point: lifetime reasoning, crash awareness and one realistic closure example.
Rehearsal rule
- Record the first attempt. If the opening sentence is longer than 12 seconds, rewrite it.
- Add one production caveat to every answer, such as app lifecycle, cancellation, memory, rollout or testability.
- For each topic, prepare one interviewer push. If you cannot answer the push, the card is not finished.
- Stop polishing when the answer sounds like something you would actually say in a live call.
Go deeper
The iOS Interview Blueprint
Turn iOS interview pressure into structured engineering judgment, from junior fundamentals to architect and leadership rounds.
The 24-Hour iOS Interview Answer Book
Review the highest-frequency senior iOS interview questions and rehearse answers, follow-ups 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.
