Process
There were five technical interviews, each lasting 45 minutes.
The problems were very algorithm-centered. I was asked two dynamic programming problems, which rarely happened at other companies.
Yet, all the problems were fair game, and none of them required knowing a certain "trick" in order to solve.
Two weeks later, the recruiter reached out with the final decision from the hiring committee: no offer. I was not surprised, since I had botched the first two interviews.
Overall, the experience was positive.
Questions
A system design problem that has an emphasis on throughput and integrity.
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.0Good place to workSoftware Engineer • Current EmployeeIrvine, California, United StatesMarch 5, 2024Pros: Nice reputation with great people.Cons: Too many cumbersome meetings and not too much crack time on development.
- 5.0Always Learning, No ConsSoftware Engineer • Current EmployeeChennai, Tamil Nadu, IndiaJuly 1, 2022Pros: Everyone can learn new things.Cons: There is no cons, I think.
- 2.0the usual big techSoftware Engineer • Former EmployeeOctober 31, 2023Pros: Lots of benefits, nice offices.Cons: Return to office is brutal.
Google Interview Questions
