There were several rounds to the interview process: - Phone screen - Code review interview (give feedback on a code sample with some flaws in it) - Schema design (how would you build something that fulfills this design, both frontend and backend)

- Intro call with recruiter - Half behavioral, half technical interview with hiring manager - Practical coding exercise with engineers - Technical onsite with ~3 interviews working some design mocks and discussing implementation and system design tradeoffs I'm of the opinion that hiring practices reflects what the organization prioritizes and I got good signal from this process. After I had my first call with the recruiter, I was quickly scheduled into the interview process based off of my deadline with clear communication from both the recruiter and recruiting coordinator. In between rounds and while waiting for final round feedback, timelines were also clearly communicated to me which I really appreciated. As for the technical interviews themselves, a clear standout is that the interviews seem to be designed intentionally to test for practical knowledge which I personally prefer, though it may be more difficult to study for compared to Leetcode. It was also nice to interview with on-time interviewers who were engaged with each interview. I know lots of other places experiencing "high-growth" will have interviewing-burnt-out engineers but had the opposite experience here. I've also pushed in interviews for the interviewers to seriously tell me what they think could they be improved about the company, and the fact that I received candid, realistic answers was also a good signal. One thing that I'd nitpick on is that the first interview with the hiring manager can be a little jarring as you jump from behavioral to technical within the same hour long slot.