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

Senior

Apr 2026

Summary

PM interview at Google with a single product strategy question about whether to build a WiFi quality assessment feature. No frills, just one meaty question and a lot of silence while I tried to figure out where to even start.

Questions Asked (1)

Should Google build a product capability to evaluate WiFi quality across different locations, and if yes, how would you approach it?

Product StrategyProduct Sense & IdeationSystem Design

Author's notes

I spent too long on the 'should they' part and not enough on the 'how'.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying the strategic fit and user value of a WiFi quality evaluation product for Google, then outline a structured approach covering user needs, technical feasibility, and business impact. Emphasize how it aligns with Google's mission and existing products, and propose a phased implementation plan with clear success metrics.

Pro tip: Demonstrate awareness of privacy and data sensitivity concerns, and suggest leveraging existing Google infrastructure like Android and Google Maps to minimize new investment while maximizing reach.

1. Clarify the Problem and Strategic Fit

Ask clarifying questions to understand the scope, target users, and Google's strategic goals. Assess whether this capability aligns with Google's mission and existing product ecosystem.

2. Identify User Needs and Use Cases

Define primary user segments (e.g., consumers, businesses, ISPs) and their pain points. Prioritize use cases such as finding reliable WiFi, optimizing network performance, or informing infrastructure investments.

3. Evaluate Technical Feasibility and Data Sources

Consider how to collect WiFi quality data (e.g., crowdsourcing from Android devices, user surveys, partnerships). Address challenges like data accuracy, privacy, and scalability.

4. Define Product Vision and Features

Outline a product concept, such as a map-based WiFi quality index or an API for developers. Prioritize features based on user value and technical effort, and consider integration with Google Maps or Assistant.

5. Propose Implementation Plan and Metrics

Suggest a phased rollout (e.g., pilot in select cities), define success metrics (e.g., user engagement, data coverage, partner adoption), and outline potential risks and mitigation strategies.

Key Points to Mention

Alignment with Google's mission to organize information and make it universally accessible, and synergy with products like Google Maps, Android, and Google Fi.
Privacy considerations: ensuring user consent, anonymizing data, and complying with regulations like GDPR.
Technical approach: leveraging crowdsourced data from Android devices, using machine learning to infer quality, and validating with ground truth.
Monetization and business model: potential for ads, partnerships with ISPs, or premium APIs for enterprises.
Competitive landscape: existing solutions like Speedtest, OpenSignal, and how Google can differentiate.
Go-to-market strategy: starting with a limited pilot, iterating based on feedback, and scaling globally.

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