Ask HN: Why does no one talk about working or interviewing for Apple?

I interviewed with Apple last year, and I wasn't asked to sign an NDA. That said, I didn't actually see anything that would have required one.<p>I didn't apply to Apple - they found me. A year later, I'm still not sure how that happened, since I don't know anyone there. It could have been through a public talk about user experience that I gave (the position was for UX director of the Apple web site), it might have been through something I wrote, or it could have been as mundane as a LinkedIn search.<p>I went through a series of phone interviews in the usual ascending order. Everyone I spoke with was very sincere and conversational, there were no MS or Google-style "tests" to go through. We looked at work I'd done, I talked about my approach to UX, we got to know one another a bit.<p>Eventually, they flew me out to Cupertino (I live in NYC), and put me up at a nice hotel near the Apple campus. I spent a full day in an interview room, meeting various members of the team I would be working with, both above and below the position I was being considered for.<p>The only time we left the conference room where the interviews were happening was to take a stroll over to the cafe for lunch. I went with most of the team, and we talked about day to day life at Apple, what it's like working with tight security, the fancy Apple buses that take employees from SF and the East Bay to work, people's personal projects and hobbies, etc.<p>I got some insight into the way Apple works, and predictably, there was none of the corporate silliness that you'd find in a less confident company, none of the buzzwords or process for the sake of process. I could see that they all worked incredibly hard, but the fulfillment on everyone's faces made me want very much to be a part of it.<p>In the end, I didn't get the job - they ended up either not filling the position at all, changing their team structure, I'm not sure - they left me feeling very good about myself and the experience, probably the best way that I've ever not gotten a job.<p>The main impression I was left with was that I had just wandered back to a pre-dot com era where people worked incredibly hard to make great things, rather than to maximize profits or burn towards an IPO or whatever. It was one of the most human job interviews I'd ever been through.

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.<p>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.<p>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.<p>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.

I interviewed for Apple earlier this month. I didn't get the position, but I really enjoyed the challenging interview process and meeting the 7 people who interviewed me.<p>I had a phone interview with a manager, and then a three-hour process at Apple HQ in which I was interviewed by three pairs of employees from the team I was applying to work with. I was very impressed that they devoted so much employee time to talking with me. They were very friendly people, and asked an interesting variety of questions, ranging from puzzles to how I'd handle various theoretical work scenarios to technical questions of various kinds.<p>The gent who recommended me told me that he had to apply six times before getting hired, so I'm planning to keep applying, for other positions.<p>There. Now someone has posted about interviewing at Apple. Happy? :)

There were 3 basic periods at Apple: the beginnings (aka Steve I), the Dark Ages (roughly '85-'97), and Steve Returns.<p>During the Dark Ages, Apple leaked internal information <i>badly</i>. One of the first things that Steve did upon return was try to clamp down (and fire people if necessary). He even had one of those WW-II posters "Loose lips sink ships" tacked up. And there is a certain truth to that. Competition has heated up (esp in the mobile space). Anyone and everyone would love to know what Apple is working on now, and what they will announce next month. Witness the kerkuffle with gawker over the iphone 4 engineering test device.<p>So people at Apple learn to say nothing, or move on down the road.

My first guess would be respect for the company. Secondarily, plenty of results in google reveal that the policy (if somewhat unofficially) is that you can say you work at Apple on your blog, etc, but not really blog /about/ Working At Apple. Even if there's no official policy on it, it's just better taste to say "The thoughts of John Doe" and not represent oneself as "John Doe of Apple."<p>"There's a PR department for that."<p>All that said, there are plenty of writers/bloggers who work at Apple. Randsinrepose.com is a personal favorite, and contains the writing work of Michael Lopp who may be an engineering manager at the fruit company. This policy of sorts goes much further back than iPhone/Android or any other blog-hyped non-competition.

The first rule of working at Apple - No one talks about Apple.

Probably because most of the people working there would like to keep their jobs.

I believe that they've got somewhat strictest policies on talking about internal stuff.<p>Well, at least that's what some bloggers write about [1] and I haven't heard about any counter-proofs.<p>[1] <a href="http://gizmodo.com/5427058/apple-gestapo-how-apple-hunts-down-leaks" rel="nofollow">http://gizmodo.com/5427058/apple-gestapo-how-apple-hunts-dow...</a>

This is a really interesting question, and got me thinking - maybe google's brutal interview process has a secondary purpose - to increase the allure of working at google?<p>This reminds me of a business case I read once about the difference between Mac Donalds and Burger King. That Mac Donalds uses a batch processing method that is faster but requires a higher skill level, whereas BK uses an assembly line, and that this affects their advertising. MacD's ads often double as recruiting ads, whereas BK tends to emphasize "have it your way" (easier to customize when you make burgers one at a time).<p>Maybe Google wants to interview more people than necessary, and subject them to an interview that leaves them thinking "man, you need to be at the top of your game to work there!" as a way of increasing the prestige of working there (and perhaps getting more top applicants?)<p>The thing is, I don't really see why this strategy would apply more to google than apple (unlike the MD vs BK thing...)<p>One thing is sure - devs are all aware of google's notorious interview process, but we (well, I should really just speak for myself, so I) never really hear these stories about apple.

