Product design question

Design a radio alarm clock for the next generation.

Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.

What this question tests

Product design skill on a familiar hardware object, checking if you can find real user needs beyond nostalgia features.

Confirm the target user and context, likely bedside use across ages, and ask if voice or smart home integration is in scope.
List pain points with current alarm clocks: waking a partner, snoozing habits, disconnection from phone-based alarms, poor sleep tracking.
Segment users into heavy sleepers, shift workers, and couples with different schedules, since needs diverge sharply.
Prioritize two or three problems, for example partner-safe wake and gentle wake-up for poor sleepers, over adding every smart feature.
Propose a design: gradual light and sound wake, per-person wake zones or haptic wearable pairing, and offline reliability without a phone.
Define success as reduced snooze count and improved reported sleep quality, and confirm scope on whether hardware cost matters.

Names a specific underserved segment, couples with mismatched schedules, as the wedge rather than building a generic smart speaker clone.
Proposes a directional haptic wristband or pillow vibration so one partner wakes without disturbing the other.
Sets a measurable goal as an assumption, for example a 20 percent drop in reported snooze taps within a month of use.
Explains why simplicity beats stacking features, since alarm clocks succeed on reliability, not app richness.

Jumping straight to smart speaker features and ignoring the specific pain of shared beds or unreliable wake.
Not defining what next generation means for this device versus a phone alarm.
Skipping a success metric entirely.

How would you prioritize between a partner-safe feature and smart home integration?
What would make someone choose this over their phone alarm?