Taro Logo

Software Engineer Interview Experience

December 1, 2014
Neutral ExperienceGot Offer

Process

I applied to the general new graduate Software Engineer position online via the jobs website.

I was asked to take an online coding assessment that was timed to 60 minutes. It was unscheduled, and they requested I complete it within 6 days.

A recruiter contacted me about 1.5 weeks later to schedule a phone interview. The recruiter asked about my GPA, who I knew at Google (for a reference), and my transcripts. They also asked standard questions about my other interviews or deadlines, visa sponsorship, etc.

The phone interview was about 35-45 minutes long. The interviewer called me late and did not introduce themselves; they just jumped immediately into the first question. They also asked me to type my thoughts and responses into the provided Google Doc instead of speaking out loud too much, so that they could have a record. The question asked was related to summed area tables for 2D matrices of integers. The interviewer did not seem impressed or friendly and immediately hung up after we discussed the single question.

The recruiter got back to me one day after the phone interview to let me know that Google wanted me to fly to the Bay Area and interview in person. The travel setup was easy, and they paid for flights, hotel, meals, etc.

The in-person interview consisted of 4 hour-long interviews with a lunch interview in the middle. It took place in Mountain View on the Google main campus. The interviews were mostly one-on-one, and I was asked coding questions on the whiteboard, questions about my resume, and questions that required analysis of existing/provided source code. Some of the topics were parallel execution, algorithms/tree data structures, image processing, and C and C++.

About 2 weeks after the in-person interview, my recruiter contacted me again to let me know that the team was ready to make an offer. The offer was good, and the position was located in the Bay Area. I negotiated the signing bonus and stock grant upwards by a fairly significant amount using several other offers I had in hand.

Questions

Analyze parallel counting code to determine what possible sequences can be output.

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