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.

Phone screen with recruiter, interview with hiring manager, take-home code challenge, code review interview with senior devs, interview with manager's manager, interview with CEO. All steps were spaced out & offer was extended the same day as the interview with CEO. Everyone I met was genuinely friendly, communicated well, and overall it was a thrilling experience. I asked a lot of tough questions & got solid, specific answers about the values and culture. I rated the interview as difficult not because of the technical challenges, but due to the high level of integrity expected of the candidate. Don't answer with "the right answer", be honest! This was a fun interview process!