A recruiter caught up to me with three similar positions and set up a phone interview. An engineer from the team conducted a coding test over the phone. After passing that stage, I was called for an onsite interview. Three two-person panels and finally a single person conducted the interview. Except for the last person, everyone else jumped into whiteboard coding right away. Finally, the recruiter got back to me saying I wasn't selected to move forward in the position. Overall, the interviews were good and not too hard. However, the attitudes of the engineers on the interview panel were a bit weird. They would all come and sit with a poker face. After seeing the team, I wasn't too sure anyway if I would have joined that team or not.
Count bits set in a byte.
Write the code for a memory manager (init, get_memory, free_memory, etc.).
Given two sorted arrays, get the i-th element without sorting to a single array.
memcpy code with overlap protection.
Code optimization of existing code printed on paper.
The following metrics were computed from 12 interview experiences for the Apple Embedded Software Engineer role in Cupertino, California.
Apple's interview process for their Embedded 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 Embedded Software Engineer interview process in Cupertino, California.