Pros: - The interview process is much more of a natural conversation about programming than about Leetcode. - Both the initial recruiter call, hiring manager call, and first technical call, were all very friendly and had a good vibe. - The people that i talked to on the calls seemed nice. - The first tech screen was set up in a way where I felt that I could highlight my own strengths. Cons: - Very unstructured process. During the System Design round it felt like the loose structure made it very difficult to have any type of discussion. It was somewhat unclear exactly what the interviewers were looking for. They mentioned that "we don't have to go into database table specifics" but then a few minutes later asked me about how the database table layout would look leading to a bit of confusion on my side as it felt unclear what skills they wanted me to highlight. - Too many people in the interviews. In the last System Design round there were 3 interviewers (2x Staff, 1x Principal) who would often talk over each other. They would often ask different questions which made it difficult to follow any type of "red thread" in the interview as we would constantly context switch back to things we discussed some time in the past.

I attended only the intro interview and dropped out of the process. The recruiters were personable and welcoming. While the job market was pretty closed during my interview, the role's requirements seemed misaligned with its advertised "full-stack" title and senior-level compensation. The position demanded not only full-stack expertise and a specific skill set but also leadership capabilities and in-depth system design knowledge. It appeared the company sought an individual to manage and maintain its legacy infrastructure while a new one was being developed, effectively assuming broad responsibility for a complex and aging system. The company itself did not seem to have much perspective going forward.