I received a phone call from a recruiter.
We talked for roughly 45 minutes about my technical background and experiences, as well as the sorts of positions that are currently available in Software Engineering at Google.
This was followed up one week later by a technical interview that consisted of two programming questions and almost no other discussion. I received my negative response from them a few hours later.
I completed both questions with a little time to spare and without receiving help from the interviewer. The two shortcomings I saw in the interview that could have led to their decision not to move forward were:
My advice to others would be to make sure you're 100% refreshed on the syntax of the language you will be interviewing in, and it may be worthwhile to attempt the riskier, flashy answer rather than the more basic solution.
Without going into specifics, I was asked questions about manipulating arrays during the technical interview.
The following metrics were computed from 96 interview experiences for the Google Software Engineer role in Seattle, Washington.
Google's interview process for their Software Engineer roles in Seattle, Washington is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for Google's Software Engineer interview process in Seattle, Washington.