There were 3 interviews in total.
The first was a screening call with the recruiter. They briefly asked about my interest in the position, what I knew about it, and what questions to expect in the interview with the engineer.
The second was with the project lead and lasted an hour. He asked me to talk about myself, and then, based on that, he dug into my past work experience and projects. He then asked a couple of technical questions about firmware and my knowledge of it. It was very chill and surface-level.
The last interview was 6 hours long with 6 different engineers – the whole team. Each one took 45 minutes. The questions were very technical and involved. They would put you in real scenarios and see how you solved problems, complicating the scenario as you answered. You should be ready for analyzing systems, identifying pain points and troubleshooting, writing some code, and answering behavioral questions. Some of the engineers were nice and would give feedback as you went, while others were very poker-faced, making it difficult to know if I was doing well.
Identify use cases. Write Python code. Troubleshoot a system. Design a system.
The following metrics were computed from 1 interview experience for the Apple Firmware Engineer role in San Diego, California.
Apple's interview process for their Firmware Engineer roles in San Diego, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Apple's Firmware Engineer interview process in San Diego, California.