Product Sense: Voice-First Calling on Smart Speakers With Privacy and Security Trade-offs

Quick Overview

A product design prompt about a voice-driven calling product for smart speakers and displays such as Alexa or Google Home. It tests the choice of user and use case, the spoken call flow on shared household devices, and concrete privacy, data security and user experience decisions, plus metrics and guardrails.

Product Sense: Voice-First Calling on Smart Speakers With Privacy and Security Trade-offs

Company: Amazon

Role: Product Manager

Category: Product Design & Strategy

Difficulty: medium

Interview Round: Other

Design a calling product that people use entirely by voice, comparable to the calling features built into smart speakers and displays such as Alexa or Google Home. Explain who it is for, how calls are placed and received, and what the first version would include. Then address three areas explicitly: user privacy, data security, and user experience. ```hint Walk one call through a shared room Follow a single call from the spoken request to hang-up on both ends. A speaker in a kitchen serves a whole household and its guests, so at each step ask who can hear, who can act, and what gets stored. ``` ### Clarifying Questions - Is this a feature of an existing assistant and device family, or a standalone product that must win users on its own? - Should calls reach only other devices and app users on the same service, or ordinary phone numbers as well? - Audio only, or video too on devices with screens? - Which markets come first? Emergency-calling and telecom rules differ by country. ### What a Strong Answer Covers - A chosen user and use case, such as families staying in touch with older relatives or hands-busy moments, and why voice beats a phone there - The core call flow: resolving a spoken name to the right contact, confirming when unsure, and routing incoming calls on shared devices - Privacy design for shared, always-listening devices: who sees contacts and call history, consent for instant connections, and visible microphone and camera state - Security: encryption, phone-number and account linking, the limits of voice identification, spam and abuse, and data retention - Success metrics with guardrails such as wrong-contact and accidental-call rates ### Follow-up Questions - A child asks the speaker to call a number that is not in the household's contacts. What should happen? - How would you let an elderly parent's device auto-answer calls from family without turning it into a monitoring tool? - How should the product respond to a request to call emergency services in a market where it cannot place such calls?

Overview: A product design prompt about a voice-driven calling product for smart speakers and displays such as Alexa or Google Home. It tests the choice of user and use case, the spoken call flow on shared household devices, and concrete privacy, data security and user experience decisions, plus metrics and guardrails.

Amazon logo
Amazon
Jun 5, 2026
mediumProduct ManagerOtherProduct Design & Strategy
0
0

Design a calling product that people use entirely by voice, comparable to the calling features built into smart speakers and displays such as Alexa or Google Home. Explain who it is for, how calls are placed and received, and what the first version would include. Then address three areas explicitly: user privacy, data security, and user experience.

Clarifying Questions Guidance

  • Is this a feature of an existing assistant and device family, or a standalone product that must win users on its own?
  • Should calls reach only other devices and app users on the same service, or ordinary phone numbers as well?
  • Audio only, or video too on devices with screens?
  • Which markets come first? Emergency-calling and telecom rules differ by country.

What a Strong Answer Covers Guidance

  • A chosen user and use case, such as families staying in touch with older relatives or hands-busy moments, and why voice beats a phone there
  • The core call flow: resolving a spoken name to the right contact, confirming when unsure, and routing incoming calls on shared devices
  • Privacy design for shared, always-listening devices: who sees contacts and call history, consent for instant connections, and visible microphone and camera state
  • Security: encryption, phone-number and account linking, the limits of voice identification, spam and abuse, and data retention
  • Success metrics with guardrails such as wrong-contact and accidental-call rates

Follow-up Questions Guidance

  • A child asks the speaker to call a number that is not in the household's contacts. What should happen?
  • How would you let an elderly parent's device auto-answer calls from family without turning it into a monitoring tool?
  • How should the product respond to a request to call emergency services in a market where it cannot place such calls?