call(back)

Apple

Deeply team-specific loops with no standard script — the screen is half résumé interrogation, and the coding half favours “implement this class, then extend it” over puzzles, with a requirement added the moment the first version works. Optimal on the first pass, narration throughout, and the memory bound volunteered on anything involving “millions”.

Typical loop

  1. 1Recruiter screen — ask which shape the technical screen takes: algorithmic, practical/domain, or design
  2. 2Hiring-manager call: résumé deep-dive (baseline, instrument, confounder for every number), often with a coding question of its own
  3. 3Technical phone screen: 45–60 min on CoderPad over WebEx, roughly half résumé and half one problem; some are voice-only design
  4. 4A second technical screen is normal
  5. 5Onsite: four to six team-specific rounds — coding, design/OOD, résumé deep-dive, behavioural
  6. 6Cross-functional round with a partner team

Questions

Callback's practice questions and the LeetCode questions Apple has been asking, filtered together.

Asked on LeetCode

298 questions · all time