Process
I had a phone interview with Google.
The interviewer was very good, and the questions were not that hard. However, I took too long to figure out the first question, leaving insufficient time for the second.
The interview was scheduled for 45 minutes. Ideally, each interviewee should spend 20-25 minutes tackling a problem and discussing it with the interviewer during that time.
Questions
Merge sorted, non-overlapping lists of intervals with another interval: [(1,3), (5,10), (12,30)] + (9,31) = [(1,3), (5,31)].
Implement a system so that the billionth search query at Google each day wins a car.
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.0Smart Team, Slow PaceSoftware Engineer • Current EmployeeSan Jose, California, United StatesJanuary 2, 2023Pros: Good benefits and WLB, and very smart engineers.Cons: Work can be a little bit slow, and there's a lot of office politics.
- 5.0Great Perks, Limited ScopeSoftware Engineer • Current EmployeeMountain View, California, United StatesJanuary 13, 2021Pros: Lots of perks and learning resources.Cons: The scope of the project can be limited.
- 4.0Good Workplace, No ConsSoftware Engineer • Current EmployeeJanuary 7, 2024Pros: A good workplace to work for.Cons: No cons as of now.
Google Interview Questions
