How to Answer Product Sense Questions
No matter which type of product sense question you face, you can apply the same six-step framework. The steps must be answered in order. Each one constrains the next.
- Clarifying questions: understand what you're being asked to build before designing anything
- Strategy: the company's mission, competitive landscape, and why this opportunity exists right now
- User types: segment the user base and select one group to design for
- Pain points: identify the specific friction your user experiences and the root problem to solve
- Solutions: generate meaningfully different ideas that map to the pain point
- MVP: define the smallest version that delivers real value and name what waits
This lesson will work through our framework from end-to-end on a confirmed recent OpenAI interview question: "You have technology that can allow humans to understand animals. What do you do?"
Step 1: Clarifying questions
Why this step matters: You cannot design for something you do not understand, especially on novel technology prompts where the technology itself is undefined.
Your goal: Ask two kinds of questions. First, questions about the question: define all terms, understand how the technology works, ask about fidelity and mechanics. These are never assumptions. Second, questions about product context: company size, market, timeline, scope. State these as assumptions and confirm rather than asking the interviewer to decide for you.
The interviewer clarifies after each question: vague emotional states only, things like happy, calm, or uncomfortable, not precise thoughts or language. Requires a wearable sensor.
This answer changes everything. The product cannot translate the exact meaning or intent. It can only surface whether the animal is responding positively or negatively to something.
Design into that constraint, say: "I am going to assume we are at OpenAI and not a startup, going after the US market, with a fully staffed team and a goal to ship in the next 3-6 months. Does that sound right?"
Step 2: Strategy
Why this step matters: This is where your product sense shines. You demonstrate your strategic thinking, knowledge of different markets and trends, and why this company, specifically, would build this thing.
Your goal: Communicate strategic thinking and align on a goal. To do so, pick the pieces most relevant to the problem: company mission, company strategy, why they would build this, given their mission and philosophy, the mission for what you are building, and a high-level metric goal. You do not need all five.
Cover the mission and pick a north star metric. Keep it to 1-2 minutes.
Step 3: User types
Why this step matters: User segmentation is a critical skill all PMs must have. Interviewers want to see you thoughtfully select a distinct, well-defined user segment to help identify unique pain points for the conversation.
Your goal: Don’t choose segments that could apply to any product. Segment by what this technology specifically enables. Then prioritize one group. Good prioritization criteria: who has the most acute pain this technology solves, who is the best fit for the company's mission and strategy, who has the clearest path to willingness to pay, and which segment gives you the best signal on whether the core product works. Pick one and make the rationale explicit.
Step 4: Pain points
Why this step matters: Interviewers are looking for evidence that you can genuinely understand the people you're building for. Not just name a problem, but feel it. That kind of empathy is a real product skill, not just an interview move. And the depth you bring here determines the quality of everything that follows: shallow problem definition produces shallow solutions.
Your goal: Start by painting a picture of what it is to be this user. Walk through their life with this animal: their daily routines, what they care about, what they worry about, what they wish they knew. The problems should surface naturally from that portrait, not from a checklist. Aim for at least three distinct pain points, then prioritize one.
Step 5: Solutions
Why this step matters: This is where product taste shows. A list of features is not brainstorming. Generate at least three meaningfully different ideas that map directly to the problem, and show genuine excitement about at least one.
Your goal: After generating ideas, prioritize explicitly. Good prioritization criteria: which solution most directly addresses the root pain point you identified, which is feasible given your assumptions about team and timeline, which is most differentiated from what already exists, and which best maps to the north star metric from Step 2.
The real-time check-in is the strongest starting point: it is directly feasible with vague emotional signals, it creates a daily habit, and it addresses the core pain without requiring behavioral modeling we cannot yet do reliably. Departure detection is compelling but requires enough data to establish a baseline first. The moonshot is the long-term vision.”
Step 6: MVP
Why this step matters: Anyone can list features. This step is about judgment, which is essential before anything else, and which should wait.
Your goal: Start with the prerequisite. What must be true before this product can work at all? Then define the smallest version that delivers real value. Name what you are cutting and explain why specifically. Vague deprioritization signals avoidance. Specific deprioritization signals judgment.
Prioritization: “A consumer app paired with the collar wearable that shows the owner a simple emotional read on their pet while they are away. Calm or distressed, updated throughout the day, with a rough sense of when and how long distress episodes last. Start with dogs. Cat support and departure pattern detection come after the core signal is validated. The question the MVP answers: Is the read reliable enough that owners actually trust it and change their behavior based on it?”
Showing the MVP
Why this step matters: At this point in the interview, many interviewers want to see your design sense, not just your product thinking. Showing the product, even roughly, demonstrates that you can translate a concept into something real and that you have a point of view on what the experience should actually feel like.
Your goal: Surface the most important and interesting parts of the product. This is not about completeness. It is about choosing the right screen or moment to show and making every design decision visible and deliberate.
Drawing vs. Vibecoding the MVP:
If the interviewer asks you to sketch or draw, use a whiteboard or paper to show the core screen or user flow. Focus on the one or two moments that carry the most product value, not a full UI walkthrough.
If the interviewer asks you to prototype, the key is that you should have been taking notes throughout the interview. Copy and paste those notes directly into Claude and give it a specific, well-structured prompt. The quality of your prototype is largely determined by the quality of your prompt.
Insider insight: Across transcripts from the Meta AI Product Sense round, the candidates who struggled most tried to build something polished. The ones who advanced thought out loud about system tradeoffs, started functioning fast, and proactively discussed production-readiness before being asked. Interviewers followed up with questions about token usage, latency, and retrieval strategy, so narrating your choices as you build is part of the signal. Candidates who had practiced with Cursor, Claude Code, or Lovable beforehand had a meaningful advantage. As one candidate put it: "I had already practiced with Cursor and Claude Code. I work at an AI startup. But I had never been asked that in an interview before, and now it's definitely becoming the norm."
Example prompt:
"You are a senior product designer building a mobile app prototype. The product is a consumer app for dog owners that shows them whether their dog is calm or distressed while they are away from home. The emotional data comes from a collar wearable.
Build two screens: (1) a home screen showing the dog's current emotional state (calm or distressed) with a timeline of emotional states throughout the day, and (2) a notification or alert screen that surfaces when a distress episode starts or ends. Design principles: warm, clean, consumer iOS feel. Should feel like a real app a pet owner would actually use, not a dashboard."
Walk through every decision as you present it: why those two screens, what the empty states would look like, what happens when the dog is consistently calm vs. when distress spikes. The prototype is a prop. Your narration is the interview.
Common pitfalls
Under-asking on novel technology prompts. "Read minds" is undefined until you define it. The questions you ask are part of the signal on novel tech questions.
Skipping strategy. Most candidates jump straight to users. Two minutes on mission and a competitive position make everything downstream feel grounded rather than generic.
Generic segmentation. Segments that could apply to any product signal, you have not thought carefully about what this specific technology enables.
Treating the question as the end of the round. Ethical follow-ups are standard on novel technology prompts. OpenAI has a dedicated legal/ethics round with questions like "How do you prevent reinforcing harmful biases?" and "Design the safeguards for an AI that takes actions on the user's behalf." At Meta, product sense rounds almost always shift into a conflicting-metric trade-off: metric A is moving in the right direction, metric B is moving in the wrong direction, what do you do? This appeared in nearly every Meta loop analyzed, making it the dominant analytical follow-up in 2026. Prepare for both transitions.