Taro Logo

Software Engineer Interview Experience

October 1, 2015
Negative ExperienceNo Offer

Process

This was my second time applying, after taking help from an internal referral. I had to ask (beg for, perhaps) to get an interview scheduled.

Last time (over a year ago), I wasn't able to solve something in C, or I wasn't able to write code at all in C. I had explicitly stated I am good with Python and okay with a 5/10 in C/C++. I was asked only C programming questions. The same thing (and mostly the SAME question) was asked.

The funny thing is, I was asked to write in C (like I had said I was a C expert), but not at all an algorithmic question. I was so surprised when HR told me, "Last time you weren't able to code, when do you want to schedule?"

Me: "Next week" (I had been preparing for 5 months).

She: "Really?" (rhetorical).

I was much disappointed, as reviews suggest completely the opposite: you can get an interview every 6 months, or no concern with language or data structure/algorithm is the primary thing to focus on.

Questions

How do you split a given string into words?

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