The first stage was a telephone call with one of the internal recruiters.

This was followed by a CV review with an engineering manager. That call was a very good chance to learn more about the projects going on, team structures, and generally about what they'd want from you as a member. It was also a chance to review your own career path and how you've worked in previous roles.

My personal last stage (as I seemed to fail it) was a 1-hour code pairing exercise in CoderPad. The task was very interesting in its simplicity and scope for extending. I never thought that such a short task could reveal so much, but I found it to be very smartly created!

A word of advice here (and my failure): they do seem to review the code from CoderPad outside of the interview. Which I thought was a huge error on their part. Based on that, even after having worked in Swift since almost the start of the language, they proposed I'd go for lower seniority roles. From experience (and even their intro to the session), I was under the impression that problem-solving and communication skills were the focus, as well as knowledge and application of best processes, not that they would expect your code there to be submitted for code review. You'd probably work under less pressure when preparing to submit something for a real code review.

I was quite disappointed at the logic behind their decision, but it was still probably the most detailed feedback I've received in an interview. So, overall, it was a good experience as I also learned from it (I can't be surprised enough at the task from the pair-programming exercise; very, very nicely planned).

Standard work practice and experience-related questions.