Choosing a product to build from unlimited global location data, privacy set aside

Quick Overview

A product design and strategy interview question: if every kind of location data were available and privacy were not a constraint, what would you build? It tests how a PM sets selection criteria, picks a problem that truly needs such data, defines a first version and metrics, and handles the misuse risks that remain.

Choosing a product to build from unlimited global location data, privacy set aside

Company: Google

Role: Product Manager

Category: Product Design & Strategy

Difficulty: medium

Interview Round: Other

Suppose you could use every kind of location data that exists anywhere in the world, and privacy was not a constraint. What product would you build, and why? ```hint Choose the problem before the data Unlimited data makes almost anything possible, so the hard part is choosing. Look for a costly problem that persists mainly because nobody knows where people or things are right now. ``` ### Clarifying Questions - Does "all location data" include live, individual positions of people and vehicles, or only places, maps and historical movement patterns? - Should the product build on Google's existing businesses such as Maps, or can it be a new standalone business? - Is the aim the largest business opportunity, or the largest benefit to people even if revenue is modest? - Does setting privacy aside also remove consent and security obligations, or only limits on what data can be collected and combined? ### What a Strong Answer Covers - A goal and selection criteria stated before choosing, with a few candidate ideas compared against them - A chosen user and problem that genuinely needs location data at this scale, rather than one that today's data already solves - A concrete product: what it does, which data it fuses, how each user experiences it, and the first version to ship - How success is measured and how the product creates value or revenue for Google - Risks that remain even with privacy set aside, such as misuse, data gaps and trust, and how the design limits them ### Follow-up Questions - Privacy rules come back tomorrow. Which parts of your product survive with aggregated or anonymized data, and which do not? - How could a bad actor misuse your product, and what would you build to stop it? - What is the smallest version you could ship first to test the riskiest assumption?

Overview: A product design and strategy interview question: if every kind of location data were available and privacy were not a constraint, what would you build? It tests how a PM sets selection criteria, picks a problem that truly needs such data, defines a first version and metrics, and handles the misuse risks that remain.

Google logo
Google
Aug 28, 2026
mediumProduct ManagerOtherProduct Design & Strategy
0
0

Suppose you could use every kind of location data that exists anywhere in the world, and privacy was not a constraint. What product would you build, and why?

Clarifying Questions Guidance

  • Does "all location data" include live, individual positions of people and vehicles, or only places, maps and historical movement patterns?
  • Should the product build on Google's existing businesses such as Maps, or can it be a new standalone business?
  • Is the aim the largest business opportunity, or the largest benefit to people even if revenue is modest?
  • Does setting privacy aside also remove consent and security obligations, or only limits on what data can be collected and combined?

What a Strong Answer Covers Guidance

  • A goal and selection criteria stated before choosing, with a few candidate ideas compared against them
  • A chosen user and problem that genuinely needs location data at this scale, rather than one that today's data already solves
  • A concrete product: what it does, which data it fuses, how each user experiences it, and the first version to ship
  • How success is measured and how the product creates value or revenue for Google
  • Risks that remain even with privacy set aside, such as misuse, data gaps and trust, and how the design limits them

Follow-up Questions Guidance

  • Privacy rules come back tomorrow. Which parts of your product survive with aggregated or anonymized data, and which do not?
  • How could a bad actor misuse your product, and what would you build to stop it?
  • What is the smallest version you could ship first to test the riskiest assumption?