I was referred by an employee and had a phone chat with the manager. This was followed by a phone screen, then a day with five 45-minute onsite interviews, including lunch.
Each interview was two-on-one.
The process took three and a half months overall, but they assured me this was abnormally slow due to WWDC and a large team reorg.
Good questions, interesting people, and awesome discussions! I'd do it again just for fun!
A runtime has a struct Class { Class* super_class; struct { id_t method_name; void (method_pointer); } methods[]; }.
How would you optimize for dynamic dispatch?
How do you familiarize yourself with a new, large codebase? How would you go about replacing a component in it?
The following metrics were computed from 162 interview experiences for the Apple Software Engineer role in Cupertino, California.
Apple's interview process for their Software Engineer roles in Cupertino, California is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for Apple's Software Engineer interview process in Cupertino, California.