After the 30-minute HR call, I was scheduled for a technical interview. It took about a week to get it scheduled, and the technical interview was actually fun. I can see how the questions could show a programmer's strengths.
Then came the final round, which started with a system design. It wasn't too hard, but the question could have been explained better, as no one knows your internal business logic. The second round was an interview; finding the top k products was pretty easy.
The third round was horrible. I don't think it reflected my ability to work. I believe the goal of this round was to have me Google everything and remember its definition.
Tell me about Spring. Well, it's a framework that implemented MVC to build a web app. Okay, how? Then tell me the definition of REST. Tell me what's MapReduce, and what's the reduce part. Tell me the difference between Spring Boot and Spring. What's the definition of Dependency Injection?
I was constantly being asked for definitions. Like, how the heck do I know? I am not fresh out of college, and even if I were, I wouldn't remember the definition.
The following metrics were computed from 3 interview experiences for the Chewy Senior Software Engineer role in Seattle, Washington.
Chewy's interview process for their Senior Software Engineer roles in Seattle, Washington is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Chewy's Senior Software Engineer interview process in Seattle, Washington.