Process
It was a 45-minute phone interview with a Google employee. The process began with two simple behavioral questions.
Then, the interviewer described a problem and asked me to solve it. I came up with an algorithm, but he was not satisfied with its complexity.
I then figured out another one, and he agreed to let me write code on a Google Doc.
Questions
A hard question from LeetCode.
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
- 5.0Great Perks, No ConsSoftware Engineer • Former EmployeeIstanbul, TurkeyMay 19, 2023Pros: salary, popularity, holidays, and lots of things like working hours, etc.Cons: There is not much of a con for me.
- 4.0Good Culture, Team DependentSoftware Engineer • Current EmployeeNew York, New York, United StatesAugust 17, 2025Pros: Flexibility and perks are generally great. Your day-to-day experience is shaped a lot by your specific team and org. Hybrid, 3 days in the office, is nice.Cons: Lots of boring work to be done. It can be hard to get interesting projects, depending on the team. Things move slow.
- 3.0SWE at GoogleSoftware Engineer • Current EmployeeApril 24, 2024Pros: The perks are amazing, and the pay is decent too.Cons: You will be a cog in a gigantic machine.
Google Interview Questions
