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 in regards to team fit and communication, of which are great questions to ask for more senior roles. After, I had an interview with a staff engineer and went over pretty basic OOP, CS, and iOS questions. This is mostly to uncover the breadth of knowledge you may have on the platform. Afterwards, I was invited to do a takehome exercise.
The process overall went well, however my main gripe was getting 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 really get a chance to explain the decisions I made in an exercise that was supposed to be time-boxed to 3-4 hours. Unfortunately, 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 where it doesn't break confidentiality of the exercise itself.
