Overall, a terrible experience.
I was mis-scheduled for back-to-back interviews in a different time zone than the interviewer, all by the same coordinator.
When I inquired about interviewing for a certain level, I was told it "was a stretch." This was despite having secured interviews for the same level at F, G, the other A, and U, all of which are considered more senior according to levels.fyi.
For the phone interview, I was asked two easy LeetCode questions. While solving the first question, the interviewer could not be convinced that I had the optimal solution, despite prolonged discussions about the runtime and space complexity. They instead proposed a solution that had the same runtime but used more space.
The discussion eventually led to an attitude on the interviewer's side of, "Hey, let's just move on."
(I double-checked the question on LeetCode after the interview to ensure I hadn't missed anything. I was indeed correct about the runtime and space complexity of the approaches considered.)
Do you know how to calculate runtime and space complexity?
The following metrics were computed from 26 interview experiences for the Apple Software Engineer role in New York, New York.
Apple's interview process for their Software Engineer roles in New York, New York is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Apple's Software Engineer interview process in New York, New York.