Software Engineer I Interview Experience - United States
Process
The recruiter was horrible.
They showed up 10 minutes late, didn't apologize, and didn't answer when I asked how they were doing, out of courtesy.
I interviewed for a full stack role. 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 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.
Questions
Standard recruiter call questions:
- Projects
- Rate
- Programming skills
- Why Chewy?
Was this helpful?
Interview Statistics
The following metrics were computed from 3 interview experiences for the Chewy Software Engineer I role in United States.
Success Rate
Chewy's interview process for their Software Engineer I roles in the United States is fairly selective, failing a large portion of engineers who go through it.
Experience Rating
Candidates reported having mixed feelings for Chewy's Software Engineer I interview process in United States.
Chewy Work Experiences
- 1.0Depends on the teamSoftware Engineer I • Current EmployeeSeptember 3, 2024Pros: Flexible office days (hybrid), which is nice.Cons: Your life really depends on how well you befriend your team (it's not enough to just get along with them). Your manager will target you if you don't talk enough or go above and beyond what is requested. It's a toxic environment.
- 4.0First Job, Pretty Good!Software Engineer I • Current EmployeeMinneapolis, Minnesota, United StatesDecember 19, 2023Pros: Good salary Unlimited PTO (mostly) Good manager (my personal experience) Great chance to learn Nice teammatesCons: Lots of new engineers delivering very visible features (not necessarily a con, as it could be good for getting promoted). Fast pace. Late days/long hours leading up to release (manager does compensate by giving us days off). Projects/requirements sometimes change during development, leading to delays. As a new engineer, I was overwhelmed and failed to deliver a difficult ticket because I: 1. Didn’t know what I was doing. 2. Did not have the guidance of a more senior engineer to make sure all my bases were covered. It was eventually fixed but could be an area of improvement for management. Challenging work is fine as long as the engineer has the support to deliver it properly.
- 3.0Very fast-pacedSoftware Engineer I • Current EmployeeBoston, Massachusetts, United StatesApril 22, 2023Pros: People who care about development learn a lot on the job.Cons: A lot of fast-paced changes and expectations.
Chewy Interview Questions
