Improve Google's speed for users: pick a segment, design fixes and measure the gain
Company: Google
Role: Product Manager
Category: Product Design & Strategy
Difficulty: medium
Interview Round: Other
You are a product manager at Google, and you are asked how you would make Google faster. Decide what "faster" should mean for the people who use it, choose where to focus first, propose the improvements you would make, and explain how you would know they worked.
```hint Define speed from the user's side
Server response time is only one piece of the wait. Follow a real search from the moment someone starts typing until they have what they needed, and look for where the time actually goes for the users you choose.
```
### Clarifying Questions
- Does "Google" mean Google Search, or the wider set of Google products such as Maps, Gmail and Chrome?
- Should "faster" mean lower technical latency, with pages and results loading sooner, or less total time for people to finish what they came to do?
- Are particular users in scope, such as people on slow mobile networks and entry-level phones, or is this about all users everywhere?
- Is something prompting the question, such as complaints, a competitor that feels quicker, or falling usage in some markets?
### What a Strong Answer Covers
- A definition of speed from the user's point of view, and the goal it serves for users and for Google.
- A breakdown of where time goes in a typical journey (typing the query, serving, network, rendering, the clicked page, rewriting the query) and a reasoned choice of the segment to target.
- Specific improvements for that segment, prioritized by impact and effort, including at least one trade-off between speed and richness, data cost, privacy or the health of publishers' sites.
- Success metrics measured at the right percentiles, with guardrails on result quality, revenue and data use, and a plan to validate with experiments.
### Follow-up Questions
- Your change makes the results page faster but sends less traffic to publishers' websites. How do you weigh that?
- People on slow connections often give up before results load, so their searches barely appear in your logs. How would you measure their experience?
- Leadership can fund only one of three projects: a lighter results page, preloading the page a person is likely to open next, or more direct answers on the results page. Which do you pick, and why?
Overview: A product manager prompt on making Google faster for the people who use it. It tests whether a candidate can define speed from the user's side, find where time is really lost, choose a user segment, prioritize improvements and measure the gain with sound metrics and guardrails.