I applied to a job posted on LinkedIn. The recruiter asked for a phone screen the very next day. The phone screen with the hiring manager went very well, with mostly general background questions. I was then called in for an onsite interview. I freed up my whole week for Apple!
However, the onsite interview was cancelled, and the recruiter asked for details for the following week.
No worries; anything for Apple! The onsite was scheduled a week after the first one. I was at Apple! The interview lasted for a few hours, and four people interviewed me. It was not overly technical – nothing like writing a script or code. It was mostly about branching strategies and other general SCM questions. I was very happy and confident I would be called in for the second round.
In hindsight, there was a reason the interview was so simple: they had already decided they were not going to hire me. After a few unreplied emails from the recruiter, I finally called, and she said they had decided to hire an internal candidate.
Every single one asked this question: Why Apple?
The following metrics were computed from 1 interview experience for the Apple GPU Build Engineer role in Cupertino, California.
Apple's interview process for their GPU Build Engineer roles in Cupertino, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Apple's GPU Build Engineer interview process in Cupertino, California.