You go through a few interviews with them:

• First, with the hiring manager.
• Then, an engineer of the same level you're applying for.
• Then, a coding exercise.

The hiring manager asked me several questions regarding team fit and communication, which are great questions for more senior roles.

Afterwards, I had an interview with a staff engineer. We went over pretty basic OOP, CS, and iOS questions. This is mostly to uncover the breadth of your knowledge on the platform.

Afterwards, I was invited to do a take-home exercise.

The process overall went well. However, my main gripe was receiving a rejection letter with no real feedback.

Unfortunately, they do not send feedback regarding the coding exercise due to confidentiality reasons, which I understand. However, it seems like I didn't even get a chance to explain the decisions I made in an exercise that was supposed to be time-boxed to 3-4 hours.

This experience really tarnished an otherwise stellar interview process, as everyone was quite responsive, amicable, and eager to talk.

As part of feedback for the interview process, while specifics aren't necessary, it would be nice to receive high-level feedback on what the issues were that ultimately led to a rejection. I believe there are ways to return feedback that is abstracted enough to not break the confidentiality of the exercise itself.

Standard OOP, CS, and iOS platform questions.