Product design: an alarm that wakes deaf users without relying on sound

Quick Overview

A product design question asking how to build an alarm clock for people who are deaf. It tests user segmentation, mapping the full wake-up journey, comparing alerts that do not rely on sound, choosing a first version, and defining success metrics centered on waking reliability.

Product design: an alarm that wakes deaf users without relying on sound

Company: Google

Role: Product Manager

Category: Product Design & Strategy

Difficulty: medium

Interview Round: Other

Design an alarm clock for people who are deaf. Explain whom you are designing for, what gets in the way of waking up on time today, which product you would build first and why, and how you would know it works. ```hint Moments, then signals List the moments the product must handle, from setting the alarm the night before to being fully awake, then ask which signals can reach a sleeping person who cannot hear and what happens if they move during the night. ``` ### Clarifying Questions - Should this be a physical bedside device, a phone or smartwatch app, or are we free to choose, including new hardware? - Are we designing only for people with no usable hearing, or also for hard-of-hearing users, such as hearing-aid or implant users who take their devices off to sleep? - Is the main job waking from sleep, or should the product also handle timed alerts during the day? - Does the user sleep alone, or should the design avoid waking a partner who shares the bed? ### What a Strong Answer Covers - Distinct groups of deaf users (hearing level, how deeply they sleep, who they live with, which devices they already own) and a reasoned choice of whom to serve first. - Pain points across the whole alarm journey: setting it, trusting that it is set, being woken reliably, snoozing and dismissing, and failures the user cannot hear, such as a power cut or a disconnected accessory. - Alert methods that do not rely on sound, compared on how reliably they wake someone, comfort, effect on a bed partner, and cost, leading to a prioritized first version. - Success metrics centered on waking reliability, and how the product would be tested with deaf users before launch. ### Follow-up Questions - A user sleeps through the alarm twice in one week. How could the product notice, and what should it do? - How would the design change for someone who is both deaf and blind? - Would you market this as an accessibility product or as a mainstream silent alarm? What changes in pricing and distribution?

Overview: A product design question asking how to build an alarm clock for people who are deaf. It tests user segmentation, mapping the full wake-up journey, comparing alerts that do not rely on sound, choosing a first version, and defining success metrics centered on waking reliability.

Google logo
Google
Nov 16, 2025
mediumProduct ManagerOtherProduct Design & Strategy
0
0

Design an alarm clock for people who are deaf. Explain whom you are designing for, what gets in the way of waking up on time today, which product you would build first and why, and how you would know it works.

Clarifying Questions Guidance

  • Should this be a physical bedside device, a phone or smartwatch app, or are we free to choose, including new hardware?
  • Are we designing only for people with no usable hearing, or also for hard-of-hearing users, such as hearing-aid or implant users who take their devices off to sleep?
  • Is the main job waking from sleep, or should the product also handle timed alerts during the day?
  • Does the user sleep alone, or should the design avoid waking a partner who shares the bed?

What a Strong Answer Covers Guidance

  • Distinct groups of deaf users (hearing level, how deeply they sleep, who they live with, which devices they already own) and a reasoned choice of whom to serve first.
  • Pain points across the whole alarm journey: setting it, trusting that it is set, being woken reliably, snoozing and dismissing, and failures the user cannot hear, such as a power cut or a disconnected accessory.
  • Alert methods that do not rely on sound, compared on how reliably they wake someone, comfort, effect on a bed partner, and cost, leading to a prioritized first version.
  • Success metrics centered on waking reliability, and how the product would be tested with deaf users before launch.

Follow-up Questions Guidance

  • A user sleeps through the alarm twice in one week. How could the product notice, and what should it do?
  • How would the design change for someone who is both deaf and blind?
  • Would you market this as an accessibility product or as a mainstream silent alarm? What changes in pricing and distribution?