Taro Logo

Software Engineer Interview Experience

October 5, 2014
Neutral ExperienceNo Offer

Process

Applied through a recruiter about 1+ year after first contact.

There were only phone screens and an on-site interview; no coding interview over the phone (perhaps because I was referred by somebody inside).

Their preparatory e-resources helped, but the space of possible questions is limitless, and there's only so much that one can study. Personally, it's been 10+ years since I last had to delete a node from a binary tree, so my algorithms were rusty, although I did study.

During the on-site visit, there were five technical interviews plus lunch.

I'd say all were considerate and respectful, but two of them were not very polished communicators, in my opinion.

My lunch was accompanied by a friendly engineer -- the best part of the day.

Questions

I'll (mostly) respect the NDA, but one starter question was "In Python, what is a generator?". I got that one; the rest, not so much.

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