Taro Logo

Software Engineer, Tools and Infrastructure Interview Experience

December 13, 2015
Positive ExperienceNo Offer

Process

I interviewed over the phone and was not invited to an on-site interview.

The recruiter reached out first, as Google had my information from previous internship applications. First, I scheduled a 30-minute recruiter call, where they provide information about the position you're applying for. This was followed by two 1-hour coding interviews, scheduled about a week and two weeks later.

The coding interviews are conducted on Google Docs, so you won't have syntax highlighting. Be prepared! I programmed in Java.

Questions were the standard type you would find in a review book. I used "Elements of Programming Interviews in Java" to prepare.

I was asked to schedule the second phone interview a few days after the first one, being told: "The interviewer thought you were very bright but has suggested another phone screen."

During the technical interviews, my first interviewer did not ask any questions specific to the SETI position (i.e., testing), but my second interviewer did ask such questions.

A few days after the last interview, I was told: "The interviewer thought you were very bright, but we would like to see a few years of industry experience first."

Questions

string manipulation; graph navigation

Was this helpful?

Interview Statistics

The following metrics were computed from 6 interview experiences for the Google Software Engineer, Tools and Infrastructure role in United States.

Success Rate

17%
Pass Rate

Google's interview process for their Software Engineer, Tools and Infrastructure roles in the United States is very selective, failing most engineers who go through it.

Experience Rating

Positive83%
Neutral0%
Negative17%

Candidates reported having very good feelings for Google's Software Engineer, Tools and Infrastructure interview process in United States.

Google Work Experiences