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.
A couple of phone screens, one of which covered some Objective-C fundamentals. Spent a day doing on-site interviews. Initially, I had to give a prepared presentation about my background to all of the interviewers. The remainder of the day consisted
I had a quick chat with the Hiring Manager and was then invited for a full-day panel interview a few days later. The panel was friendly and asked relevant questions for the position (no LeetCode). I received the offer a few days after the interview
Multiple phone screens, then a full day on-site. Whiteboard coding and system design sessions were conducted with pairs of engineers, one of whom took the lead. The questions were fairly open-ended.
A couple of phone screens, one of which covered some Objective-C fundamentals. Spent a day doing on-site interviews. Initially, I had to give a prepared presentation about my background to all of the interviewers. The remainder of the day consisted
I had a quick chat with the Hiring Manager and was then invited for a full-day panel interview a few days later. The panel was friendly and asked relevant questions for the position (no LeetCode). I received the offer a few days after the interview
Multiple phone screens, then a full day on-site. Whiteboard coding and system design sessions were conducted with pairs of engineers, one of whom took the lead. The questions were fairly open-ended.