Initial phone screen with the recruiter asking about background. Followed by 1-hour one-on-one interview with a senior engineer. This was part meet-and-greet to ask about past projects, and part live code session. The live coding session involved a handful of basic but very granular JS and React questions - "here's a function that needs its "this" variable rescoped, how do I do that and why," "here's an old-school React pattern, how would I do this with hooks?", etc. Also included a dreaded LeetCode/HackerRank-style algorithm code challenge. Straightforward prompt, but tedious to think through and very conceptual, as they often are. Sadly, did not make it past this stage due to performance anxiety. Have to say I was disappointed to see Chewy use this interview format as it's a poor way to showcase a developer's skillset and the value they could bring to a team. I feel I could've made it farther if I were able to instead answer the questions ahead of time and then talk them through with the interviewer, which better simulates a typical development + code review cycle a professional software dev would be familiar with. Unfortunately it is par for the course in this industry so not truly a Chewy-specific problem.

First is an HR phone screening. Telling you about the company, benefits, position, and inquiring about your experience and technical skills. If you pass that you'll have a virtual video technical interview. If you passed that one, then you'll have a day of the onsite interview which consists of 2-4 technical & non-technical. Unfortunately, I don't know the exact number of interviews as I did not pass to the onsite. The interview was a good experience and was pretty casual. Consisted of software skills and technical one. After the coding, there was time to ask them questions as well. The interviewer I had was pretty easy to talk to and gave a good rundown of what it's like working at the company and the team you'll be working in. The coding challenge is a joined coding hackerrank, but they allow you to reference external online documentation. I didn't pass as I was told the interview was going to be in Java & OOP, and prepared for that instead, of vanilla JS & CSS. However, I should've known better as this was a front-end position. Tip: Focus on the basics for the coding interview, and definitely don't be afraid to get feedback from the interviewer. And always ask questions at the end of the interview. Overall a good experience, and would probably apply again for another position in the future.