Taro Logo

Software Engineer Interview Experience

October 1, 2014
Neutral ExperienceNo Offer

Process

Several recruiters from Google reached out to me a few times over the last few years; they were quite persistent. The recruiter clearly explained the official interviewing process to me.

For some reason, they skipped the phone interview for me, and the first time I spoke to any Google Engineers was during my in-person interview. I didn't officially "apply" until just before I scheduled the interview, and I didn't apply for any specific job.

The questions were interesting, and the engineers were super smart, quite friendly, helpful, and sometimes awkward. I had five technical interviews in one room over the course of a day in the Google NY office during my in-person interview. Most were one-on-one, and one had a junior engineer sitting in.

Each interviewer wrote down information about the specific question they asked on a sheet of paper, but each of the interviewers noted that they couldn't read the previous interviewers' handwriting.

I was taken to lunch in the Google cafeteria.

Everybody was very intelligent and excited about working at Google. I feel pretty good about working through solutions to all of the interview questions, but I stumbled a little on my probability.

Questions

How would you design & build Twitter from scratch?

Was this helpful?

Interview Statistics

The following metrics were computed from 3,728 interview experiences for the Google Software Engineer role in United States.

Success Rate

12%
Pass Rate

Google's interview process for their Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive59%
Neutral29%
Negative12%

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

Google Work Experiences