For projects that Apple upper management has its eyes on, quality is given high priority. Teams on those projects are also often very good, with smart and experienced people with whom it's fun to work and from whom one can learn a lot.
It's a big place, and there are sometimes inefficiencies due to the number of people involved with a project. There is a significant amount of politics involved with promotions and a significant amount of empire-building, with teams growing unnecessarily to bolster team management's prestige.
Projects that are not visible to upper management suffer from quality problems typical of any organization, but everyone is very confident about the superiority of their work regardless of their actual performance and the actual quality of what they produce. Arrogance is rampant and encouraged by management and the corporate culture.
Things are going very well, so there's not much advice to give.
More needs to be done to differentiate quality work from other work within the company, even when the overall product of the work at the company is deemed to be good. Otherwise, over time, the company's results will not be so good.
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.