I was recommended by a Google employee. The recruiter contacted me within a week and guided me through the interview process.
They asked me to select four to five 2-hour periods on workdays for two 45-minute phone screens. They utilize a Google Doc for each interviewer to write code.
On the day of my interview, the first interviewer did not contact me. I emailed the recruiter, who called me back in 30 minutes with updated information. The interviewer was late, so their session would be scheduled after my originally second interview.
At that time, I received a call from one interviewer. The question they asked was essentially how to find the point closest to given points on a gridded plane. I did not perform well, and the phone connection was not clear.
The second interview was pleasant. The question was about binary trees and palindromes. These were straightforward topics.
I was rejected within two weeks.
How to locate the point with the minimal distance to all the given points.
This should be done by a connected graph, as all points on the grid can only move up and down.
I tried to answer the question, but the interviewer kept asking me, "Is this the global minimum?" I don't know!
The following metrics were computed from 123 interview experiences for the Google Software Engineering role in United States.
Google's interview process for their Software Engineering roles in the United States is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for Google's Software Engineering interview process in United States.