New Product from Two Decades of Historical Street-Level and Satellite Imagery
Company: Google
Role: Product Manager
Category: Product Design & Strategy
Difficulty: medium
Interview Round: Other
Imagine you can draw on 20 years of geographic data, such as street-level imagery like Street View and satellite images. Which product would you create from it, who is it for, and why?
```hint Make the time dimension earn its place
A current map already shows what a place looks like today. Think about who needs to know how a place has changed, and what decision that history helps them make.
```
### Clarifying Questions
- Is the data only imagery, or does it also include other geographic layers such as road networks, business listings or traffic history?
- Am I free to choose the customer, whether consumers, businesses or public agencies?
- What limits apply to using the imagery, for example around faces, license plates and private homes?
- Should the product live inside an existing product such as Maps or Earth, or can it be a new standalone business?
### What a Strong Answer Covers
- A clear goal and a deliberate choice of user segment, with a reason why twenty years of history matters to that segment
- Pain points the historical imagery solves better than a present-day map or existing tools
- A prioritized product concept with a focused first version, including how raw imagery becomes usable signals
- Success metrics and a business model that fit the chosen segment
- Risks such as privacy, uneven coverage across places and years, model errors and misuse
### Follow-up Questions
- Coverage is dense in big cities and sparse in rural areas and early years. How does that change your product?
- How would you stop the product from being used to track specific people or homes over time?
- How would you test demand before committing a team to build it?
Overview: A product design question asking what product to build from 20 years of geographic data such as street-level and satellite imagery. It tests choosing a user segment for whom historical change matters, prioritizing a focused first version, defining success metrics, and handling privacy and coverage risks.