CIRCLES breaks the question into seven steps; Sean Ellis's 'very disappointed' segmentation decides whose feedback is worth acting on. Together they make today's real point: picking a segment isn't a throwaway line at the top of an interview answer — it's the first choice that determines which direction every later step of analysis takes. The practice question comes from a real PM mock-interview question bank: design a product that helps elderly users ride public transit independently. The walkthrough shows how to split 'elderly users' into at least two groups with genuinely different failure modes — cognitively sharp but mobility-limited, versus mobile but cognitively declining — and build a different solution and safety net for each. The case is Rahul Vohra's own account, published on First Round Review, of how Superhuman found product-market fit: only 22% of early users said they'd be 'very disappointed' if they could no longer use the product, well below Sean Ellis's 40% threshold. Instead of rushing to change the product, Vohra isolated the users who did say 'very disappointed' and studied what they had in common — that segmentation step alone, before a single feature changed, pushed the score to 32%. Running the same survey-segment-analyze-iterate loop every quarter after that moved the score to 47%, 56%, and then 58%.
The easiest thing to underestimate in a product sense interview isn't coming up with a framework — it's that the five scoring dimensions are graded independently, so one visibly weak dimension drags the whole answer down; a clean structure can't paper over a vague segment. Today's framework is the five-dimension structure from Lenny's Newsletter and former Meta PM Ben Erez — still the industry standard in 2026: clear communication, product motivation, segmentation, problem identification, and solution development, each with its own time budget and common failure mode. The practice question is a real Meta phone-screen prompt from 2026: you're assigned to design a brand-new product connecting home-repair workers with consumers. The walkthrough shows how to avoid stopping at an obvious segmentation like 'homeowners, landlords, contractors,' and instead anchor on the genuinely distinct pain point of 'not knowing which trade to call,' then tie the solution to an asset a pure marketplace doesn't have — Meta's own social graph of neighborhood groups and friend recommendations. The case is Thumbtack's real decision, announced April 30, 2026: its own survey found more than half of homeowners misdiagnose their home problems, and nearly 85% aren't sure which type of professional to call — so Thumbtack replaced its category-first search with a flow where users describe the symptom in text, photo, or voice and let AI infer the right trade. In early testing, 87% of users said describing the problem with a photo or voice felt valuable, and CEO Marco Zappacosta framed the move as 'using AI to rebuild word-of-mouth trust at scale.'
Product Sense interviews fall apart most often at two steps: pain points and solutions. Candidates list three pain points that are really the same complaint in three outfits, then propose three solutions that are really the same idea wearing three different interfaces. Today's drill uses Aced's (formerly Exponent) 2026 six-step framework — clarify, company strategy, pick a user segment, find pain points, brainstorm solutions, define the MVP — and leans on two specific tools for the back half: four pain-point buckets (time, money, motivation, trust & safety) to force three genuinely different root causes, and 'product cuts' (AI/software, hardware, platform/network, ambient, moonshot) to make sure the solution options can each fail independently. The practice question is a real one Meta candidates reported in 2026: 'you've been put in charge of a brand-new product for volunteering — what would you do and why?' The breakdown shows how to narrow 'volunteering' down to a specific segment (young urban professionals who want to volunteer with friends, not alone), and how the real pain point isn't 'can't find opportunities' but a motivation-layer root cause: without someone in the friend group consistently organizing, the second outing never happens. The case study is Peloton's real 2018 decision — its annual member survey found people wanted more variety, but the hardware price tag ($1,995 for the bike, $4,000 for the treadmill) locked out an entire segment that wanted the content without the equipment. Peloton unbundled the workouts into a standalone $19.49/month Peloton Digital app, aiming to push workout completion from 36% past 60%.
The easiest trap in a Product Sense interview is seeing a user segment with great-looking numbers and immediately jumping to 'what should we build for them,' without first asking whether that segment is well-served or just stuck with no better option. Today's practice question: Instacart data shows that subscriber households aged 35-44 with kids order more frequently and spend more per order than other segments, but the app has no interface built specifically for them. The answer runs on a user-problem framework (current state → pain point → root cause → opportunity) that separates 'high frequency and high spend' from 'needs are actually met,' then uses a Reach × Underserved Degree matrix to judge where this segment really sits on the priority list — so a segment that already looks strong doesn't get mistaken for one with a big open opportunity. The case study is Airbnb Categories: in 2022, Airbnb rebuilt its homepage search around 56 niche lodging themes — treehouses, castles, private islands — using ML plus human review to sort four million of its six million listings into them, successfully surfacing demand nobody knew to search for. But after Airbnb expanded into Homes, Experiences, and Services as three separate product lines starting in 2023, Category search's single-product assumption stopped holding, and Airbnb retired it in September 2025, reverting to a traditional search box plus three tabs.
The easiest way to fail a Product Sense question isn't running out of ideas — it's being unable to explain, with specifics, why you'd build this feature before that one when resources are tight. Today's practice question is real: 'A social app is gaining traction with teens but has limited engineering bandwidth. As the PM, prioritize these potential features: stories, events, profiles, messaging, analytics.' The answer still runs on CIRCLES — clarify the context and constraints, identify the users, surface their real needs, list the options — but this time the Cut-to-Ladder step gets replaced with RICE scoring: Reach (how many users this touches), Impact (how much it changes their experience), Confidence (how sure you are about those estimates), and Effort (engineering cost), multiplied and divided into one number that turns 'this feels more important' into something a reviewer can challenge and reproduce. The case study is Intercom itself — RICE is the framework PM Sean McBride published on Intercom's own blog in January 2018, built specifically because the team's roadmap debates kept getting won by whoever argued loudest, not by whichever idea actually mattered most.
The most common way Product Sense interviews go wrong isn't a lack of ideas — it's jumping straight to a feature list before pinning down where users are actually stuck. Today's scenario is a real interview question reported by a Rox candidate: 'Our analytics dashboard shows users a lot of data, but we suspect many aren't deriving actionable insights from it. What would you do?' The answer framework is CIRCLES: comprehend the situation and constraints, identify the users you're serving, report their real needs, cut a list of solutions, ladder them by trade-off, and evaluate by defining what success looks like. The case study is ConvertKit — a bootstrapped creator-newsletter SaaS that grew to roughly $41M ARR — which found that creators staring at a generic, one-size-fits-all report page had no idea what to do next. In August 2021 it redesigned the dashboard into a per-account summary of subscriber growth, email performance, and deliverability, turning 'having data' into 'having a next action.'
The most common Product Sense trap is jumping straight to a list of new features the moment you hear 'growth has stalled,' without first figuring out which part of the funnel is actually broken. Today's drill uses the CIRCLES framework on a case where a grocery delivery app's new signups keep growing steadily but weekly active users (WAU) have been flat for two straight quarters. The answer framework starts by using the funnel to locate the broken stage, then digs deeper with a user-problem framework (current state → pain point → root cause → opportunity) before proposing any solution. The case study is Slack mining its own behavioral data to find that teams crossing 2,000 messages sent had a 93% chance of long-term retention — an insight that reshaped Slack's entire onboarding strategy, from 'teach users every feature' to 'get teams past the activation threshold as fast as possible.'
The most common way to fumble a Product Sense question isn't running out of feature ideas — it's skipping past "who is this user and what are they actually stuck on" and jumping straight to a feature list. Today we use the CIRCLES framework on a real Google PM interview question — "You're the PM for Waymo, design a new feature" — with the focus on the Comprehend and Identify steps: asking the right questions before proposing anything. The case study is how Slack grew out of an internal tool the team couldn't live without while building a failed game called Glitch — a demonstration that watching what users actually keep using beats asking them what they want.
The most common way to fumble a Product Sense question isn't running out of ideas — it's segmenting too broadly and getting stuck on vague statements like 'all travelers want a smoother experience.' Today we use CIRCLES to scope the question, then layer JTBD (Jobs-to-be-Done) on top so pain points get written as 'situation + motivation + what's missing from the current workaround,' practicing the 'design a product for airport travelers' prompt that shows up in Google's product sense screen. The case study is Rahul Vohra's four-question survey — 'how would you feel if you could no longer use this product?' — which took Superhuman's product-market fit score from 22% to 58%, demonstrating how concrete segmentation beats gut-feel guessing.
Product Sense questions rarely fail because you can't think of a feature — they fail because you can't say why that feature, and not another. Exponent's latest 2026 real-interview roundup notes an Adobe candidate was asked to 'design a feature for LinkedIn,' and the strongest answers all committed to one user segment early instead of listing ten ideas. Today we pair CIRCLES with a root-cause layer to work through that question, using Airbnb's early 'photograph hosts' listings by hand' move as the case study.
Product Sense interviews don't test how many features you can brainstorm — they test whether you can turn a vague prompt into a behavior-driven diagnosis. In a real Google HC debrief, a candidate who pitched 12 YouTube features got rejected because 'they described what, not why.' Today we use the CIRCLES framework to break down a senior-user search experience problem, with Superhuman's story of raising their product/market fit score from 22% to 58% using a four-question survey as our case study.
AI pushes execution cost toward zero. People with good taste create more value; people with poor taste create more garbage. The difference is not whether you can use AI, but whether your mind contains something worth amplifying before you use it. This series documents my attempt to sharpen judgment systematically.
Product Sense interviews don't test how many features you can think of — they test whether you can find the problem truly worth solving within a vague requirement. Core skills: user segmentation thinking, problem reframing (turning 'add a feature' into 'what problem are we solving'), structured reasoning for feature prioritization, and the ability to hold or revise your judgment under follow-up questions.