First, I had a phone screen with a recruiter, then came on-site for a technical interview. After that, I returned for a full day, which included four technical interviews, an architecture discussion, and a "previous work" discussion. Everyone I met was friendly and interesting.

In general, I liked the interview process because the technical interviews revolved around actual problem-solving, including compiling your own code, rather than focusing solely on algorithms and theory. The interviewers clearly stated their expectations upfront (e.g., "make it work but don't worry about efficiency").

The process lasted a long time because I was intentionally extending it while interviewing at other companies. The recruiters were very kind about letting me take my time and did not pressure me to move forward more quickly.

Over the course of all the interviews, I had five or six different tech questions. These aren't things you can study for because, as I said earlier, they are looking for your capacity to learn and adapt, along with your experience, rather than how well you studied algorithms over the weekend.