Taro Logo

Software Engineering Interview Experience

October 1, 2015
Neutral ExperienceGot Offer

Process

The engineering interviews were awesome. My interviewers were really nice, and I felt like they wanted me to be successful.

The process took way too long. There was a two-week delay from resume to contact, a two-week delay between contact and interview, and a week delay from interview to notification of success. This led to submission to a committee, which took over two weeks. Finally, after the committee approved my application, I waited a week to get in touch with my recruiter, who explained host matching. By this time, I had been in the process for over two months.

I accepted an offer at a similar company that offered a much smoother process, more responsive recruiters, and significantly better compensation.

Questions

NDA. However, I suppose it doesn't hurt to say that you should know about:

  • How to code
  • Data structures
  • The programming language you are using's core libraries
  • Basic algorithms like quicksort and binary search
  • Dynamic programming
  • Backtracking algorithms.

Was this helpful?

Interview Statistics

The following metrics were computed from 123 interview experiences for the Google Software Engineering role in United States.

Success Rate

26%
Pass Rate

Google's interview process for their Software Engineering roles in the United States is very selective, failing most engineers who go through it.

Experience Rating

Positive67%
Neutral24%
Negative9%

Candidates reported having very good feelings for Google's Software Engineering interview process in United States.

Google Work Experiences