Taro Logo

Software Engineer Interview Experience - Mountain View, California

July 1, 2011
Neutral ExperienceNo Offer

Process

The interviews included demoing previous work I'd done (public product) and answering detailed questions about the technologies in my area of interest. Algorithmic coding on the whiteboard was also part of the process. Ultimately, I think only the algorithmic coding was significantly considered, based on the internal recruiter's feedback about all candidates (though they wouldn't provide information specific to me).

The problems presented were atypical to coding we do in computing in general, much more aligned with what I studied as an undergraduate. Big-O analysis and scaling were prominent. I believe there is a disconnect between what they tested and what engineers in the positions I was focused on do on a regular basis, with neither necessarily being a good measure for the other.

I found all the interviewers very friendly. It was as if they wanted me to succeed and would ask helpful questions when I was off base. A friend (also interviewing there) and I wondered if their model is that everyone gets the answer, and the measure is just how much help they provided.

Questions

They asked that we keep the interview questions confidential, and I will respect that.

Was this helpful?

Interview Statistics

The following metrics were computed from 748 interview experiences for the Google Software Engineer role in Mountain View, California.

Success Rate

20%
Pass Rate

Google's interview process for their Software Engineer roles in Mountain View, California is very selective, failing most engineers who go through it.

Experience Rating

Positive64%
Neutral23%
Negative14%

Candidates reported having very good feelings for Google's Software Engineer interview process in Mountain View, California.

Google Work Experiences