Product Sense Interview Answer
Six-part spine (clarify → rationale → goal → segmentation → pain → solution) for PM product-sense interviews — sound thoughtful out loud instead of over-scripted on paper.
You walked into the "How would you improve YouTube?" interview, brain-dumped four feature ideas, and walked out wondering why you didn't get the offer. Product sense isn't about creativity — it's about reasoning out loud. Establish the user, goal, and pain before any solution, and the answer feels earned. Skip those, and even good ideas sound ungrounded.
Who it's for: PM candidates practicing product-sense interviews, hiring managers running mock interviews, coaches teaching FAANG-style prompts, candidates moving to senior PM roles
Example
"How would you improve YouTube?" → Clarify (creators vs. viewers vs. advertisers?) → Rationale (why now) → Goal (help beginner learners find content they're glad they watched) → Segment (beginner learners vs. enthusiasts) → Pain (no structured progression) → MVP (Learning Paths) with v1 exclusions
CLAUDE.md Template
New here? 3-minute setup guide → | Already set up? Copy the template below.
npx ccplaybooks add product-sense-interview-answer# Product Sense Interview Answer
Coach PM candidates through open-ended product-sense interviews using a six-part answer spine: clarify, rationale, goal, segmentation, pain points, solution. Sound thoughtful out loud — not over-scripted on the page.
Not a memorize-and-recite script. A reasoning scaffold that prevents solution-jumping.
## What These Interviews Test
- Clarify ambiguous prompts without getting stuck
- Tie user value to market/business logic
- Segment thoughtfully (not "everyone")
- Prioritize one pain point (not ten equally)Get new playbooks like this one
One email a week with new Claude Code workflows. Free, like everything here.
No spam. Unsubscribe anytime.
What This Does
Coaches you through 6 sequenced sections (clarify → rationale → goal → segmentation → pain → solution) with quality bars at each step. Prevents solution-jumping, segmentation theater, and weak closes. Outputs an answer that sounds conversational, prioritizes one user/pain/MVP, and ends with a memorable one-sentence recap.
Pairs with problem-statement, proto-persona, and opportunity-solution-tree for deeper practice.
Quick Start
mkdir -p ~/Documents/ProductSenseInterview
mv ~/Downloads/CLAUDE.md ~/Documents/ProductSenseInterview/
cd ~/Documents/ProductSenseInterview
claude
Provide the prompt ("How would you improve X?", "Design Y for Z", "What would you build next?"). Claude coaches you through the six-part spine and stress-tests the answer.
The Six-Part Spine
| # | Section | Output |
|---|---|---|
| 1 | Clarify | 1-2 scope-changing questions or stated assumptions |
| 2 | Rationale | One-line thesis (market + company logic) |
| 3 | Product Goal | Help [user] [outcome], so that [impact] |
| 4 | Segmentation | Target segment + 2-sentence persona |
| 5 | Pain Points | Journey map + one prioritized pain |
| 6 | Solution | 3 distinct options + chosen MVP + exclusions + closing recap |
Tips & Best Practices
- State structure early. "I'll clarify, then walk through goal, segment, pain, and MVP" — interviewer can follow.
- Cap clarifiers at 2. More than that feels like stalling.
- One pain, not three. Severity + frequency lens. The fulcrum of the whole answer.
- Three distinct solutions. Different mechanisms, not three flavors of the same idea.
- Memorable close. "For beginner learners, the top pain is no structured progression, and my first bet is Learning Paths." That's what gets repeated to the hiring panel.
Common Pitfalls
- Feature dump before naming user/goal/pain
- Listing 5 segments and choosing one with no rationale
- Goal that's actually a feature ("build an AI learning path")
- Pain points that are missing features ("no AI summary")
- Three "solutions" that are one solution with different packaging
- Ending after listing features (no closing recap)