← Google Interview Insights

Google·Product Manager·Onsite - Product Sense / Strategy·Senior

Senior
Jun 2026

Summary

PM interview at Google with a cost estimation question for Google Photos. Pretty classic product sense meets back-of-envelope math combo, nothing too wild but it requires you to actually know what goes into running a product at that scale.

Questions Asked (1)

Q1

Estimate the annual cost of managing Google Photos. What factors would you consider in your calculation?

Product Analytics & MetricsProduct StrategyTechnical Trade-offs
Author's notes

I started with storage since that's the obvious one, but then kind of froze trying to figure out whether to account for compression, deduplication, tiered storage across hot and cold buckets.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Break down the cost into major components: storage, compute, network, and operations, then estimate each using reasonable assumptions about user scale and usage patterns. Structure your answer by first stating assumptions, then calculating costs, and finally discussing key drivers and trade-offs. Emphasize that this is a product management estimation, focusing on order of magnitude and strategic implications.

Pro tip: Anchor your estimate with known public data (e.g., Google Photos has over 1 billion users, and Google's total cloud storage is exabytes) and use round numbers to simplify calculations. Show that you understand the difference between marginal cost and fully loaded cost, and highlight how product decisions (e.g., compression, tiered storage) impact the bottom line.

1. Clarify scope and assumptions

Define what 'managing Google Photos' includes (storage, serving, processing, etc.) and state key assumptions like number of users, average photos per user, and storage per photo.

2. Estimate storage costs

Calculate total data stored by multiplying users, average photos, and average file size. Then apply a cost per GB per month for cloud storage (e.g., Google Cloud Storage rates) to get annual storage cost.

3. Estimate compute and network costs

Consider costs for image processing (uploads, transcoding, ML for search), serving images (CDN egress), and ongoing operations. Estimate based on usage patterns and cloud pricing.

4. Sum components and sanity-check

Add up storage, compute, network, and operational costs to get a total annual cost. Sanity-check against Google's overall cloud spending or revenue to ensure plausibility.

5. Discuss key drivers and trade-offs

Highlight factors that most impact cost (e.g., user growth, compression algorithms, storage tiering) and how product decisions can optimize costs while maintaining user experience.

Key Points to Mention

  • User scale: Google Photos has over 1 billion users, with varying activity levels.
  • Storage cost: Average photo size (e.g., 2-5 MB) and total data stored (exabytes).
  • Compute cost: Image processing, machine learning for search, and serving images.
  • Network cost: Data egress for viewing and sharing photos.
  • Operational cost: Engineering, support, and infrastructure maintenance.
  • Cost optimization: Use of cold storage, compression, and efficient data centers.

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.