I’ve sat through a lot of interviews with other major tech companies and have never really had an interview like this, where I felt my skills weren’t tested fairly, while also leaving me with a rather negative impression.
The interviewer overwhelmed me with code right off the bat – 400 lines were pasted in for the question. The interviewer initially told me to ignore the incredible amount of code, but my code was failing due to that same code. I was forced to try and understand and read this code under time pressure to discover a requirement that was not provided upfront. In other words, the interviewer instructed me to ignore a resource I actually needed to solve the problem.
It seemed like one of those "gotcha" moments that interviewers use to see if candidates can figure out the issue, hoping they have some magic intuition, while also using CoderPad, making it impossible to easily search the code.
It’s also the first tech screen I’ve ever had that was 30 minutes long, whereas all the ones I’ve done in the past have been at least 45 minutes. When I asked the interviewer about this, he mentioned that he only needed this much time to evaluate my skills. This doesn't really take into consideration what the candidate needs to demonstrate their skills.
Implement a compound iterator in Java.
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.