Working for Apple is best if you like having a peer group to learn from and grow with. You get out of Apple what you put in. You really can't be a "super rock star to it alone" type, since the process of creating a product requires many hundreds of people.
An individual can come up with and promote their own idea, and then see a support group grow around it if the executive team decides to productize it. This is quite different from other companies where individual contributions are not respected nor desired. Apple lets you be creative and rewards that.
The biggest downside to working at Apple has to be the overcrowding on the main campus. They're building another campus, and they've leased a bunch more space, but new hires are starting to double up, and the on-site cafeteria has become a madhouse.
Apple no longer has a sabbatical program, which is something I'd hope they bring back in the future. With the economy being the way it is, Apple holds the cards as far as compensation, but I really have no complaints. They recently improved the coffee situation too.
I wish they had a better employee purchase program.
I would tell senior management that they need to rein in the number of parallel projects. All groups seem to be working at full steam all the time, without a chance to realign and redesign things that are getting old. It would be a good idea for Apple to fund more basic research. All that being said, Apple makes amazing products, and it's an honor to be a part of this company.
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.