Product Sense: Choose a User Segment and Design a Better Physical Keyboard

Quick Overview

A product design question that asks a PM candidate to design a computer keyboard for a chosen group of users. It tests segmentation in a mature hardware market, pain-point discovery, feature prioritization under cost and battery constraints, and success metrics for a physical product.

Product Sense: Choose a User Segment and Design a Better Physical Keyboard

Company: Google

Role: Product Manager

Category: Product Design & Strategy

Difficulty: medium

Interview Round: Other

Design a keyboard for computers. Decide which users it is for and which of their problems it should solve that today's keyboards do not, choose the features you would build first, and explain how you would measure whether the product succeeds. ```hint Earn a reason to exist Keyboards are cheap, mature and everywhere. Look for one group of typists whose daily problems current keyboards leave unsolved, and let that group's needs decide every feature you keep or cut. ``` ### Clarifying Questions - Is this a physical keyboard, an on-screen software keyboard, or both? - Which devices must it work with: a single desktop or laptop, or several devices such as a work laptop, a home computer and a tablet? - Is the goal a profitable new hardware product line, or a keyboard that mainly strengthens an existing family of devices and software? - Are there constraints on price point, launch markets or the languages and layouts it must support? ### What a Strong Answer Covers - A clear reason for a new keyboard in a crowded, mature market, tied to a stated goal. - Segmentation of keyboard users and a justified choice of one segment to design for. - Concrete pain points of that segment, ranked by how often and how badly they hurt. - Prioritized features with the hardware trade-offs they bring, such as cost, size, battery life and compatibility. - Success metrics and risks suited to a physical product, including returns and defects. ### Follow-up Questions - Your top feature pushes the price well above mainstream keyboards. Do you keep it, cut it, or change the segment? - How would you test demand for the keyboard before committing to a manufacturing run? - How would the design change if it had to serve people who type in several languages and scripts every day?

Overview: A product design question that asks a PM candidate to design a computer keyboard for a chosen group of users. It tests segmentation in a mature hardware market, pain-point discovery, feature prioritization under cost and battery constraints, and success metrics for a physical product.

Google logo
Google
Oct 28, 2025
mediumProduct ManagerOtherProduct Design & Strategy
0
0

Design a keyboard for computers. Decide which users it is for and which of their problems it should solve that today's keyboards do not, choose the features you would build first, and explain how you would measure whether the product succeeds.

Clarifying Questions Guidance

  • Is this a physical keyboard, an on-screen software keyboard, or both?
  • Which devices must it work with: a single desktop or laptop, or several devices such as a work laptop, a home computer and a tablet?
  • Is the goal a profitable new hardware product line, or a keyboard that mainly strengthens an existing family of devices and software?
  • Are there constraints on price point, launch markets or the languages and layouts it must support?

What a Strong Answer Covers Guidance

  • A clear reason for a new keyboard in a crowded, mature market, tied to a stated goal.
  • Segmentation of keyboard users and a justified choice of one segment to design for.
  • Concrete pain points of that segment, ranked by how often and how badly they hurt.
  • Prioritized features with the hardware trade-offs they bring, such as cost, size, battery life and compatibility.
  • Success metrics and risks suited to a physical product, including returns and defects.

Follow-up Questions Guidance

  • Your top feature pushes the price well above mainstream keyboards. Do you keep it, cut it, or change the segment?
  • How would you test demand for the keyboard before committing to a manufacturing run?
  • How would the design change if it had to serve people who type in several languages and scripts every day?