Process
I received an email to schedule two one-hour phone interviews back-to-back. Both interviews began with an introduction, followed by technical challenges, and then non-technical questions.
The technical challenges occupied a significant portion of the hour, typically 20-40 minutes. The interviewer would often ask for optimizations or present a more difficult problem related to the initial challenge.
Questions
What is the most challenging bug, and what did you learn?
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.0Amazing work experienceSoftware Engineer • Current EmployeeDublin, Leinster, IrelandOctober 23, 2022Pros: Flexible work hours. Good working environment.Cons: I didn’t find any corn, actually.
- 5.0Great Culture, Fewer OpportunitiesSoftware Engineer • Current EmployeeToronto, Ontario, CanadaFebruary 12, 2025Pros: Best for work and cultureCons: Less in terms of opportunities.
- 4.0Great People, Red TapeSoftware Engineer • Current EmployeeSan Francisco, California, United StatesOctober 29, 2024Pros: Great people Great work/life balance Free foodCons: Tons of red tape
Google Interview Questions
