Process
Contacted by recruiter in February 2014.
Did phone screen in March 2014 and was rejected the next day.
Questions
The coding questions have nothing to do with data structures or algorithms. The coding itself is short and extremely easy, requiring no improvement beyond a brute-force solution. However, the background is complicated. Lots of questions need to be asked before any coding is done, otherwise you will be doomed, as I was.
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
- 4.0Typical big techSoftware Engineer • Current EmployeeJanuary 4, 2023Pros: Flexible WFH policy, nice people to work with, nice culture, perks, free food, and all kinds of training.Cons: The company is too big. Sometimes it feels like you are just a drop in an ocean.
- 4.0Software Engineer at GoogleSoftware Engineer • Former EmployeeSan Jose, California, United StatesMarch 16, 2023Pros: I like the work environment, as it is very professional.Cons: The hours can be daunting at times, and some projects have seemed less than rewarding.
- 5.0Good Company and BenefitsSoftware Engineer • Current EmployeeMountain View, California, United StatesJanuary 16, 2023Pros: Good benefits and a very nice, friendly workplace.Cons: Do not have as many benefits as a full-time employee.
Google Interview Questions
