Software Engineer applicants have rated the interview process at Chewy with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 43% positive. To compare, the company-average is 46% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 24 days to get hired, when considering 49 user submitted interviews for this role. To compare, the hiring process at Chewy overall takes an average of 18 days.
Common stages of the interview process at Chewy as a Software Engineer according to 49 Glassdoor interviews include:
Phone interview: 27%
One on one interview: 21%
Group panel interview: 18%
Presentation: 13%
Skills test: 10%
Background check: 4%
Other: 3%
Drug test: 3%
Personality test: 2%
Here are the most commonly searched roles for interview reports -
Initial screening, coding round, technical round, manager round. Coding was around secario based ask in algo and data structure. Leetcode helps to gain exp in clearing the Algo n ds question n problem
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.
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.