Chewy Software Engineer Interview Questions
& Process

My interview process started with a Hackerrank MCQ test, followed by a recruiter phone screening. The final round consisted of a 45-minute behavioral interview and a 45-minute technical interview. Although I felt I did well, they had already filled all internship positions before my final interview and subsequently canceled all interviews scheduled after mine. The recruiter apologized and later informed me via email about a meeting to discuss my potential joining, which unfortunately resulted in a 'no.' While the interview experience itself was positive, the process lacked organization on their part, which I only realized after it concluded.

So the interview process here is okay. I rated it as difficult mainly because it takes way too long to get a job offer, which is tough if you're already employed and trying to prep, work, and interview well. It started with a phone screen, then a HackerRank coding challenge for the second round, followed by four back-to-back one-hour interviews. That's a total of six interviews with one company. I actually liked the first two rounds, but it's wild that the third round isn't just a meet-and-greet to see if you're a good culture fit. Having basically four out of six technical rounds is pretty wild. Also, if they find someone they like before you finish, they'll cancel your final interview, and you don't even get a shot. (So you waste weeks prepping for nothing because they already filled the spot). A lot of weird things happened with this interview, not really thought out. On the plus side, everyone I interacted with from the company was cool, which makes it a bit disappointing.

I applied through LinkedIn. First, I had a recruiter call where they asked about my background. Then, a Senior Engineer conducted a live HackerRank session focusing on a LeetCode medium array problem. My recruiter later set up the final round, which was a panel interview. It included three technical interviews and one behavioral interview with the hiring manager. The behavioral part involved questions about my resume and 'tell me about a time' scenarios. Two technical rounds featured LeetCode medium/easy problems, one array-based and another on binary search trees, along with some Java and Spring vocabulary questions. The last technical interview was frontend-oriented, requiring me to implement a JavaScript class that used async/await to fetch data from an API and process it. I found this part a bit tricky since I primarily do backend work, but they were okay with me checking documentation, and I managed to complete it. I got an offer the following week. Basically, if you're solid on the blind 75 LeetCode problems and understand the core concepts of the tech stack, you should do well.