A recruiter contacted me about a 1-year contract position. The first phone interview was conducted two weeks later. The interviewer asked me to write code to detect a cycle in a singly linked list, then asked about the time complexity. The second question was to write a circular buffer. I think I did not do very well, as there was no response for the next three weeks. One day, the recruiter told me Google wanted a second phone interview, so we set it up for one week later. This time, I passed, as I was asked to go onsite one week later. The onsite was conducted two weeks later, with five interviewers, each having a one-hour session. I believe I did very well, but again, I did not get any response for the next three weeks, so I asked the recruiter. He told me I was the only candidate for this position, but Google was still interviewing more candidates. Another two weeks passed, and the recruiter told me they moved to another candidate. The total process took about three months. Most of the interviewers were friendly, except for the team lead, who was very rude for some reason. The overall interview process was frustrating.
Normal interview coding questions.
The following metrics were computed from 1 interview experience for the Google Software Engineer (Consultant) role in Mountain View, California.
Google's interview process for their Software Engineer (Consultant) roles in Mountain View, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Google's Software Engineer (Consultant) interview process in Mountain View, California.