An interview with the hiring manager, then an hour-long coding interview with an engineer via Coderpad, solving a problem that has zero implications on how well I could handle the everyday work requirements of the job.
These kinds of interview processes need to be put to rest. No one at Apple got to know me or my work.
Why should I study Apple as a company and invest in joining it when Apple's hiring team is too lazy to actually invest time in vetting their candidates beyond obtuse technical challenges that foster nervous energy and stifle creativity?
Write the "random out of a hat" algorithm (that you could easily Google for understanding in your day-to-day) how they want, or you don't have a shot.
I have 9 years of experience with consumer products shipped and easily verifiable open-source contributions. Why are you measuring someone like me via a random LeetCode-style question as a pass/fail?
Be better, Apple.
Recursion based around an already implemented function, pretending it doesn't exist. This could involve doing your own sort or filter, for example.
The following metrics were computed from 595 interview experiences for the Apple Software Engineer role in United States.
Apple's interview process for their Software Engineer roles in the United States is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for Apple's Software Engineer interview process in United States.