Taro Logo

Software Engineer Interview Experience

October 1, 2016
Negative ExperienceNo Offer

Process

The interview was even colder and more impersonal than I expected.

The call started, the interviewer told me their name and job title, then gave me the problem for my code test. I finished the code test, and the call ended.

Not a single question about me or my background. I wasn't really expecting any, but I was surprised that the interviewer said perhaps a couple of dozen words that weren't directly related to the code test.

An important tip: I was told to take the code test in any language that I felt comfortable in. I chose Python because it is so fast to write compared to something like C++, and moving fast is important during code tests. I later learned that they don't like Python for code tests.

Questions

The question had to do with string processing and wiki-style markup.

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