"Product sense" might be the most anxiety-inducing phrase in PM interviews. It sounds like something you either have or you don't. Like taste. Like intuition. Like some innate quality that interviewers can detect and candidates can't practice.
After 200+ interviews, I can tell you: that's wrong. Product sense is a collection of specific, observable skills. Interviewers score it on rubrics with defined criteria. And you can get meaningfully better at demonstrating it in a matter of weeks.
Let me show you what's actually on the scorecard.
What are interviewers actually scoring when they evaluate product sense?
Every company has a slightly different rubric, but after comparing notes with interviewers at Google, Meta, Stripe, Airbnb, and a dozen mid-stage startups, the same five dimensions show up consistently. Interviewers might use different labels, but they're looking at the same things.
1. User empathy
Can you step into the user's shoes with enough specificity that it's clear you've actually done it before? This is the difference between "users want a faster experience" and "the person using this at 6am on the train with one hand, half-paying attention, needs to complete this action in under three taps or they'll close the app."
What a high score looks like: The candidate names a specific user segment, describes their context (when, where, why they're using the product), and identifies a pain point that isn't obvious from the surface. They've clearly spent time with real users or been one themselves.
What a low score looks like: The candidate says "users want simplicity" or "the target audience is millennials aged 25-35." These are demographic descriptions. They don't demonstrate empathy. They tell the interviewer nothing about whether you understand what the user actually feels.
2. Problem framing
Before you jump to solutions, can you articulate the problem in a way that reveals its structure? Strong problem framing means identifying the root cause underneath the symptom, understanding who's affected and how severely, and defining what success looks like before proposing what to build.
I once asked a candidate how they'd improve Spotify's podcast experience. Within 30 seconds, they were pitching features. No discussion of what's actually broken. No clarity on which podcast listener they were solving for (casual vs. power listener, that distinction matters enormously). They jumped straight from question to solution, and the solution was generic because the problem was undefined.
3. Prioritization logic
This one trips up candidates who are otherwise sharp. You generated five good ideas. Great. Now which one do you build first, and why? Interviewers want to see a clear, defensible rationale for prioritization. RICE, ICE, effort/impact matrices: these frameworks are useful here. The key is that your prioritization has to connect to the problem you framed and the user you identified.
When candidates prioritize based on "this would be a quick win" without explaining for whom or against what goal, it signals shallow thinking. When they say "I'd prioritize the content calendar feature because our power creators (top 5% by posting volume) told us in research that inconsistency is their biggest growth blocker, and this segment drives 60% of platform content," that's prioritization with teeth.
4. Business awareness
Can you connect user value to business value? This is where many candidates, especially those from design or engineering backgrounds, leave points on the table. You don't need an MBA. You need to demonstrate that you understand the company makes money, that your proposed feature has to fit into a business model, and that tradeoffs exist between user delight and business sustainability.
What a high score looks like: "This feature increases creator retention, which drives content supply, which is Spotify's primary moat in podcasting. The business case is that each retained creator represents roughly X hours of exclusive content per month." The candidate connects user value to a business lever the interviewer cares about.
5. Conviction
This is the one nobody talks about, and it might matter most. After walking through your analysis, do you actually believe in your recommendation? Or are you hedging with "it depends" and "we'd need to test this"?
Yes, humility is good. Yes, data-driven decision making is important. But in an interview, the ability to take a stance and defend it is a signal of product leadership. The best candidates I've interviewed say things like: "Based on everything I've laid out, I'd build X first. Here's what would make me wrong, and here's how I'd validate it quickly." That combination of conviction and intellectual honesty is incredibly compelling.
Is product sense something you can actually practice?
Yes. Full stop. Here's why people think you can't: the candidates who demonstrate strong product sense make it look effortless. Their answers flow naturally. They seem to just "get it." What you don't see is the hundreds of hours they've spent analyzing products, forming opinions, arguing those opinions with peers, and refining their thinking.
Product sense is a muscle. You build it by using it. Specifically:
- Use products critically. Every app you open is a case study. Why did they put that button there? What metric are they optimizing for? What would you change? Form an opinion, then try to argue against it.
- Read product teardowns. Lenny's Newsletter, Stratechery, product Twitter. Absorb how experienced PMs think about product decisions, then practice applying the same lens yourself.
- Practice the full loop. Don't just practice answering questions. Practice identifying users, framing problems, generating solutions, prioritizing, and defending your choice. The full sequence is what interviewers evaluate.
- Get real follow-up pressure. Product sense shows up most clearly when someone asks "why?" three times in a row. If your practice doesn't include aggressive follow-ups, you're training for the wrong test.
What does a product sense interview question actually look like?
Here's a real question I've used: "How would you improve Google Maps for tourists?"
Most candidates immediately start listing features. Offline maps (already exists). Restaurant recommendations (already exists). Itinerary planning (already exists). They're brainstorming from a position of ignorance, and it shows.
Here's what a strong product sense answer looks like in the first 90 seconds:
I want to narrow down what kind of tourist we're talking about, because the needs are very different. A backpacker navigating Bangkok for the first time has different problems than a family visiting Paris for a week. Let me focus on the solo international traveler in an unfamiliar city, because I've been that user recently and I have strong opinions about what's broken. The core problem isn't missing features. It's that Maps treats me the same whether I live here or arrived yesterday. Every recommendation is optimized for locals. The search results, the suggested routes, the place rankings. There's no concept of "I've never been here before and I don't know what I don't know."
Notice what happened. The candidate narrowed the user segment. They drew on personal experience. They identified a structural problem (the product doesn't differentiate between locals and tourists) rather than a surface symptom. And they showed conviction: "I have strong opinions about what's broken." That's product sense in action.
How do you score high on all five dimensions at once?
The good news is that these five dimensions are interconnected. When you start with genuine user empathy, your problem framing gets sharper. When your problem framing is sharp, your prioritization becomes more defensible. When your prioritization is defensible, you can connect it to business value more naturally. And when the whole chain holds together, conviction comes easily because you actually believe what you're saying.
The chain breaks when you skip the first step. If you start with generic users ("millennials who want convenience"), everything downstream is generic too. That's why the candidate who talks about their own experience as a tourist in Bangkok sounds more convincing than the candidate who hypothetically imagines what tourists might want.
Before your next practice session, write down three products you've used in the last week where something frustrated you. Those frustrations are product sense gold. They give you real user empathy, a genuine problem to frame, and the conviction that comes from caring about the answer.
Why does product sense matter more in today's market?
With over 500,000 tech workers laid off between 2022 and 2024, the PM candidate pool is deeper and more experienced than it's been in years. Companies are being pickier. When you have 30 to 40 qualified applicants for every entry-level PM role, interviewers can afford to filter aggressively on product sense because it's the hardest thing to fake.
You can memorize frameworks in a weekend. You can rehearse behavioral stories in a week. But demonstrating genuine product sense requires you to have actually spent time thinking deeply about products. That's why it's the dimension where interviewers put the most weight. It's the best proxy for how you'll actually perform on the job.
The stakes are high, too. Senior PM compensation has risen 13% between 2023 and 2025, with Group PM roles jumping 25%. The financial gap between getting the offer and getting the rejection keeps widening. Investing time in building real product sense pays off in a very literal sense.
Product sense is specific, scorable, and practicable
If you walk away with one thing, let it be this: product sense is not a vibe. It's not a gut feeling the interviewer has about you. It's a structured evaluation of five specific skills, each of which you can improve with deliberate practice.
User empathy. Problem framing. Prioritization logic. Business awareness. Conviction. Score well on all five, and you'll hear "strong hire" more often than you expect. Score poorly on even one, especially user empathy or conviction, and it drags the whole assessment down.
The candidates who seem to have natural product sense? They just practiced it before you did.
Practice product sense with real follow-ups Try it free →
PM Interview Copilot scores your answers on the same dimensions interviewers use.