A Google recruiter had been in contact with me over the last couple of years, likely having found my LinkedIn profile. After a few phone conversations in the past where I decided the time wasn’t right, eventually it was, and we scheduled the first technical interview. This followed a few phone conversations about the available positions, discussing how the process worked, and how to prepare.
The recruiter provided ample resources for preparation, including videos, PDFs, book titles, coding practice websites, as well as direct written advice on how to handle the interview itself.
For the technical interview, there were a few technical hiccups at the start. Eventually, we got going over a combination of Google Meet, phone (the interviewer said I was difficult to hear over Meet), and Google Docs (the link to the other platform wasn’t working).
The interviewer helped stop me from going down unproductive pathways that I would have wasted time on and asked probing questions to get me to improve my solutions.
Write a function to insert a new value into a hashed linked list. This is a linked list where every entry has a hash value determined by its value and the hash of the following value.
The following metrics were computed from 3,728 interview experiences for the Google Software Engineer role in United States.
Google's interview process for their Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Google's Software Engineer interview process in United States.