Taro Logo

Software Engineering Interview Experience

January 1, 2016
Positive ExperienceNo Offer

Process

I applied online in October 2016 but did not hear back until December.

While waiting, I personally contacted one of the employees whom I knew from my university.

Right after I was referred by that person, the recruiter began contacting me for documentation and scheduling the interviews.

I went through three separate phone interviews from January to February 2016.

The interviews were sequential, scheduled one after another.

All interviews were about coding questions. There were no questions about my resume or background at all.

All interviews were one-on-one, and the interviewees were very interactive and tried to help.

Questions

There were one or two coding questions per interview. Most of the questions followed a similar pattern:

Given a specific set of data (e.g., a 2D matrix with random values or with some patterns), what is the best way to perform specific operations (e.g., searching or sorting) on that dataset?

Explain how you would solve it and why you think it is a good approach.

Show the implementation.

Was this helpful?

Interview Statistics

The following metrics were computed from 123 interview experiences for the Google Software Engineering role in United States.

Success Rate

26%
Pass Rate

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

Experience Rating

Positive67%
Neutral24%
Negative9%

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

Google Work Experiences