I first spoke with them at a job fair at my school. They were aware that I knew one of the higher-ups there.
My initial assessment involved one online HackerRank quiz, which required significant Java knowledge but no direct coding. Following this, I had a two-to-three-hour interview at their office in Boston. During this session, I spoke with two engineers for experience and resume discussions, and completed one Java code reading/refactoring exercise. I felt the entire process went quite well, and I liked the people I met.
After the interview, I remained in frequent contact with the recruiters. I also knew others who had interviewed with the company.
The recruiters strung me and others along for about a month. They repeatedly told us they would get back to us the following week, then the week after that, and so on. Finally, around Thanksgiving, they emailed me (and I assume the others) to explain that it was the busy season and all engineers were needed to handle the workload. They stated they were pausing recruitment until the new year.
At this point, the situation had become quite ridiculous. I decided to withdraw myself from consideration, as I had other offers. Even though I was fairly confident I would eventually receive an offer, the company's disorganization throughout the process left me with a poor overall impression.
Read a Java snippet and discuss how to refactor it and make it better.
The following metrics were computed from 16 interview experiences for the Chewy Software Engineer role in Boston, Massachusetts.
Chewy's interview process for their Software Engineer roles in Boston, Massachusetts is extremely selective, failing the vast majority of engineers.
Candidates reported having negative feelings for Chewy's Software Engineer interview process in Boston, Massachusetts.