Process
The interviews were pretty straightforward, each lasting 45 minutes, and they were scheduled within an hour of each other.
I thought I performed poorly, but I still received an offer. This experience suggests it's not solely about writing perfect code on the first attempt, but rather about explaining your thought process and communicating clearly.
The questions were challenging, but I don't believe they were intended to be easy.
Questions
There were two questions per interview:
- One that tested more coding.
- One that tested more problem-solving skills.
Was this helpful?
Interview Statistics
The following metrics were computed from 123 interview experiences for the Google Software Engineering role in United States.
Success Rate
Google's interview process for their Software Engineering roles in the United States is very selective, failing most engineers who go through it.
Experience Rating
Candidates reported having very good feelings for Google's Software Engineering interview process in United States.
Google Work Experiences
- 5.0Great Team, High TalentSoftware Engineering • Former EmployeeSingapore, SingaporeAugust 19, 2018Pros: Nice people to work with.Cons: Easy to replace, as the team is full of superstars.
- 4.0Good perks, degrading culture, maintenance work in India, slow growthSoftware Engineering • Current EmployeeMay 4, 2024Pros: Good perks. Brand name. Good WLB. Awesome tech and people.Cons: Internal politics. Everything is too slow to build. Slow growth.
- 1.0I hate myselfSoftware Engineering • Former EmployeeSeattle, Washington, United StatesNovember 22, 2010Pros: Free food, easy work hours.Cons: Never got to see my product make it to launch.
Google Interview Questions
