# Product Sense Interview Answer

Structure a spoken PM product-sense answer with assumptions, segmentation, pain-point...

- Repository: https://github.com/deanpeters/Product-Manager-Skills (7825 stars)
- Category: Design
- License: see repository
- Last updated: 2026-10-16
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add deanpeters/Product-Manager-Skills --skill product-sense-interview-answer -g -a claude-code -y`
Codex: `npx skills add deanpeters/Product-Manager-Skills --skill product-sense-interview-answer -g -a codex -y`
Cursor: `npx skills add deanpeters/Product-Manager-Skills --skill product-sense-interview-answer -g -a cursor -y`
Gemini CLI: `npx skills add deanpeters/Product-Manager-Skills --skill product-sense-interview-answer -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add deanpeters/Product-Manager-Skills`

## Description

Structure a spoken PM product-sense answer with assumptions, segmentation, pain-point prioritization, and MVP tradeoffs. Use when practicing design, improve, or build-next interview questions.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

## Purpose

Help PM candidates and interview coaches structure product-sense answers that sound strong out loud, not just on paper. Use this when practicing prompts like "How would you improve X?", "Design a product for Y", or "What would you build next for Z?"

This is not a memorize-and-recite script. It is a reasoning scaffold that prevents solution-jumping, forces real prioritization, and leaves the interviewer with a clean story they can follow.

## Input

**Works best with:** The interview prompt you're practicing (e.g., 'How would you improve X?', 'Design a product for Y').
**Also useful:** The company/role you're interviewing for and how much time the answer gets.

Anything supplied with the invocation itself, text after the skill name, a pasted context dump, or an appended `ARGUMENTS:` line, counts as answers already given. Use it and skip whatever it covers; don't re-ask.

**Arriving empty-handed? That works too.** The skill asks for the prompt, then walks the reasoning scaffold with you out loud.

**Example invocation:** `Practice this: 'How would you improve Google Maps for commuters?', 25-minute answer, L5 PM loop.`

## Key Concepts

### What Product Sense Interviews Actually Test

Strong product-sense answers do more than generate ideas. Interviewers are usually testing whether you can:

- Clarify ambiguous prompts without getting stuck
- Tie user value to market or business logic
- Segment thoughtfully instead of talking about "everyone"
- Prioritize one pain point instead of describing ten equally
- Make tradeoffs explicit when choosing an MVP
- Communicate clearly under time pressure

### The Six-Part Answer Spine

The rest: https://github.com/deanpeters/Product-Manager-Skills/blob/HEAD/skills/product-sense-interview-answer/SKILL.md