Striveworks interview questions

Intro Call to discuss role, Technical Coding Evaluation, Technical Call with individual Didn't make it past the technical call. Overall, not a bad process. A little disorganized. Seemed like things were thrown together at the last minute.

45 minute call with a Recruiter 1-3 hour online coding exam 2 hour long interviews with Senior Engineers Full day in the office I only made it to the 2 interviews with engineers. My experience was good until the second interview with the Senior engineer. The recruiter was friendly and did a great job explaining the company, role, and interview process. The coding exam was straightforward and similar to something you would find on LeetCode The first of the hour-long interviews I had an organized, well spoken Engineer who talked through my resume, answered questions about the role, and explained the tech stack in the first half. The second half there was an "over-the-shoulder" coding exam given a similar style prompt to the online coding exam. The second one hour interview I had an Engineer who did not seem very organized. The first 5 minutes were him getting set up. We then jumped immediately intro a contrived coding exam to design an API. I tried to explain how I would do it in production, but there was a lot of hand-waving that didn't make sense. We then briefly talked about my experience before going into a rapid-fire question/answer phase. It seemed like breadth was valued higher than depth, and the way the questions were posed were vary impersonal. The interview ended with a hard stop at the end of the hour. It was this interview that soured my experience with the process. I was rejected for "lack of depth and experience with distributed systems" despite feeling that the interviews went pretty well.