-
Communication
Start with a one-sentence thesis
Answer the question directly first (“Key paths let you reference a property without calling it…”), then add detail. Interviewers use the first thirty seconds to calibrate your clarity.
-
Depth
Signal when you’re done — and invite follow-ups
End with “That’s the core; happy to go deeper on KVO, SwiftUI bindings, or performance.” It shows confidence and saves awkward silence.
-
Trade-offs
Name alternatives before you pick one
For architecture or API questions, briefly mention MVVM vs VIPER, or async/await vs Combine, then justify your choice for the scenario.
-
Debugging story
Prepare one Instruments / crash story
Be ready to walk through how you found a retain cycle, memory spike, or main-thread block — tool names and what you changed.
-
Honesty
“I haven’t shipped that, but here’s how I’d learn”
Strong candidates admit gaps and outline a concrete plan (docs, spike, code review). Avoid bluffing on platform fundamentals.
For hundreds of structured Q&A pairs, see The iOS Interview Handbook.