|
For the people working there, talking about it on a public forum is cause enough to get fired, and hiding behind an online alias is not going to give you enough protection. Apple is full of really smart people, who like their jobs well enough not to risk losing them so casually and for such little incentive. As for the process of interviewing: for a lot of the more interesting jobs at Apple, interviewing involves signing an NDA. Hence, whether or not they end up getting hired, they’re contractually prevented from talking about the interview process. Having worked there in the past myself but not anymore, I can speak only _somewhat_ freely about it all. The interview process can be intense, taking up to several weeks and with a minimum of 4 interviews, but usually 7 or 8. Often, for practicality reasons (travel to Cupertino), all those interviews are done in a single day, and if it's more than 8 it'll be done across two+ days. As for the specifics of an average interview itself, I can’t really say anything. And as for working there, my own experience was largely fantastic, but it wasn't for me in the end. Apple's campus is by far the nicest I've seen of all the major companies (and I've seen all the ones in Silicon Valley), and though there is always a constant pressure, stress and a major (and insane) deadline to make, working there is incredibly satisfying. Unless, perhaps, you're at MobileMe. But maybe that was just me. |
The thing to remember about Apple is: it's really big. The interview process for an engineer working on Mac OS X could be completely different from that for an engineer working on iPhoto vs a product manager working on the iTunes store vs a finance person vs a supply chain person (et cetera). Generalizing is hard, and probably wrong.
Generally, we did a couple of rounds of phone screens, and brought someone in if we were convinced they had enough technical savvy. Once they were on campus, we'd evaluate competence (do they know what they're doing?) and personality/fit (can we work with this person?).
Given that our team was a bunch of generalists, we'd ask you about everything from pointers to dialog box design to HTML to database administration to shell scripting. We'd expect you to know a little bit about everything and be an expert on one or two things.