Product Sense Interview: What It Is, How It's Scored, and 15 Practice Questions

The product sense interview is the round that ends the most PM candidacies. It’s also the least understood: no leetcode-style right answer, no case framework you can memorize the night before. Just an open-ended prompt — “How would you improve Google Maps?” — and 30 minutes of an interviewer watching how you think.

This guide covers what the round actually is, how interviewers score it, a framework for structuring answers, and 15 practice questions to drill.

What the product sense interview is

Product sense questions ask you to do the core PM job in miniature: understand users, identify the highest-leverage problem, propose solutions, and reason about trade-offs. The classic forms:

• Improve: “How would you improve [product]?”
• Design: “Design a [feature] for [user segment].”
• Diagnose: “Engagement is down 20% — what do you do?”
• Choose: “Should we build X or Y?”

What makes the round hard isn’t the questions — it’s that the interviewer is scoring your thinking process, not your conclusion. Two candidates can propose the same feature; the one who got there through user insight and explicit trade-offs passes, and the one who jumped to the idea fails.

How it’s scored

Interviewers typically score product sense on five dimensions. The best-documented version is Meta’s five criteria for the product sense interview (described by Aakash Gupta and widely adopted as the industry’s default rubric):

1. Motivation — do you show genuine curiosity and drive about products and users?
2. Audience understanding — can you identify and empathize with the specific user?
3. Problem prioritization — do you find the highest-leverage problem, not just any problem?
4. Creative solutions — can you generate strong, differentiated ideas?
5. Design choices — do you reason well about the details and trade-offs of your proposal?

More generally, interviewers across companies look for five underlying signals (the dimensions in Exponent’s product sense rubric): user empathy, structured thinking, product taste, strategic awareness, and communication. Notice what’s missing: domain expertise. The scenarios are deliberately not about insider knowledge — they’re instruments for measuring judgment. The candidate who tries to impress with industry trivia instead of user reasoning is making the classic error.

What “great” looks like on each dimension:

• User empathy: names a specific user with a specific job-to-be-done — not “users” in general.
• Structured thinking: states the structure up front (“I’ll cover users, pain points, solutions, prioritization, and success metrics”) and follows it.
• Product taste: solutions show an opinion about what good feels like, not a laundry list of features.
• Strategic awareness: connects the answer to business context — why this matters for the company, not just the user.
• Communication: crisp, decisive, lands the recommendation. No 10-minute monologues.

The framework: structure first, always

You don’t need a memorized acronym, but you need a skeleton. Use this five-part structure for any product sense question:

1. Clarify and scope. Ask 2–3 sharp questions: which user segment? What goal — engagement, revenue, retention? What’s out of scope? (60 seconds, not 10 minutes.)
2. Users and pain points. Name 2–3 user segments, pick one, and list their top pain points with the product. Rank them by severity × frequency.
3. Solutions. Brainstorm 3–4 solutions mapped to the top pain points. Go for breadth first — this is where product taste shows.
4. Prioritize. Pick one. Say why explicitly: impact vs. effort, strategic fit, risk. Say the trade-off out loud — “I’m choosing B over A because…, even though we give up…”
5. Metrics and risks. Name the one metric that proves success, one guardrail metric, and the biggest risk.

State the structure in one sentence before you start. Interviewers can’t score structure they can’t see.

Self-assessment checklist

After each practice answer, run through these ten yes/no checks. Every “no” is a rep to schedule:

1. Did I state my structure before starting?
2. Did I name a specific user segment (not “users”)?
3. Did I rank pain points instead of listing them?
4. Did I generate at least three distinct solutions?
5. Did I pick exactly one and defend it?
6. Did I state a trade-off out loud — what I’m giving up?
7. Did I name a success metric with a rough target?
8. Did I name a guardrail metric?
9. Did I finish in under 6 minutes?
10. Could a smart non-PM follow my reasoning?

If you’re honest, most early attempts fail checks 6 and 7 — trade-offs and metrics. That’s normal, and it’s exactly why the checklist exists: it turns vague “I should structure better” into two concrete drills to run tomorrow.

15 practice questions

Drill these the way the round works: 5-minute timer, out loud, structure stated up front.

Improve:

1. How would you improve the onboarding flow of a food delivery app?
2. How would you improve Google Calendar for parents?
3. Pick your favorite consumer app. What’s its biggest product flaw, and how would you fix it?

Design:

1. Design a feature that helps Airbnb hosts increase repeat bookings.
2. Design a savings feature for a neobank targeting freelancers.
3. Design a product for elderly users to video-call their families.
4. Design an AI assistant for teachers grading homework.

Diagnose:

1. A social app’s daily active users dropped 15% after a redesign. Walk me through your investigation.
2. Your marketplace’s repeat purchase rate is declining while new user growth is strong. What’s happening?
3. Push notification opt-in rates fell by half after an OS update. Diagnose and propose fixes.

Choose / Strategy:

1. Should a music streaming app invest in podcasts or live audio? Decide and defend.
2. Your company can build either a mobile app or a better mobile website. Which, and why?
3. Should a B2B SaaS company launch a free tier? Argue both sides, then pick.
4. A competitor just copied your flagship feature. What’s your response?
5. How would you decide whether to expand to a new country?

Good vs. great: a worked example

Question: “How would you improve the onboarding flow of a food delivery app?”

A good answer: picks new users, lists three friction points (too many steps, no guest checkout, unclear delivery fees), proposes fixes, prioritizes guest checkout by impact, names activation rate as the metric. Structured, sensible, hireable.

A great answer does all of that plus: questions whether “onboarding” is even the right frame (“is the drop-off a flow problem or an intent problem — are these users actually hungry right now?”); segments by intent (first-time curious vs. referred with a coupon); names the trade-off explicitly (“guest checkout lifts activation but costs us the account relationship — I’d gate the second order on signup, not the first”); and proposes a guardrail metric (fraud/abuse rate on guest orders). Same structure, sharper judgment.

That gap — between sensible and sharp — is what expert rationales train. Reading the difference once is informative; practicing it across dozens of scenarios is what moves your interview performance.

How to practice product sense daily

Product sense is the least crammable interview skill because it’s judgment, not knowledge. The training loop that works:

1. One scenario a day, timed. Five minutes, out loud, structure first.
2. Cross-examine yourself. After answering, argue the opposite. Which stakeholder hates your proposal?
3. Study great answers. For every scenario, read an expert rationale — not to memorize it, but to notice what it noticed that you didn’t.
4. Track the dimensions. Score yourself 1–5 on user empathy, structure, taste, strategy, communication. Your lowest dimension is your study plan.

Product Drills is built for exactly this loop — the Duolingo for PM judgment. Every drill is a 5-minute product scenario with stakeholder perspectives that push back on your answer, a confidence wager that calibrates your Conviction Score, and expert rationales showing what the “great answer” version looks like. Your Skill Heatmap tracks Strategic Thinking and User Research separately, so you always know which muscle needs work.

Try a product sense drill free.

Interviewing at Meta specifically? Their product sense round follows the five criteria above closely — practice naming the user, ranking the problem, and defending one solution with explicit trade-offs. That’s the round in a sentence.