I applied online. I interviewed at Chewy in May 2026
Interview
Applied online and received a call about 3 weeks later. We first had a screening phone interview where they asked things like "Why chewy".
About a week later there was a technical round scheduled with an engineer on the team. During this round I was presented with an easy hacker rank question and was able to move forward.
The final round was a set of 4 interviews, 3 of which were technical and 1 behavioral. The technical interviews involved debugging existing applications and talking through the design of a basic CRUD application. Each of these interviews was 1 hour long and they spanned over 2 days.
Overall, everyone was pretty respectful and friendly throughout the whole process.
Interview questions [1]
Question 1
Walk through the design of a basic CRUD application. Consider various trade offs of all the decisions you make.
Recruiter was straight up horrible. They showed up 10 minutes late, didn't even apologize, and didn't answer me when I asked how they were doing out of courtesy. I interviewed for a full stack role, and although I did not possess direct work experience in React (which the job description did not explicitly state in the requirements) I have used it before in multiple side projects which I mentioned during the call. I was then rejected immediately after being asked about my react skills, which was annoying given that it wasn't explicitly mentioned in the requirements. However, what angered me the most was that the rejection email was sent DURING our call not even after. I don't know if all their recruiters are like this, and perhaps I got unlucky, but this experience rubbed me the wrong way
I applied online. I interviewed at Chewy (Minneapolis, MN)
Interview
A phone call with behavioral questions about current work experience. Then a 10 minute multiple choice test with 20 questions about Java. Questions were on very specific parts of Java that I have not used before like Vector classes and different implementations of Vector classes.
On the initial call, the screener told me that the coding interview would be a series of coding questions on a certain skills-testing website, so that is what I prepared for. It wasn’t that at all— the interviewer plonked me down in an empty online environment that I wasn’t familiar with and basically said “build a web app, go” with very little guidance. I wasted too much time trying to figure out how to import different packages into the environment while the interviewer was very unclear on if that’s what he expected me to do or not. Then he said “time’s up” and was not interested in hearing any more about my thought process.
