Process
They ask typical data structure and algorithm questions, but not as hard as other companies.
Rather than using Hackerrank or CodePad, they have you code in a Google Doc. The focus is more on the algorithm and problem-solving than whether the code compiles.
The process includes 1-2 phone screens, followed by 4-5 onsite interview sessions for a total of 6.
Senior people will have some design/architecture interviews rather than pure coding. PhD candidates will be asked about their thesis by a Googler knowledgeable in the area.
Questions
List processing
Binary Tree Traversals
Dynamic Programming
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
Google's interview process for their Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having very good feelings for Google's Software Engineer interview process in United States.
Google Work Experiences
- 2.0Too big and too politicalSoftware Engineer • Current EmployeeMountain View, California, United StatesJuly 28, 2025Pros: Lots of talented people within the company, yet.Cons: A lot of bureaucracy and politics.
- 3.0Fun Place, But Not FunSoftware Engineer • Current EmployeeMountain View, California, United StatesSeptember 5, 2023Pros: A very fun place to work.Cons: not that fun to work.
- 5.0Absolutely Love Working HereSoftware Engineer • Current EmployeeAugust 26, 2020Pros: Love it! It is really great.Cons: None! I love working here.
Google Interview Questions
