← Google Interview Insights

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

Intermediate
May 2026

Summary

Google PM interview, one question about accessible product design. Pretty open-ended and I wasn't sure how structured my answer needed to be.

Questions Asked (1)

Q1

How would you design a fire alarm system specifically for people who are deaf or hard of hearing?

Product Sense & IdeationAdaptability & Ambiguity
Author's notes

I jumped straight to strobe lights and kind of stalled there for a bit.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying the goal and constraints, then segment users by degree of hearing loss and context (home, workplace, public spaces). Propose a multi-modal alert system that combines visual, tactile, and smart-home integration, and prioritize features using impact vs. effort. Conclude with success metrics and potential risks.

Pro tip: Emphasize that accessibility features designed for deaf users often benefit everyone (e.g., visual alerts in noisy environments), and mention the importance of co-designing with the deaf community to avoid assumptions.

1. Clarify the problem and constraints

Ask questions to understand the scope: is this for a single building, a campus, or a smart home? What budget, regulatory, and technical constraints exist? Who are the exact users (deaf, hard of hearing, with or without cochlear implants)?

2. Segment users and use cases

Break down users by degree of hearing loss, age, tech-savviness, and environment (home, office, public space). Identify key scenarios: sleeping, working, in a noisy area, or alone.

3. Brainstorm multi-modal solutions

Generate ideas across visual (flashing lights, strobe, screens), tactile (vibration on wearables, bed shakers), and digital (smartphone push, smart home integration) channels. Consider redundancy and personalization.

4. Prioritize features and define MVP

Use a framework like RICE or impact/effort to prioritize. Define a minimum viable product that covers core safety needs, then plan iterations for advanced features like AI sound recognition.

5. Define success metrics and risks

Propose metrics: alert latency, reliability, user satisfaction, adoption rate. Identify risks: false alarms, power outages, privacy concerns, and accessibility of the solution itself.

Key Points to Mention

  • Multi-modal alerts: visual (strobe lights, flashing), tactile (vibration, bed shakers), and digital (smartphone notifications, smart home integration).
  • Redundancy and fail-safes: ensure alerts work even if one channel fails (e.g., backup battery, multiple signal types).
  • Personalization and customization: allow users to choose alert types, intensity, and schedules based on their needs.
  • Integration with existing systems: leverage smart home platforms (Google Nest, Alexa) and building alarm systems for cost-effectiveness.
  • User-centric design: co-create with deaf and hard-of-hearing users to validate assumptions and ensure usability.
  • Regulatory and standards compliance: adhere to ADA, NFPA 72, and other accessibility guidelines for alarm systems.

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