Process
I applied through an employee referral. The process took 3 weeks. There was standard Google algorithmic rigor, with a heavy focus on scale and edge cases. There was a 45-minute technical phone screen, followed by a 5-round virtual onsite loop.The onsite had:- 3 coding rounds (data structures/algorithms)- 1 System Design round- 1 Googleyness & Leadership roundTo prep, I practiced with standard algorithmic patterns and used Apex Interviewer to simulate the live coding environment, with questions that I scraped from gothamloop and 1point3acres.
Questions
Given a stream of real-time coordinate data from thousands of concurrent users, design an algorithm to find the top K densest geographic clusters within a dynamic time window.
Was this helpful?
Interview Statistics
The following metrics were computed from 5,754 interview experiences for the Google Software Engineer role.
Success Rate
Google's interview process for their Software Engineer roles is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having very good feelings for Google's Software Engineer interview process.
Google Work Experiences
- 4.0Good Pay, Not Meta ScaleSoftware Engineer • Current EmployeeSeattle, Washington, United StatesMay 28, 2025Pros: Slightly above average pay and good perks.Cons: Not paying at Meta's scale
- 5.0Good Pay, Free Food, SlowSoftware Engineer • Current EmployeeLondon, England, United KingdomNovember 8, 2022Pros: Free food, great culture, good pay.Cons: Big company, lots of slow processes.
- 4.0Big company with pockets of start-up projectsSoftware Engineer • Current EmployeeMountain View, California, United StatesMay 10, 2009Pros: Your colleagues are smart, motivated, inventive, and helpful. If you work on the right teams, you can pick up a ton of useful knowledge in a short period of time from world-class experts. The company is attacking plenty of exciting technical problems: machine translation, huge distributed systems, creating smooth AJAX UIs, large-scale machine learning in search & ads, and creating a mobile phone OS from the ground up. Again, this depends on what team you're on, but there's no excuse to be bored with the technical challenges. Parts of the company (e.g., Chrome, Android, mobile apps like Latitude) are blazing new ground and still feel like a start-up. In those areas, there are opportunities for entrepreneurial engineers to make a big impact (although this can be a struggle). Food is excellent.Cons: Big company syndrome. We have dozens of VPs and hundreds of directors. Some are good; all have their own agenda. Successfully launching something to our users is a matter of convincing the right set of people, not building a great product. Hiring bar is lower than it used to be. There are lots of great people coming in, but also plenty of mediocre and some bad hires. Company is much less transparent than it used to be.
Google Interview Questions
