Taro Logo

Software Engineer Interview Experience

December 1, 2014
Negative ExperienceNo Offer

Process

The process began with two phone screens, followed by an onsite interview.

The second phone screen involved basic technical questions.

The onsite interview consisted of two 50-minute sessions with developers from the team I applied to.

After these interviews, an experienced employee joined me for lunch. This was a non-technical Q&A session.

Following lunch, there were two more 50-minute interviews with interviewers from other departments at Google.

Each 50-minute interview included a coding question to be completed within 45 minutes, followed by a 5-minute Q&A. Coding was done on a whiteboard.

The questions were generally easy, but candidates were expected to explain their ideas and algorithms while coding.

If a question was completed with significant time remaining, a follow-up question would be posed, up to a maximum of three, or conceptual questions would be asked to fill the remaining time.

I tackled approximately 10 coding problems and one design problem across the four interviews.

Despite feeling confident in my answers, I was ultimately rejected. The recruiter declined to provide specific reasons.

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