Taro Logo

Software Engineer Interview Experience

October 6, 2018
Positive ExperienceGot Offer

Process

[NEW GRAD]

First, the recruiter and I had a phone screen. They want to get a rough idea of what you like (web, systems, data science, infra, etc.) and see if you're a normal person. We scheduled a phone screen for one month from then, and they sent me a small study guide and pointers about how to do the phone screen.

The phone screen was easy and chill. Implement binary search and know its O(log n). Focus on easy and medium LeetCode problems. The hard ones are too algorithm-based, and none of Google's questions were actually algorithmically hard. Writing workable code is the hard part. Could you implement binary search without a compiler?

On-site interviews were mixed. Some questions were LeetCode easy and medium. The harder ones were just lots and lots of code. For example, designing a whole workable API for some task, then a design parameter changes, and you have to rewrite your thing.

Questions

(Example of a typical design question)

Design a function that will return the degree between the minutes and hours hands on a clock.

(You'll probably write some class and 2 or 3 functions.)

Now, what if we are on a planet with 16-hour days and 57 minutes in an hour?

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