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.