Process
I interviewed on campus at my current university.
I had two technical interviews, about 45 minutes in length each.
Nothing was super challenging, but I definitely want to study for them.
I highly recommend "Cracking the Coding Interview" and other similar prep materials to master all your common data structures, Big O times, etc.
Questions
Cannot comment specifically due to NDA.
Similar difficulty as most technical interview prep materials.
Be sure to speak your thoughts all out loud. Even if you're doing poorly, if they understand how you're thinking, it's better than standing there dumbfounded.
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.0Cutting-edge But Tedious WorkSoftware Engineer • Current EmployeeAlmaty, KazakhstanAugust 29, 2025Pros: Challenging cutting-edge engineering tasksCons: Full-time hard work may be tedious.
- 5.0Good company to work forSoftware Engineer • Current EmployeeMountain View, California, United StatesDecember 13, 2023Pros: Good pay and work-life balance.Cons: Depending on the team, there's a lot of politicking.
- 5.0Excellent work environment, but your relationship with your manager will determine your fateSoftware Engineer • Current EmployeeJanuary 5, 2014Pros: Brilliant co-workers, excellent perks, and a collaborative internal culture.Cons: All things hinge on your manager. If they're not very good, this will harm you.
Google Interview Questions
