Interview process starts with a basic homework assignment that takes less than an hour to complete. There's no brain teaser or overly complex functionality to implement so it's mainly just a screening technique. Afterwards, they'll schedule you for a 1 hour phone interview with one of their engineers. They'll quiz you on your knowledge of whatever programming language is relevant to the position you're applying for as well as asking a little bit about your experience with software development processes. All the questions they ask here are pretty reasonable. Next is the onsite interview where they do a deep dive into your technical knowledge and experience as well as some pair programming. The technical deep dive is where things can become difficult as the majority of the questions they ask are based off of previous projects you've worked on including ones from several years back. This segment is just talking so there is no coding or white boarding at all. The interviewers really push for as many details as possible about everything you mention so make sure that you that you drive the interview and only bring up topics that you're comfortable speaking about in extravagant detail. Unfortunately, I made the mistake of speaking to broadly about my experience and the interviewers kept pushing for details on topics that were either too far in the past for me to speak about in detail or were not really my preferred topics of discussion. Most of the questions they ask are based on what they read off your resume so make sure you review what you've written on there and possibly tailor it to only include items that you want to talk about.

They do a 30 minute call and then quickly give you take home assignment that takes around 8 hours to do, however after that, they never tell you yes or no. After a week, the recruiter contacted them and they said they were too busy to look at it.