The interview process was pretty standard. Two phone screens (standard and coding), an on-site with one algorithms question, one architecture question, and a couple of get-to-know-you and get-to-know-us kind of sessions. The only unusual part was the project. The project, without giving too much away, is an exercise where you are given three hours on-site to write a simple webapp that you will then present to a panel. This is outlined below. Personally, I would have preferred the project as a homework rather than on-site, but I do recognize that this would be a huge turn-off for some candidates. Also, there could have been more preparatory instruction given (make an entire skeleton project that you can immediately start adding models/views to). Outside of that, it was pretty straightforward. I had a friend who was interviewing at the same time, but was unnerved by the project. Don't be; it's actually pretty chill, all things considered. In the end, the interview process itself was nothing all that special or unusual (other than the project), but that's good. It did exactly what it's supposed to; helped me evaluate the company, and helped the company evaluate me. Overall, it was a good fit, and I'm happy with that.