Taro Logo

Software Engineer Interview Experience

November 1, 2015
Neutral ExperienceNo Offer

Process

I got the chance through campus recruitment. It was a 45-minute tech interview over the phone. The interviewer started by introducing his role and how things work for him. He then asked an open-ended question, continued to ask follow-up questions to guide the direction, and finally asked me to implement it on Google Docs.

Questions

Given a random large number, how do you show or express it?

Let's say a number like "1234567", what other ways can you show it instead of, for example, "1,234,567"?

How many bytes does an "int" typically use?

If it's 4 bytes, how large a number can it hold?

Why are there different numbers of bytes for an integer across different machines?

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