I may have described the interview procedure in too much detail because I received no feedback after the first stage.
This stage was a pair programming coding exercise. The problem was fairly easy, nothing horrific. The only issue was that the allotted time was not enough to finish the test using proper TDD. I was told that this was expected, so you need to hurry to fit everything into the given timeframe. However, I suppose that's part of the process.
It was supposed to be a pair programming session, but the interviewer did not pay any attention. He was working on another screen and did not listen to what I was doing or why. I asked if I could speak out loud and explain my actions. The response was: "I don't mind; whatever works best for you." He wasn't interested in the interview at all, and this was the point when I realized I stood no chance of progressing.
When my time elapsed, he asked what I had accomplished. He gave me two minutes to explain and then said we had no more time.
This was a very negative experience with a company that is likely the leading tech innovator in the world. One expects a lot more from such an organization, and a more engaged interviewer, showing some interest, should have been normal.
Nothing that I am allowed to disclose.
The following metrics were computed from 1 interview experience for the Apple Senior Software Engineer - Java role in London, United Kingdom.
Apple's interview process for their Senior Software Engineer - Java roles in London, the United Kingdom is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Apple's Senior Software Engineer - Java interview process in London, United Kingdom.