Interview process was pretty thorough and took about a month from initial application to job offer. All of the interviews were one on one (no panel interviews.) There was one take home coding project, review of which, was then the subject for the next interview. Capstone interview was with the CEO (smart guy, very enjoyable.)

Recruiter screen, technical discussion with engineering manager, take home assessment, review of take home assessment with engineers. Every step up to the assessment review stage was pleasant. At the assessment review, you will deal with very opinionated engineers, who basically expect a solution that would be ready to deploy to the cloud in that instant. This is an unreasonable expectation for a candidate, instead, the focus should be on whether the candidate can code with best practices. Be prepared to argue for all of your architectural decisions at this stage, and for extreme push back if the interviewers think their view point is the correct one. When my interviewer began to argue that my implementation would be susceptible to sql injection attacks, I had to explain to him how postgresql defends against this with the usage of $ arguments. If an interviewer is extremely nit-picky at this stage, it is obvious the job would be no better. I withdrew my candidacy after this.