The process began with a call with the recruiter, focusing on basic background and resume-related questions. The interview was straightforward, and I was informed that the next round would be a short, take-home MCQ test on JavaScript. This test lasted 15 minutes and consisted of easy questions.
After passing that round, I proceeded to my third technical interview, which was a front-end coding challenge lasting an hour. As soon as the interview started, the interviewer, without any introduction or communication, simply provided a link to the coding challenge and instructed me to share my screen. I found this approach a bit unusual, but I proceeded.
The coding challenge was hosted on HackerRank and involved DOM manipulation, fetching data from an API, displaying results, and adding event listeners. I was able to complete the entire challenge, despite encountering a few hiccups in the middle, which I managed to resolve. I felt I performed well and was confident I would be invited for an on-site interview. However, I never heard back from the recruiter.
After several follow-ups, I was informed that they were moving forward with another candidate, which was expected. I requested feedback, but it was never provided.
In summary, the interview process was good and not overly demanding, but I remain unsure about their specific expectations.
Round 1 with recruiter - resume based and background check.
Round 2: MSQ test - JavaScript-related questions, to be solved in 15 minutes.
Round 3: Front-end coding - 1-hour technical interview on DOM manipulation, fetching data from an API, adding event listeners, etc.
The following metrics were computed from 1 interview experience for the Chewy Software Engineer - UI role in Boston, Massachusetts.
Chewy's interview process for their Software Engineer - UI roles in Boston, Massachusetts is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Chewy's Software Engineer - UI interview process in Boston, Massachusetts.