Product sense is the ability to understand users deeply, think strategically about what a product should do, and communicate your reasoning in a clear, structured way. It is the skill PM interviewers probe most heavily — because it cannot be faked with frameworks alone. You either have a genuine habit of thinking about products critically, or you do not. The good news: it is a skill you can build, and the interview questions that test it are largely predictable.
What product sense actually means
Product sense has three components. User empathy: can you genuinely inhabit the perspective of someone very different from yourself and understand what they need? Strategic thinking: can you connect user needs to business outcomes and make defensible trade-offs? Structured communication: can you take a messy, open-ended question and give a clear, organized answer — not rambling, not bullet-listing without narrative?
The 5 most common product sense question types
Design a product — "Design a product for X." You are being asked to identify a user group, understand their needs, and propose a solution. Improve a product — "How would you improve [app they care about]?" Choose a specific user, a specific pain point, and a specific fix — not a laundry list of features. Favorite product — "What is your favorite product and why?" This tests whether you can articulate product quality in specific, principled terms — not just "it's easy to use." Prioritize features — "You have a backlog of ten features. How do you choose what to build?" Demonstrate a repeatable framework. Metrics — "How would you measure the success of [feature]?" Define a north star, add supporting metrics, and identify what you would not optimize for.
A framework for answering any product sense question
Clarify — Ask one or two clarifying questions to narrow scope before diving in. What stage is the company at? Which user segment? What does success look like? Structure — Tell the interviewer how you are going to approach the answer before you give it. "I am going to start by identifying the user, then the core pain point, then propose a solution and explain how I would measure it." Explore — Work through the problem out loud. Show your thinking, not just your conclusion. Interviewers are evaluating the process. Recommend — Make a clear recommendation. Do not hedge indefinitely. Take a position and explain it. Measure — End every answer with how you would know if your recommendation worked. Name a specific metric.
3 example questions with answer structure
"Design a product for people who want to learn a new language."Clarify: which platform, which languages, what learning style? Structure: identify one specific user (busy professional, 20 min/day), name their biggest barrier (inconsistency), propose a feature (streak + spaced repetition), measure with 30-day retention and weekly active learning sessions.
"How would you improve Spotify?" Clarify: improve for whom — casual listeners, power users, artists? Structure: pick one user (power listeners who explore new music), identify one pain (discovery quality drops after initial novelty), propose a feature (collaborative listening rooms), measure with new artist plays per active user per week.
"What metrics would you track for a new onboarding flow?"Clarify: what is the goal of onboarding — activation, retention, feature adoption? Structure: define activation (user completes first key action), name the north star (% of signups who activate within 7 days), add supporting metrics (drop-off by step, time to first action), name what not to track (raw signups, which are marketing not product).
Common mistakes to avoid
Jumping to solutions before establishing the user — you look like you are feature-pitching, not problem-solving. No user empathy — your answer describes a product, not a person. Vague metrics — "engagement" is not a metric; "daily active users who complete at least one core action" is. Covering too much ground without depth — three well-developed points beat ten shallow ones. Not making a recommendation — wishy-washy answers signal low conviction.
Practice the framework on products you use every day and you will internalize it faster than reading about it. For structured interview prep, explore the interview prep track on NewRoleKit.