The definitive guide to mastering product sense interviews

Ben Erez, a former Meta PM and interview coach, presents a structured playbook for product sense interviews, which are now common across major tech companies. He explains that interviewers look for clear signals across five dimensions: communication, product motivation, segmentation, problem identification, and solution development, and that weakness in one area cannot be offset by strength in another. The post walks through each dimension with worked examples for sample prompts, along with common pitfalls and practice drills. Its main value is making an opaque interview format legible, so candidates can practice deliberately rather than guess at what a good answer looks like.

01Key takeaways

• State 2-4 assumptions and a game plan at the start, then confirm the interviewer agrees before diving in.
• Treat each dimension as a must-pass; a strong score in one area cannot compensate for a weak one elsewhere.
• Separate user needs (desires) from problems (specific obstacles) and prioritize by both severity and frequency.
• Build segments on motivations and context rather than demographics, and check that they are mutually exclusive.
• Brainstorm several genuinely different solutions and justify your pick with impact versus effort reasoning.
• Practice with a reusable template and time each section so you finish the full framework within the session.

02Key sections

What the interview measures

Product sense interviews run about 45 minutes and score candidates on five dimensions, each needing at least a passing mark. The author stresses that interviewers are busy and want easy-to-identify signals.

Clear communication

Candidates should state assumptions, lay out a game plan for the session, and check in with the interviewer before proceeding. Waypointing between sections keeps the interviewer oriented.

Product motivation and segmentation

Strong answers connect a product to deeper human needs and its strategic context, then map the ecosystem and define meaningfully different, mutually exclusive segments. One segment is chosen and brought to life as a persona.

Problem identification and solutions

Candidates map a day-in-the-life journey for the persona, distinguish needs from problems, and prioritize by severity and frequency. They then brainstorm several distinct solutions, weigh impact against effort, and define a concrete v1 with risks and mitigations.

Pitfalls and practice

Common mistakes include thinking out loud without structure, premature narrowing, shallow segmentation, confusing needs with problems, and solution jumping. The post closes with drills such as templates, mutual-exclusivity tests, and impact-effort grids.

03From the post

“Annual subscribers now get a free year of Perplexity Pro, Notion, Superhuman, Linear, and Granola. Subscribe now. A lot of you are having a hard time finding a job. I hear stories from readers who send out hundreds of resumes and get zero responses, go through month-long interview loops that often end in getting ghosted, and continue on without ever hearing honest feedback about what they could do differently. I want to help. In the coming months, I’m going to be sharing a number of newsletter posts with the goal of helping you find a job you love. Today’s post is the first in that series, and it’s a doozy. The product sense interview is one of the most important and most mysterious steps of the PM interview loop, and Ben Erez just wrote your new bible for mastering that interview. Ben shares exactly what the product sense interviewer is looking for, a simple framework for structuring your answer in real time, how to practice for these interviews, and even specific phrases you should be using. If you read this…”

04Frameworks mentioned

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.