I was told to schedule an on-site interview after the initial coding task they gave me.
It took three attempts to schedule this day of interviews with the recruiter, spread over two weeks. I had to repeatedly free my schedule for the day, only to find out I had done so for nothing because yet another one of the engineers who were going to interview me decided they were busy that day.
But worry not; the day of my interview did finally come.
I was there at 11:00 and left at 18:00. At lunch, I was rushed into a group that went out to get food, and I had to buy my own lunch. (Am I entitled to hope for at least my lunch being subsidized when others get flown across the Atlantic and receive accommodation for several days during their interviews?)
As the interviews way overran, I left at a staggering 18:30. I happily went home because, at least, the people I had the chance to talk to were nice to me and seemed happy with my responses.
Anyway, I had to wait another 39 days for my result, which was a rejection. Thirty-nine days.
I only encountered whiteboard coding in my 5th interview, which was already at 5 in the afternoon.
It was a medium-difficulty exercise, nothing to worry about if you've interviewed for other big companies before.
However, I was quite disappointed to see that for a Software Developer position, four interviews solely consisted of behavioral questions.
The following metrics were computed from 3 interview experiences for the Apple Software Engineer role in Cambridge, United Kingdom.
Apple's interview process for their Software Engineer roles in Cambridge, the United Kingdom is incredibly easy as the vast majority of engineers get an offer after going through it.
Candidates reported having mixed feelings for Apple's Software Engineer interview process in Cambridge, United Kingdom.