Product sense is not about having a lot of product ideas. It is about having structured judgment. Interviewers are not looking for creativity or innovation. They want to see that you can quickly understand users, identify the right problem to solve, make reasoned trade-offs, and define what success looks like.
Candidates who walk into product sense interviews thinking they need to impress with bold ideas consistently underperform. Candidates who think rigorously and show their reasoning consistently do well, even with mundane solutions.
What Product Sense Actually Tests
At its core, product sense is three things:
User empathy: Do you understand that users are not a monolith? Can you identify specific user segments with specific needs, rather than designing for everyone at once?
Prioritization judgment: When you have multiple problems to solve and multiple solutions to choose from, can you make reasoned trade-offs? Do you explain why you chose one over another?
Business awareness: Do your product decisions connect to the product's business model and goals? PMs who design features that users love but that hurt revenue, retention, or margins are not demonstrating strong product sense.
The Jobs to Be Done framework is one of the most useful mental models for developing user empathy quickly. It asks: what is the user actually trying to accomplish, and what functional, social, and emotional dimensions does that job have?
The 4-Step Framework
Use this structure for every product sense question. It takes practice to execute in 30 minutes, but it works reliably once internalized.
Step 1: Understand the Users
Before proposing anything, define who you are designing for. Identify 2-3 user segments. Pick the highest-value one to focus on (with reasoning). Build a quick mental model of their goals, pain points, and current behavior.
Do not say "users want X." Say "the specific segment I am focusing on, frequent business travelers who fly 4+ times per month, experience X pain because Y."
The product discovery guide covers the qualitative research techniques that inform this kind of rapid user modeling.
Step 2: Define the Problem
State the problem you will solve clearly, specifically, and from the user's perspective. A good problem statement: "Business travelers waste 15-20 minutes per trip selecting seats that match their real preferences, because airline apps surface seat maps before the traveler can filter by their priorities (window, aisle, exit row)."
A weak problem statement: "The booking experience is frustrating."
Specific problem statements generate specific solutions. Vague problem statements generate generic ones.
Step 3: Ideate Solutions
Generate 3 distinct solutions. They should address the same problem but in materially different ways. This shows you can actually think across the solution space, not just implement the first thing that comes to mind.
For each solution, note the key assumption it rests on. The best solutions are ones where the core assumption is both likely to be true and testable.
Step 4: Prioritize and Define Success
Pick one solution and explain your reasoning using explicit trade-offs. Then define your success metrics: what is the primary metric, what are the guardrail metrics, and what does a successful launch look like in 90 days?
Use the RICE framework as a mental model during this step. You do not need to calculate RICE scores out loud, but thinking through Reach, Impact, Confidence, and Effort will sharpen your prioritization reasoning.
8 Product Sense Questions with Answer Structures
Question 1: "Design a feature for Spotify to help users discover new music."
Answer structure:
Users: Casual listeners (70% of base, mostly playlist consumers) vs. music enthusiasts (smaller but more engaged, actively seek new music). Focus on the casual listener because the discovery problem is more acute for them and the market size is larger.
Problem: Casual listeners want to feel pleasantly surprised by new music, but discovery recommendations feel like work (new playlists to evaluate, unfamiliar artists). The core job is "find music I would love without having to think about it."
Solutions: (1) Blend new artists into existing favorite playlists with a 10-15% injection rate, labeled as "new for you." (2) Weekly 15-minute podcast-style show hosted by AI summarizing the listener's taste and playing 3-4 new artists. (3) "Discovery mode" toggle on any existing playlist that substitutes 30% of songs with similar-artist alternatives.
Priority: Option 3, because it meets users where they are (existing playlists), has low friction (one toggle), and can be tested with a small experiment. Success metric: 7-day listening rate on new artists discovered via Discovery Mode.
Question 2: "How would you improve LinkedIn for job seekers?"
Answer structure:
Users: Active job seekers (updating resume, applying daily) vs. passive candidates (open to opportunities but not actively hunting). Focus on active seekers because their pain is highest and they are most likely to attribute value to a specific LinkedIn improvement.
Problem: Active seekers waste significant time on applications that go nowhere because they cannot assess likelihood of response before applying. The core pain is applying blindly.
Solutions: (1) "Response likelihood" score for each job posting based on historical data (company response rate, posting age, role competition). (2) Direct connection to current employees at the company before applying, with AI-generated introduction. (3) Application tracker with automated follow-up reminders.
Priority: Option 1, because it solves the highest-friction problem (wasted applications) at scale without requiring behavioral change from users.
Question 3: "What would you build next for Google Maps?"
Answer structure:
Users: Daily commuters (high frequency, route-established), travelers (exploratory, planning-heavy), local explorers (seeking nearby experiences). Focus on local explorers because Google Maps has the weakest product experience for serendipitous discovery versus navigation.
Problem: Explorers want to find interesting things nearby but Maps optimizes for getting somewhere specific, not for discovering what is worth going to. The search experience requires you to already know what you want.
Solutions: (1) "Mood-based" discovery (show me something active, relaxing, or social nearby, based on time of day and past behavior). (2) Friend social layer (see where your connections have been recently and what they rated). (3) AI-generated "local story" for any neighborhood, surfacing the three most interesting things within walking distance.
Priority: Option 1, because it is differentiated from Yelp and TripAdvisor (which require search intent), testable with a small surface area, and builds on Google's existing behavioral data.
Question 4: "Design a new product for senior citizens who want to stay connected with family."
Answer structure:
Users: Seniors vary by tech comfort. Focus on low-tech users (65-80, smartphone owners but not power users) because the connection problem is most severe for them and this segment is underserved.
Problem: Low-tech seniors want to feel connected to family without the anxiety of technology. Current tools (FaceTime, WhatsApp) have too many steps, notifications they cannot manage, and interfaces that change without warning.
Solutions: (1) A dedicated device with one-touch video call to pre-saved family members. (2) A photo-sharing app that automatically sends a family member's latest photos to a digital frame in the senior's home without any action required from the senior. (3) A simplified messaging app with voice-to-text input and large UI with no configurable options.
Priority: Option 2, because it requires zero technology learning from the senior (the family member opts in and the photos flow automatically), has no failure mode for the senior, and creates a daily touchpoint that does not require initiation.
Question 5: "How would you improve Airbnb for first-time guests?"
Answer structure:
Users: First-time guests face trust and certainty problems that repeat guests have already resolved. The key pain is the unknown, arriving at a stranger's home without knowing what to expect.
Problem: First-time guests experience anxiety between booking confirmation and check-in because the information they need (parking, entry instructions, neighborhood norms) is scattered, arrives at different times, and sometimes does not arrive at all.
Solutions: (1) Standardized pre-arrival checklist automatically compiled from host info, sent 48 hours before arrival. (2) "First stay" badge and matching with hosts who have high ratings from first-time guests. (3) In-app arrival guide with neighborhood overview, parking map, and entry instructions assembled from structured host data.
Priority: Option 3 because it addresses the trust gap with structured information (not dependent on host communication quality) and creates reusable content that persists as a product feature.
Question 6: "Design a new feature for Slack to reduce meeting overload."
Answer structure:
Users: Knowledge workers in medium-to-large companies who spend 4+ hours per day in meetings and use Slack to coordinate. The specific pain: unnecessary meetings that could have been async.
Problem: Meeting organizers default to synchronous meetings because async alternatives in Slack (long message threads, voice notes) require too much effort to set up and do not create a clear decision record.
Solutions: (1) "Meeting alternative" button when creating a calendar event that converts the agenda into an async Slack thread with a deadline. (2) AI-powered meeting summarizer that turns a Slack thread into a formatted decision doc. (3) "Needs decision by" message type that prompts stakeholders to vote or respond by a specific time, with automatic escalation if they do not.
Priority: Option 3 because it creates a new communication pattern (async decision requests) that is genuinely different from existing Slack message types and gives organizers a path besides "schedule a meeting."
Question 7: "How would you improve Duolingo for advanced language learners?"
Answer structure:
Users: Advanced learners who have passed the beginner and intermediate content. Their problem is different from new users: they are not learning structure anymore, they are trying to achieve fluency.
Problem: Advanced learners stall in Duolingo because the gamified lesson format does not build real conversational fluency. They can pass tests but cannot hold a natural conversation.
Solutions: (1) AI conversation partner that simulates real conversations with native speaker pacing and colloquialisms. (2) Native content integration (news articles, podcast clips in the target language with comprehension exercises). (3) Story-based missions where the learner has to use the language in a simulated real-world scenario (ordering at a restaurant, negotiating a price) with adaptive AI responses.
Priority: Option 1 because conversational practice is the highest-value unmet need, the AI technology now makes it feasible, and it directly addresses the fluency gap that advanced learners identify as their core problem.
Question 8: "What is your favorite product and how would you improve it?"
This is a trap question for underprepared candidates. Do not pick a product you know superficially or one you cannot critique honestly.
How to answer:
Pick a product you genuinely use. Have a real improvement in mind, not just a feature you wish existed. Walk through the same 4-step framework as any other question: who specifically has the problem, what is the problem, what are possible solutions, and which would you prioritize.
The evaluation is not about whether your favorite product is impressive. It is about whether you can think like a PM about something you care about. Authenticity and specificity matter more than choosing a high-status product.
Building Product Sense Over Time
Product sense develops through deliberate practice, not passive experience. Read product teardowns. Use the PM certification to build structured knowledge of the frameworks product sense draws on. Practice questions out loud with a timer. Do product critiques of every app you use for more than 5 minutes per day.
The candidates who do best in product sense interviews have internalized this kind of thinking so deeply that it is no longer an exercise. They just think this way about products naturally.