As an engineer, it feels great to make contributions that have a visible impact on Apple products. People love it or hate it, but they never ignore it. Even the negative user comments just show how much they expect from Apple. Engineering is well respected, and the thing I like most is that the rest of the engineers are very grounded and like to make an impact on a product level. In some other big tech-focused companies, engineers often end up building an entire new compiler in order to get done with their project. This seldom happens at Apple, and it is a good thing.
There is a lot of secrecy and silos in order to keep company information on a need-to-know basis and extremely confidential. This is a good thing from the perspective of PR and marketing, but sometimes it hinders learning, sharing, and effectively working on new things. It also has a tendency to foster a culture where more senior employees can effectively shut off newer employees.
Do not let the genie out of the bottle!
Even though Steve is no longer with the company, there is no other company that can create such damn good products with a fantastic management team.
There is still a lot to be done though. Trust your engineering employees more.
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.