I first had an initial phone call with the team manager. We talked about general embedded concepts, semaphores, mutexes, and my Real-Time OS experience. It was a pleasant conversation overall. He advised me to refresh basic C concepts for the in-person interview.
The in-person interview was a rushed experience. There was no overview of the number of interviewers, and the first person just dove in and started asking questions. It was difficult to understand many of the interviewers. The next interviewer would come in, interrupt the current question, and then just start the next problem.
There was no sense of personality fit for the group. It basically felt like I could have been at home programming while they watched. I'm not sure why they had a face-to-face interview since they just wanted to look at my code.
Create a bitmask that takes a width and position as input.
Reverse the elements in an array.
Eliminate duplicates from an array.
Solve the cashiers make change problem.
Create an interpolation function.
Convert a string to an integer value.
The following metrics were computed from 2 interview experiences for the Apple Firmware Engineer role in Santa Clara, California.
Apple's interview process for their Firmware Engineer roles in Santa Clara, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Apple's Firmware Engineer interview process in Santa Clara, California.