Product Case Interviews: Product Sense, Metrics and Trade-Offs (2026)

The short answer: product case interviews give you an open-ended problem (“Design a product for…”, “How would you improve…”, “Sign-ups dropped 10%. Why?”) and assess how you think: who the users are, which problem matters most, creative but realistic solutions, how you’d measure success, and the trade-offs you’d make. Meta’s own product manager guide says its Product Sense interview assesses understanding the product landscape, determining the target audience, identifying and prioritizing the problem, and developing creative and impactful solutions, and that you “should be leading the conversation.” Use a clear structure, state your assumptions, and pick a direction. Below are a framework, worked examples and practice questions.

Example answers are illustrations, not quotes from real candidates.

What companies say they assess

Meta’s Product Manager Interview Prep Guide describes 45-minute interviews: an initial screen with Product Sense and Analytical Thinking, and a full loop that adds Leadership & Drive. It lists what interviewers look for:

The guide also says interviewers may ask you to sketch the interface, and that “it’s ok if you don’t know,” encouraging clarifying questions. Other companies’ product interviews follow similar lines.

A framework for product sense questions

1. Clarify the goal. Why would the company build this? Business goal, constraints, platform.
2. Pick users. List segments, then choose one to focus on and explain why.
3. Find their problems. List pain points for that segment and prioritize one or two by impact and frequency.
4. Generate solutions. Three or so ideas, from simple to ambitious.
5. Prioritize. Choose one, using impact, effort and risk, and say what you’d build first.
6. Measure. One primary success metric and a couple of guardrail metrics.
7. Summarize. Recap the user, problem, solution and metric in a few sentences.

A worked example

“How would you improve a fitness app’s experience for beginners?”

• Goal: retain new users past the first month, the riskiest period.
• Users: complete beginners, people returning after injury, and people preparing for an event. Focus: complete beginners, the largest group and most likely to quit.
• Problems: workouts feel too hard, they don’t know what to do next, and they lose motivation when they miss a day. Prioritize: not knowing what to do, which drives the others.
• Solutions: a 10-minute guided starter plan; a check-in that adapts the next workout to how the last one felt; small accountability groups of beginners.
• Pick: the adaptive starter plan; it’s the most direct fix and testable quickly.
• Metrics: primary, the share of new users who complete at least eight workouts in their first 30 days; guardrails, injury reports, plan completion time and uninstalls.
• Summary: “For complete beginners, the biggest problem is not knowing what to do next, so I’d build an adaptive starter plan and measure eight-workout completion in 30 days.”

Metrics and root-cause questions

“How would you measure the success of a feature?”

Start from the feature’s goal, choose a primary metric that captures value to users, add guardrail metrics to catch harm (for example, more time spent but lower satisfaction), and say how you’d test it, often with an A/B test.

“We’ve seen a 10% drop in newly registered users. What would you look at?”

This example comes from Meta’s own guide. A structured answer:

1. Check the data: Is the drop real? Any tracking or logging changes?
2. Scope it: Sudden or gradual? Which platforms, countries, acquisition channels or app versions?
3. Internal causes: a recent release, an experiment, a sign-up flow change, an outage, or a marketing campaign ending.
4. External causes: seasonality, a competitor launch, an app store change, or news.
5. Go down the funnel: visits, sign-up starts, completions, verification. Find the step that dropped.
6. Fix and prevent: roll back or fix the cause, and add an alert for the step.

Trade-off questions

• “Would you prioritize growth or engagement for this product right now?” Depends on its stage and the biggest risk; pick one, explain why, and name what you’d watch on the other.
• “Ship a feature with known bugs before a big event, or wait?” Weigh user impact, severity, reversibility and the cost of waiting, and consider a limited rollout.
• “Two teams want the same engineering time.” Compare expected impact against strategy, effort and risk, decide, and explain the decision to both.

Common mistakes

• Jumping to solutions before choosing a user and problem.
• Listing many ideas without choosing one.
• Vague metrics such as “engagement” without a definition.
• Not stating assumptions, or not leading the conversation.

Practice questions

1. Design a product to help people find volunteering opportunities.
2. How would you improve a ride-sharing app for older adults?
3. What metrics would you use for a messaging app’s group chats?
4. Daily active users of a photo app dropped 5% this week. Why?
5. Should a streaming service add a free ad-supported tier?
6. What’s a product you love, and how would you improve it?

See our product manager interview questions, and for the behavioral round use the STAR method.

Frequently asked questions

Sources

• Meta Careers, Preparing for Your Product Management Interview and the Product Manager Interview Prep Guide linked from it. Read on 1 October 2026.