The interview process was relatively straightforward: two phone screens followed by an on-site interview.
My main complaint with this whole process was the recruiter. His communication was essentially non-existent the entire time. I felt like I was recruiting myself.
After the on-site interview, I was supposed to hear back within one week. After not hearing back for almost two weeks, I emailed the recruiter for an update. Then, in an almost auto-reply fashion, I received a very generic rejection email. It felt like an auto-generated response, as if "Oh, I forgot to tell this candidate he was a no, let me send this email real quick, copy, paste, done." I felt like I was just another number.
I'm pretty sure if I had never emailed him for a status update, he would have never replied back to me. I was very, very disappointed with this unprofessional communication.
About previous roles, technical questions, and a very deep and very broad range of topics.
The following metrics were computed from 17 interview experiences for the Apple Engineer role in Cupertino, California.
Apple's interview process for their Engineer roles in Cupertino, California is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for Apple's Engineer interview process in Cupertino, California.