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

Senior

May 2026

Summary

Google PM interview, one big open-ended product design question covering basically everything: user scenarios, MVP scoping, architecture, and scale. Felt more like a mini system design session than a typical product sense round, which threw me off a bit.

Questions Asked (1)

Design a photo-sharing app where users can upload, view, share, and download photos across multiple devices. Walk through user scenarios, the MVP feature set, the system architecture (clients, backend, storage, sync), and how you'd think about scaling it.

System DesignProduct Sense & IdeationTechnical Trade-offs

Author's notes

I started with user scenarios which felt right, but I spent way too long on the fluffy persona stuff and barely had time for the architecture piece, which is clearly where they wanted to go.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by framing the problem around user needs and business goals, then define a focused MVP that delivers core value. Next, outline a scalable system architecture that handles multi-device sync and storage, and finally discuss trade-offs and scaling strategies. Balance product sense with technical depth, always tying decisions back to user impact and metrics.

Pro tip: Anchor your answer in a clear product vision and success metrics (e.g., daily active users, upload success rate) before diving into technical details. This shows you think like a PM who prioritizes user value and measurable outcomes, not just an engineer.

1. Clarify Goals and User Scenarios

Ask clarifying questions to understand target users, key use cases, and business objectives. Define primary user scenarios such as uploading from mobile, viewing on web, sharing albums, and downloading originals across devices.

2. Define MVP Feature Set

Prioritize features that deliver core value: upload, view, share, and download photos. Include essential capabilities like authentication, basic album organization, and cross-device sync. Defer non-critical features like advanced editing or social feeds.

3. Design System Architecture

Outline clients (mobile/web), backend services (API gateway, auth, metadata, sync), storage (object storage for photos, CDN for delivery), and sync mechanism (e.g., delta sync, conflict resolution). Consider using cloud services for scalability.

4. Address Scaling and Trade-offs

Discuss scaling strategies: horizontal scaling of services, sharding metadata, using CDN for global delivery, and optimizing storage costs with tiering. Highlight trade-offs between consistency, latency, cost, and complexity.

5. Summarize and Measure Success

Recap key decisions and propose success metrics (e.g., upload success rate, sync latency, user retention). Suggest next steps for iteration based on user feedback and data.

Key Points to Mention

Multi-device sync strategy (e.g., delta sync, conflict resolution, offline support)
Storage architecture (object storage, CDN, image optimization, metadata database)
Scalability considerations (horizontal scaling, sharding, caching, rate limiting)
Security and privacy (encryption, access control, GDPR compliance)
MVP prioritization and trade-offs (build vs. buy, feature scope)
Success metrics and user feedback loops

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