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.
Team-specific interview process. This team focused on OOP principles. The phone screen involved OOP with a bit of system design. The onsite included another OOP section and a peculiar tree/node question where the task was to serialize and deserializ
Honestly, pretty damn easy, lol. I'm going to try Google next. This was genuinely so simple, I'm amazed a FAANG company would do this. Just practice 300 LeetCode questions and you'll be set!
It was good, tough, and long. 1. Prescreen interview with overall questions to estimate my technology knowledge and experience. It took a 15-minute talk. 2. Test task: write a project. It took 2 hours. 3. Tech interview: 3 sessions, 1 hour each.
Team-specific interview process. This team focused on OOP principles. The phone screen involved OOP with a bit of system design. The onsite included another OOP section and a peculiar tree/node question where the task was to serialize and deserializ
Honestly, pretty damn easy, lol. I'm going to try Google next. This was genuinely so simple, I'm amazed a FAANG company would do this. Just practice 300 LeetCode questions and you'll be set!
It was good, tough, and long. 1. Prescreen interview with overall questions to estimate my technology knowledge and experience. It took a 15-minute talk. 2. Test task: write a project. It took 2 hours. 3. Tech interview: 3 sessions, 1 hour each.