Take home technical, real-world problem. At the time, it was a kind of small application functionality you might build out on the job. Then phone screen, and on-site with technical questions solving some coding and system design problems.

The interview process was outlined in the job listing, and they followed it well. The first rounds were your typical recruiter screen and hiring manager conversation. Then there were two technical rounds. One was a pair programming exercise, and the other was an architectural exercise. The final round was a panel interview with people in multiple job functions that you would be working with. The tech rounds were a little different than what I'd experienced with other companies. The pair programming exercise wasn't really DSA/LeetCode-esque. Instead, it was a real-world problem that you worked through to kinda prove you knew how to reason through a problem and code it out. The architectural exercise was generally conversational, and we discussed how to go about building something and how to approach different things you might see in production. Both were straightforward, and there weren't any trick questions or anything like that. I feel like it was one of the more realistic technical interview experiences I’ve had, and I appreciated that. The recruiters were very communicative and gave info on what to expect at each round. They got back to me promptly between rounds to let me know where I stood and to answer any questions I had. The interviewers were all nice and knowledgeable, and they were able to answer all of my questions. Overall, it was one of the better interview experiences I've had, especially compared to other startups and tech companies.