Taro Logo

Software Engineer Interview Experience

February 20, 2015
Neutral ExperienceNo Offer

Process

I just got through the technical phone screening. I applied via campus recruiting.

The recruiter requested that I fill out some information and assigned a time slot.

The Google engineer called me. He had a unique accent and asked some brief questions regarding my resume before starting the coding problem. I was struggling, and after 30 minutes, he tried to give some sub-problems that could serve as hints for the coding assignment. After 40 minutes, he explained a brief solution.

We also used Google Docs to show my code.

It was somewhat hard to communicate with the interviewer because of his unique accent.

After several days, I received notice that I would not be considered for the next interview.

Questions

I cannot specify the exact coding problem, but it was related to graphs. The problem was concise but somewhat tricky. I am actually an EE engineer, and while I have learned data structures, I am not completely comfortable using them. This was the reason I struggled.

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