Re:My experience of interviewing for a job at Apple
by foobarqux on Tuesday February 24, 2015 @10:53PM
(#9105195)
I have never been able to distinguish whether the subtext is "I hated my job and left as soon as I got the chance" with "I loved my job and only left because I got something even better".
Re:My experience of interviewing for a job at Apple
by sukilot on Wednesday February 25, 2015 @01:51AM
(#9105611)
Often, one of those is true on Tuesday and the other on Thursday. Our emotional connection to our experiences is dynamic and inconsistent.
Re:My experience of interviewing for a job at Apple
by jsmthrowaway on Tuesday February 24, 2015 @10:57PM
(#9105210)
I would be lying to your face if I told you that Apple didn't have its negatives, sometimes severe ones. All jobs do. But hate? No.
Re:My experience of interviewing for a job at Apple
by nickbauman on Tuesday February 24, 2015 @11:01PM
(#9105214)
Great answer. Could Steve Jobs himself succeed at a company like Apple as an employee? I doubt it. But that is the question.
Re:My experience of interviewing for a job at Apple
by vinceguidry on Tuesday February 24, 2015 @11:07PM
(#9105235)
Jobs could not have succeeded as an employee anywhere. It's just the way he was wired.
Re:My experience of interviewing for a job at Apple
by scriptproof on Wednesday February 25, 2015 @07:34AM
(#9106405)
They created at Atari a night shift just for him (he was the only employe of this team) to do the same work than the others. This answers the question.
Re:My experience of interviewing for a job at Apple
by vanessa98 on Thursday February 26, 2015 @02:32PM
(#9114806)
Yikes! Don't fall into the title driven career path. Titles are a false currency and a company accreditation that is of non-transferrable value outside that company, for the most part.
Re:My experience of interviewing for a job at Apple
by sparaker on Wednesday February 25, 2015 @01:52AM
(#9105613)
I am the kind of person who likes to work with small but effective teams. I like people who are willing to go the extra mile to build something cool and advanced. Although i haven't been to Google, Apple, etc but i think these companies do not leave enough room for people to explore new cool technologies to work in, which is pretty much all you do in startups.
So i'll always go with a smaller and effective team than being part of a very big company where my role is more or less insignificant.
There's no shortage of folklore about Jobs hand-picking teams, as I'm sure you know, and moving around at Apple is very social by its nature. You have to make a conscious effort to end up in a position where you get an opportunity to build Swift, or iPhone (I mean building it, not keeping it going; vast numbers of people keep it going now), or Apple Watch unless you're hired into an essential role for something like that. Most people at Apple are doing the same things you and I do: upgrading Cassandra, diagnosing some OS bug that only appears on certain phones and carriers, localizing a piece of iTunes. So it becomes a question of how much you're willing to invest to earn your place at Federighi's side on stage, launching your passion that will change the world. For some, that equation breaks the right way. For me, I need more immediate feedback. Make sense? More me than them.
My time in the peninsula taught me that I value small, scrappy teams more, and that I'm not cut out for Facebook, Google, Apple, and friends. For that very same reason, I'm not the best person to ask on whether you should work for Apple or Google: some people thrive very well in large-scale corporate organizations but it isn't for me. In general, I'd wager a new grad should do a peninsula tour before getting into the risk game up 101, but I think that's a very myopic view, if I'm honest.