Taro Logo

Software Engineer Interview Experience - Mountain View, California

February 2, 2016
Neutral ExperienceNo Offer

Process

Overall: Disorganized, but friendly

The interview process took a while, as I was strung across three different recruiter-type people. At one point, one of them forgot a scheduled phone call and apologized in an email, ending it with a "LOL."

The interviews themselves seemed a little disorganized. I asked for a list of interviewers two days ahead of time, and Google said that there wasn't a scheduled list of interviewers. They also had one person interview me about my PhD but couldn't (or didn't) find a relevant expert in my research area. The interviewer they did find was not very polite or curious.

After the interview, Google couldn't tell me when they'd get back to me with a decision (during this time, I was making another company wait), and eventually when they did get back to me, it was just a recruit who wasn't able to offer any useful feedback or advice.

Google, if you want to improve the interview process, here are my suggestions:

  • Use a single recruiter as the point of contact
  • Organize your interviews better
  • Have an interviewer give feedback, not a recruiter

Questions

Algorithms & Data Structures 101

(To be honest, I was surprised at how simple the questions were.)

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