Taro Logo

Software Engineer (University Grad) Interview Experience - Mountain View, California

May 1, 2016
Positive ExperienceNo Offer

Process

Overall process took 14 weeks.

The recruiters were very friendly and helpful.

  • Week 1: Recruiter emails to set up a phone screen.

  • Week 2: Recruiter phone screen: an informal phone call with the recruiter to discuss your current projects and skills.

  • Week 4: Coding sample: you are given a link to two coding problems you have to solve in 60 minutes.

  • Week 9: One phone interview with Google Docs. This is where most of the filtering of candidates happens. I delayed this for 4 weeks to review. The interviewer was helpful and not intimidating. Make sure you walk through your thinking and do not go straight to coding. There were two problems, and I was not able to finish the second one, but I told him my approach. Make sure to engage the interviewer throughout the 45 minutes. They will give you a broad problem, so ask questions!

  • Week 12: Onsite interviews: the most fun interview experience I've ever had! Their campus is awesome. They booked me into a very nice hotel with a shuttle to the campus. They pay for the hotel and flight, with reimbursements for food and ground travel expenses.

    There were two interviews in the morning, lunch with another engineer (not an interview), and two interviews in the afternoon. The first two interviewers were really friendly. The third interviewer was kind of intimidating. He was on his laptop; I don't know if he's taking notes or doing his own thing. I was still able to engage him a little bit and was still able to come up with a solution. The fourth interview was where I screwed up. The interviewer was from an Asian background, and I could not understand most of the words she was saying. I wasn't prepared for the question. It involved a lot of analysis and math.

    All interviewers take pictures of your code for every progress and fixing of bugs you make.

    Approach to all interviews: ask questions, talk through your approach, start coding while talking through what you're writing, and do testing.

  • Week 14: Recruiter called me; they cannot give me an offer. I was kind of expecting this because I knew I had to nail all four interviews. They cannot disclose any information regarding the decision.

I may not have received an offer, but going on-site was such an amazing and memorable experience!

Questions

Data structures and algorithms, including time complexity.

Topics include:

  • Trees
  • Hashmaps
  • Lists
  • Strings
  • Graphs
  • Coding design
  • OOP principles
  • Searches
  • Sorting
  • Traversals

They give you a study guide; make sure to review all of those.

"Cracking the Code Interview" and "HackerRank" definitely helped me prepare.

Was this helpful?

Interview Statistics

The following metrics were computed from 1 interview experience for the Google Software Engineer (University Grad) role in Mountain View, California.

Success Rate

0%
Pass Rate

Google's interview process for their Software Engineer (University Grad) roles in Mountain View, California is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive100%
Neutral0%
Negative0%

Candidates reported having very good feelings for Google's Software Engineer (University Grad) interview process in Mountain View, California.

Google Work Experiences