For any manager, the way to succeed at Apple is to be seen to conspicuously innovate.
Good managers tap into the talents of those who report to them so that the whole team is seen to succeed and innovate.
Managers get substantial authority – it's very top-down – so if you get a good manager, things will work well for you. If you are considering a position at Apple, learn as much as possible about the managers you will report to, as they will make or break your experience.
The hypothetical "good" managers referred to in the Pros section are uncommon. Much more common is the sort of manager who feels insecure and considers his/her reports to be competitors, and prevents them from contributing effectively.
Such managers feel under pressure to provide all the innovation themselves and actively suppress anything from below. Of course, that won't stop them from giving their reports negative performance reviews for failing to innovate.
If you get this sort of manager, you will find you have no voice.
If you are considering a position at Apple, learn as much as you can about your potential managers and try to find out which sort they are.
Rate managers by their ability to harness the talents of their reports, not by their own personal innovation.
Permit engineers a voice.
The company is spending a lot of money on talent - stop wasting it.
The interview process was fairly standard, consisting of one full day of interviews, plus lunch with a team member. I met with most of the team members, as well as the manager and director. The questions spanned across both experience and technical
It was very intense. I sat with a variety of people on the team and interviewed all day, encountering different personalities and different perspectives of the job. This was a very good tactic to find out what the person is all about. They learned a
An engineer contacted me based on my technical blog. I had a phone interview, then was flown out for a full interview. It was a pretty intense interview (I've been through an MS interview, too). There were lots of people, and the interview was very
The interview process was fairly standard, consisting of one full day of interviews, plus lunch with a team member. I met with most of the team members, as well as the manager and director. The questions spanned across both experience and technical
It was very intense. I sat with a variety of people on the team and interviewed all day, encountering different personalities and different perspectives of the job. This was a very good tactic to find out what the person is all about. They learned a
An engineer contacted me based on my technical blog. I had a phone interview, then was flown out for a full interview. It was a pretty intense interview (I've been through an MS interview, too). There were lots of people, and the interview was very