It's great to work on products with outstanding recognition. Everybody believes in the product to a good extent and engineers' ability to provide input on many aspects of a product, even if it's not their area of expertise (such as user interface, process, and general quality).
There is little bureaucracy and politics for a company of its size. I've worked for companies many times smaller with far more politics, which creates inefficiencies through needless intracompany competitiveness and lack of communication. This is less so at Apple due to three reasons:
I like the people a lot here. They are very smart and pretty humble. There is not much individual arrogance, which makes it a comfortable place to be (although there is a fair amount of arrogance on the products). Good focus on products.
The focus on products (and profits) means it's unlikely for Apple to stray into new territory or experiment with something that doesn't have a clear path for profitability. There will never be a policy at Apple which allows engineers to spend 20% of their time working on some experimental project like Google or other companies have.
There is some arrogance on the products where engineers believe what they have done is THE right way to do it, despite users having valid complaints about it.
Apple is pretty cheap. It's difficult to get managers to spend money or invest unless there is a clear path for profitability as the result of the investment (this includes training such as books and conferences). That's one of the reasons it has $46 billion in the bank.
Also, as a result of the company's frugality, Apple hasn't really shared its success with employees who have worked very hard to get it there. There is job stability in a poor economy, but there is no profit sharing or increase in bonuses as a result of record revenues and profitability. Not even the products are given to employees or discounted very highly.
Share some of the company's success with employees who have worked very hard to get the company where it is.
Lots of questions that looked like they belonged in a lower-division CS final.
I re-contacted an Apple recruiter who had contacted me in the past because I was looking for new opportunities. After sorting out the location, I had two phone interviews. The questions were quite basic C++ and algorithm questions. After those two i
This was probably one of the best and fastest-moving interviews I've done. Everyone I met with was tack sharp, and the questions were relevant and fun. These included questions about my research background, as well as a few whiteboard coding proble
Lots of questions that looked like they belonged in a lower-division CS final.
I re-contacted an Apple recruiter who had contacted me in the past because I was looking for new opportunities. After sorting out the location, I had two phone interviews. The questions were quite basic C++ and algorithm questions. After those two i
This was probably one of the best and fastest-moving interviews I've done. Everyone I met with was tack sharp, and the questions were relevant and fun. These included questions about my research background, as well as a few whiteboard coding proble