The process took 2 days. I interviewed at Apple (Cupertino, CA) in Mar 2009
Interview
I was first contacted with a recruiter, who set up a phone screen with a hiring manager. The first phone screen was technical and covered mostly operating system concepts and a little bit on data structures. It went well, so I was told that the recruiter would schedule a second phone screen with another team member. The recruiter scheduled the second phone screen. This phone screen was also technical and not much different (a lot of questions about operating systems). This one was not with a manager. The recruiter contacted me two days later and said they were going to "pass on me." Both of the interviewers I talked were pleasant to talk to and seemed intelligent. The only downside was that the second interview seemed to be more about what I could remember from my operating systems class than my experience and real capabilities. I thought I had done well on the second interview and I thought interviewer's attitude backed that up; there is no feedback on your answers.
Interview questions [4]
Question 1
Have you ever written multithreaded code? Tell me about it..
The process took 1 week. I interviewed at Apple (Cupertino, CA) in Dec 2008
Interview
I interviewed with the hiring manager, then with several team members, two at a time. The final interview was with VPs, one after the other. I was not told beforehand that they would be VPs. Aside from the background check, this is the final step before an offer is authorised.
My potential co-workers all seemed very capable, there was no bottom 5% as far as I could see. I hear that laziness or time pressure is the most likely cause of screw-ups or people not wanting to do things thoroughly, rather than people not having the technical know-how.
Interview questions [1]
Question 1
Questions on background, coding exercised, how I would approach problems, how I would debug. all very typical.