Fermi estimate of how much data per second Google Maps moves over the network
Company: Google
Role: Product Manager
Category: Product / Decision Making
Difficulty: medium
Interview Round: Other
How much network bandwidth does Google Maps need? Build an estimate, showing your equation, the assumption behind each input and your final figure.
```hint Split the traffic
Break the traffic into the main things people do in Maps and estimate the data each one moves, before multiplying by how many people do it.
```
### Clarifying Questions
- Should the estimate cover data sent to users, data users send back (location, photos, reviews), or both?
- Is the scope global or a single country?
- Do you want the daily average or the peak load the network must be provisioned for?
- Should traffic from other websites and apps that embed Maps through its developer APIs be counted?
### What a Strong Answer Covers
- A clarified scope: direction, geography, and average versus peak
- A clear equation that splits traffic by user activity, with users, frequency and data size for each
- Assumptions stated as round, labeled numbers, with reasoning for the largest drivers
- Correct arithmetic and unit conversion from bytes per day to bits per second
- A sanity check, and how caching and peak load change the answer
### Follow-up Questions
- Which single assumption moves your answer most, and how would you pin it down?
- How would wider use of offline maps, or a better on-device cache, change the figure?
- How does the estimate change if the interviewer wants the capacity needed for one region at its evening peak?
Overview: A Google product manager estimation question asking how much network bandwidth Google Maps needs. It tests scoping the estimate, building a clear equation from user activities and data sizes, labeling assumptions, converting units correctly, and sanity-checking the result against caching and peak load.