Part 1: HR Screening with Recruiter - There was nothing out of the ordinary there. The recruiter was friendly and informatively answered my questions about the role and the company's somewhat recent merger (Angi's List, Homeadvisor, and Handy are all Angi now). Part 2: 1-Hour Coding-Pair Interview - Before going into my interview, the recruiter gave me a prep document that told me what leetcode problem would be the basis of the code-pair. That was nice, so I was able to know exactly how to prep and I wasn't caught off guard. My interviewer was very amicable and we actually worked together on the problem. And despite everything going wrong (dogs barking, internet cutting out for a few minutes), he was very understanding and even reminded me to breathe. I'm always nervous with interviews. Part 3: Virtual Onsite - This has a similar structure as most FAANG companies. Thankfully, there was an option to split the interviews over two days, which is what I did. The first interview of the onsite was a coding-pair interview, though this interviewer was not as collaborative or friendly as my previous one. They continued to mention that they expected working code by the end of the interview. When I got stuck, it was like pulling teeth to get help. At the end, they said that I got the hardest part completed, so I did well. Their tone of voice didn't reassure me at all. The second interview, a API and Databased building exercise, was easy and more reminiscent of what I actually do everyday. The third interview was a culture fit, which was also pretty straightforward. The fourth interview was a review of an architecture proposal, trying to find errors within it. For these interviews, the interviewers were much friendlier than the first interviewer. The final interview was with the Director of Engineering that focused more on my mentoring and leadership style. The conversation flowed easily, though he did start it with some frontend knowledge questions since the interviews only cover backend topics and this was a frontend-focused role. He said that he hoped to speak with me further at the end of the interview. The next day, the recruiter called me and said that despite all the positive feedback from the team, they would not be extending an offer. They said that they wanted a tech lead that had strong software architect skills. I'm not sure if the job description matched exactly what they were looking for then since I'm a software engineer, not an architect. The recruiter said that they would keep my information and let me know if they have mid-level roles available later on. Not sure if I want to join a somewhat large company that doesn't have a dedicated QA team. We'll see. Overall the process went well enough. I do wish that companies would move away from that multiple hour onsite format. It's very draining, even with breaking the interviews up over a couple of days.