You get a chance to innovate, making a difference. The tech industry desperately needs someone to show how you can truly innovate in a way that people get, and Apple does that.
Benefits are acceptable, but not great. But really, I'm in this job because I like what I do, not because of the compensation. Lately, that hasn't been an issue, though, because of the way AAPL has rallied.
Other than the innovative part, I like the mentality of people at Apple. People in general are open to new ideas, and if you push for it, you can realize your dreams here.
People are working very long hours at Apple, especially on crucial projects where delays are simply not acceptable. It's a job to live for, and if you're not willing to do that, you're probably not going to have a great time at Apple.
Raising a family while working at Apple is a hard thing, and I'd recommend anyone thinking about it to either have a partner that is not working or get some help taking care of your kids.
Also, the compensation isn't great. The AAPL rally lately has compensated for that, but that won't last forever. Apple management knows they can get away with paying lower salaries because of the hype surrounding the company.
Be even more open to new ideas. There are a lot of people at Apple with great ideas, and not all of them get a chance to be heard.
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.