Taro Logo

Software Engineer (New Graduate) Interview Experience

October 1, 2014
Neutral ExperienceNo Offer

Process

Applied 6 months ago and was luckily picked up by a recruiter.

And that luck ended there.

The first phone call malfunctioned with the timing, and I missed the call.

After waiting for 2 weeks, I finally got the phone interview.

Sadly, I was not asked to program C on a whiteboard.

There was 1 brain teaser and 1 very broad algorithm/design question.

It looks like Google is looking for a person with very deep and wide logical thinking and who can discuss mega distributed systems, rather than rigid and swift coding skills for an algorithm snippet.

I guess the interviewer thought I was a PhD student in computer theories.

Questions

  1. From Houston to Mountain View, how long does it take to transfer information via the internet, e.g., texts via a shared online Google Document?

  2. Describe how social media works, e.g., LinkedIn, on finding if two users are connected.

Was this helpful?

Interview Statistics

The following metrics were computed from 1 interview experience for the Google Software Engineer (New Graduate) role in United States.

Success Rate

0%
Pass Rate

Google's interview process for their Software Engineer (New Graduate) roles in the United States is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive0%
Neutral100%
Negative0%

Candidates reported having mixed feelings for Google's Software Engineer (New Graduate) interview process in United States.

Google Work Experiences