When Glyph Lefkowitz (of the Twisted project) was hired, he posted unboxing pics of his job offer to his blog (which has since been closed down). He praised the usability of the letter.<p>Second-hand mention in: <a href="http://www.geek.com/articles/apple/unboxing-an-apple-job-offer-2009106/" rel="nofollow">http://www.geek.com/articles/apple/unboxing-an-apple-job-off...</a>

The man in the black turtleneck will find you if you talk

I worked at Apple EMEIA for a year and, truth be told, the interview process there depends.<p>It depends on where you want to work. If it's in Cupertino I'm told it's a completely different story to the EMEIA office. Having worked there, I can vouch for there really being a culture of absolute secrecy. It's quite common for one team to not know what's going on in the other corner of the room with another team. Secrecy has gotten even more prevalent in the EMEIA office (the office being made up of project managers alone, it was formerly less secretive than Apple World Wide/Cupertino) since the Gizmodo iPhone 4 affair. As regards fear related to Apple's security paranoia? It was moreover regarded as an irritation.<p>Going back to the interview process at Apple EMEIA (I can't say for Apple WW), it depends entirely upon who interviews you, which team, for what role, and what level. There is no set pattern. There may be an NDA for the interview process, there may not. It depends on the role and the person you are seeing. I know some who've had only two interviews, some who've had nine. It depends.

Whether it's intentional or coincidence, it's interesting how it parallels their products. There are approximately three people who work for Apple. They are the shiny, slick interface. Everything else is an implementation detail.<p>Jonathan Ive is like OS X. Nobody knows how OS X actually works, but they know the name and that it is why their screen shows such pretty things.

I interviewed for Apple a few months ago. I didn't get to the NDA signing part (I backed out because another opportunity came up during the process) but still wouldn't talk about the interviews I went through because I still hope to go back and try again someday (in the slim chance that our current venture doesn't work out).

There's folklore.org but that's like 25 years ago.

I blogged about my experiences both in Apple Retail, and in "corporate" Apple for a number of years. Eventually I took it all down, though not due to any pressure from the company. I took it down because I was inundated with emails from 15 year olds who wanted to know how to get a job in an AppleStore. But I worked for Apple for 6 years in Retail and AppleCare, and interfaced extensively with hardware engineering. I'm not sure I'd have anything interesting to say, but if you have any questions, I'll try my best to answer them.

The NDA comments across this thread are interesting, in the company I work for we NDA on just about every single external interaction. We're an IP black hole - anything you do using company resources (including sitting interviews) is considered our IP and is controlled as such.<p>We often get PHD students in to do research for us, and we compensate the hell out of them - because nothing they do ever leaves the walls. They sign a series of NDA and IP related contracts up front and don't get to use any external assets internally or vice versa.<p>The structure of the business itself is a mess of interwoven black box systems / IP and our own work, so it gets pretty aggressive / tight lipped whenever anyone is dealing with other people / companies, even internal branches.

NDA?

If you go to Apple, you might be surprised to find out that you've already agreed to some form of NDA with them. Especially, for example, if you're a part of any Apple Developer program. They might not always feel compelled to remind you of this, however.<p>I wouldn't know, though; I don't think I recall ever having been to Apple. No, not in a million years. I do find this Apple sweatshirt which I must've found at a thrift store to be especially comfy, however.

but i think the author's got a point, you never hear about any stalwarts of software dev defecting to apple, do you?

Regarding NDA's - Don't most companies sign some sort of an NDA with potential hires/ employees??Still, interview questions of most companies are available if you google well enough. But yeah, the difference is humongous- Apple doesnt seem to have the faintest thing similar to mini-microsoft :-)

i have a friend that works at apple, and other than providing a vague job description and saying they like it, they don't discuss details.<p>i think it's the culture, your work speaks for itself. he puts in long hours (on par with goog really) and has a great salary and perks.

The first rule of interviewing at apple is that you do not talk about interviewing at apple.

Sounds like a cult tbh - and I'm a mac fan.

It's simple.<p>If you want the job,<p>And you're smart,<p>You'll keep your goddamn mouth shut.

The first rule of Fight Club?

Fear is a man's best friend.

I interviewed at Apple for a product manager role. I have an MBA, and they were an on-campus recruiter. I interviewed on campus, then they called me to tell me I was going to have a 2nd round interview in Cupertino. 2 weeks later, I haven't heard anything and I am scheduled to be in Mountain View for a GOOG interview. I email them, telling them that I'd be happy to come in and save myself the time and them the travel expense...<p>They email me a week later (post my interview) and tell me "that should work..." They really have a crappy set of recruiters working there. Ultimately, I needed to accept another job (ended up being at AMZN), and Apple never actually got back to me. I've heard some similar stories about recruiter ineptitude there.

Remember the Oompa Loompas?<p>Same concept.

We all talk about how Megan Fox is hot, but then return to designing a descript schemantic intended to woo the girl next door.<p>And I dont mean to say that apple is out of one's league.

There's enough talk here about Apple, maybe not about working or interviewing there, but honestly there's just way too much talk about big companies on HN already; we don't need more.<p>What's the point of this meta thread anyway? Are you planning to work at Apple? If so, why don't you just ask specific direct questions about that?<p>Flagged for zero content.