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

SeniorPrefer not to say

May 2026

Summary

Google product sense question about world traffic data. No navigation allowed, which is the obvious answer, so you're kind of forced to actually think. Pretty open-ended and I'm not sure I landed anywhere great.

Questions Asked (1)

If you had access to traffic data for every street in the world, what would you build? Navigation and maps-style applications are off the table.

Product Sense & IdeationProduct StrategyAdaptability & Ambiguity

Author's notes

The constraint is the whole point of this question.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying the scope and constraints, then choose a specific user segment and problem to solve. Brainstorm a few ideas, select one, and dive deep into its value proposition, features, and success metrics, ensuring it's not a navigation/maps app.

Pro tip: Anchor your idea in a clear user pain point and articulate how the unique dataset enables a defensible advantage. Show awareness of data privacy and ethical considerations, which is crucial for Google.

1. Clarify and Scope

Ask clarifying questions about the data (real-time vs historical, granularity) and constraints (e.g., no navigation apps). Define the goal: to build a product that leverages global traffic data.

2. Identify User Segments and Pain Points

Brainstorm potential users (e.g., city planners, logistics companies, event organizers, emergency services) and their pain points related to traffic. Choose one segment to focus on.

3. Ideate and Select a Product Idea

Generate 2-3 product ideas that solve the chosen pain point, then select the most promising one based on impact, feasibility, and alignment with Google's strengths.

4. Deep Dive into the Chosen Idea

Describe the product's core value proposition, key features, how it uses the traffic data, and how it differs from navigation apps. Outline the user journey.

5. Define Success Metrics and Risks

Propose metrics to measure success (e.g., user engagement, cost savings) and discuss potential risks (e.g., data privacy, adoption barriers) and mitigations.

Key Points to Mention

User-centric problem definition: Clearly state the problem and target user before jumping to solutions.
Data application: Explain how the traffic data (real-time, historical, global) uniquely enables the solution.
Differentiation: Emphasize how the product is not a navigation/maps app and provides distinct value.
Feasibility and scalability: Consider technical and business feasibility, including data infrastructure and go-to-market.
Success metrics: Define measurable outcomes (e.g., reduced congestion, increased efficiency) to evaluate the product.
Ethical considerations: Address privacy, data security, and potential misuse of traffic data.

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