Interview tips
Habits that make technical answers land, in phone screens and on-sites. The free handbook applies them to 537 questions.
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 an awkward silence.
trade-offs
Name alternatives before you pick one
For architecture or API questions, briefly mention the options (MVVM or a coordinator, async/await or Combine), then justify your choice for the scenario.
debugging story
Prepare one Instruments or crash story
Be ready to walk through how you found a retain cycle, a memory spike or a main-thread block: the tool names and what you changed.
honesty
“I haven’t shipped that, but here’s how I’d learn it”
Strong candidates admit gaps and outline a concrete plan: docs, a spike, code review. Avoid bluffing on platform fundamentals.
ai code
When they show you code, review it out loud
More interviews now hand you a snippet, often AI-written, and ask what’s wrong. Say what each line does, where it runs and what happens when it fails, before you suggest a fix. The course teaches a 60-second review pass for exactly this.
Crashes on the first unexpected response. Throw, or handle the error and show a state the user can act on.
Comments cite rules from the Good Code or Slop? checklist, part of the video course.