The interview process began with an initial call with the recruiter. This was a standard conversation to ensure the role's requirements aligned with the candidate's aspirations.
The second step involved a call with the VP of Engineering. This was also a standard call, not technical in nature. The primary goal was for the company to present the position and organization to the candidate, providing a wealth of information. It's advisable to prepare thoughtful questions for this stage.
Third, a technical assessment was administered via HackerRank. The initial question required determining if two input strings were anagrams. The difficulty was then increased by a variation: identify if a short string exists as an anagram within a longer text.
Following the technical assessment, there was another brief recruiter call to discuss the upcoming onsite interview.
The final stage was the onsite interview, which included meetings with individuals from various departments: HR, Product Management, Software Development team members, and a Software Manager. The interviews were not intensely technical. The Software Manager presented a scenario focused on collaboration with Product Managers, with the complexity of the question increasing. This was designed to gauge thought processes rather than technical difficulty. A technical question posed was to write a Java method to insert a new node into a sorted linked list of integers while maintaining the sorted order. The constraint was that all nodes had a final next member variable, preventing direct alteration of the nodes.
After completing the onsite, the process concluded with the recruiter. They sought extensive feedback on the interview and the overall process. Subsequently, a follow-up email with a survey was sent, requesting further feedback. The final communication was a phone call informing the candidate of their non-selection, delivered with a brief, generic reason. This provided a disappointing end to the experience, especially given the company's emphasis on detailed candidate feedback contrasted with their concise rejection.
In Java, write a method to insert a new node into a sorted linked list of integers such that the list still remains sorted. The catch is all the nodes have a final member variable for next, so you cannot alter the node.
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.