I applied online and the recruiter contacted me a little afterward for a quick phone screen. I then had the technical phone screen the following week, which was surprisingly pretty manageable, a really basic question. The interviewer was actually very friendly during the process, and it felt more collaborative compared to some other companies I interviewed for. It seems like for this phase they want to know that you can actually code normally. I moved quickly to the onsite - three more coding interviews, all very friendly. They helped unblock me and point out some or my mistakes as I was typing, which I really appreciate. I definitely would not have gotten through the problems if they just watched me, like other companies do. They want to see how you can work through a problem, not if you can pass or fail the challenge. Something to note is that all interviewers come with problems that they come up with on their own, not from a pool of pre-approved questions, so it's pretty impossible to prepare for specific questions. Next was lunch with an engineering manager (delicious), and then architecture with a pair of interviewers. Don't be deterred by interviewing with a pair of engineers. It's actually better, in my opinion, because it lessens bias from one, single individual and helps you with balanced feedback, if, for example, the solo interviewer was having a bad day. Together we designed a calendar API. I then interviewed with another pair of engineers about my previous projects. Just a casual chat about what you've worked on, no whiteboarding whatsoever. It was pretty relaxed. They just want to get a sense of your general experience, didn't go into too much depth. Overall, a much more positive experience than other companies I've interviewed at. Much more personable in general. The interviewers generally want to help you and see you succeed, instead of just watching you with their arms folded.