Process
Contacted by Google within two weeks from resume submission.
Two consecutive phone interviews were conducted, each lasting 45 minutes and featuring one coding question.
No behavioral questions were asked.
- The first interview focused extensively on data structures, with some language and design questions.
- The second interview started directly with the coding question.
Questions
Nothing requires knowledge of fancy algorithms, e.g., the Knuth–Morris–Pratt algorithm.
You just need some "street smartness" on practical problems to work out coding problems.
Chapter 10, "Scalability and Memory Limits," in Cracking the Coding Interview will help.
Was this helpful?
Interview Statistics
The following metrics were computed from 58 interview experiences for the Google Software Engineering Intern role in United States.
Success Rate
Google's interview process for their Software Engineering Intern roles in the United States is fairly selective, failing a large portion of engineers who go through it.
Experience Rating
Candidates reported having very good feelings for Google's Software Engineering Intern interview process in United States.
Google Work Experiences
- 4.0Good Perks, Limited ImpactSoftware Engineering Intern • Former EmployeeLos Angeles, California, United StatesSeptember 1, 2021Pros: * A cool experience; you get to meet a lot of cool people. * Well paid with good perks.Cons: You don't really get to do much as an intern. Experience and learning vary largely because of the host/team.
- 5.0Exceptional Experience, Few CriticismsSoftware Engineering Intern • Current EmployeeSanta Monica, California, United StatesAugust 30, 2011Pros: Everything looks fine to me.Cons: Almost no cons to me.
- 4.0Great Perks, Slow ProgressSoftware Engineering Intern • Former EmployeeFebruary 13, 2024Pros: Work-life balance Benefits (food, insurance, massage chairs, etc.)Cons: Can be slow to work. The manager is usually busy, and progress is slow.
Google Interview Questions
