Not the best company culture
Not the best company culture
- Great pay
- Good benefits
- Good location
- Software Engineering management doesn't really care about team culture.
- The majority of your teammates will be remote, and the company does not really aid in getting to meet each other in person.
- Unrealistic expectations and deadlines.
- No sense of team bonding.
- It's an "every man for themselves" type of work culture.
Work on improving team bonding and team culture.
Additional Ratings
Was this helpful?
Chewy Interview Questions
Chewy Interview Experiences
Software Engineer
A phone call included behavioral questions about current work experience. This was followed by a 10-minute multiple-choice test with 20 questions about Java. The questions covered very specific parts of Java that I had not used before, such as Vecto
Software Engineer
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 placed me in an unfamiliar online en
Software Engineer
The interview consisted of a half-hour session covering behavior and Java knowledge. Key topics included OOP and the differences between ArrayLists and arrays. The session concluded with 25 minutes of coding and 5 minutes for Q&A. The interviewer
Software Engineer
Minneapolis, Minnesota, United StatesJuly 20, 2025A phone call included behavioral questions about current work experience. This was followed by a 10-minute multiple-choice test with 20 questions about Java. The questions covered very specific parts of Java that I had not used before, such as Vecto
Software Engineer
United StatesJune 2, 2025On 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 placed me in an unfamiliar online en
Software Engineer
United StatesMarch 1, 2025The interview consisted of a half-hour session covering behavior and Java knowledge. Key topics included OOP and the differences between ArrayLists and arrays. The session concluded with 25 minutes of coding and 5 minutes for Q&A. The interviewer
