Career
PM Interview Prep Guide
The question types, the frameworks that actually work, what interviewers are evaluating, and the mistakes that eliminate otherwise strong candidates. Written from direct experience on both sides of the table.
Product Sense Questions
Questions about how you think about products — design, improve, prioritize, and evaluate.
Example questions
- •How would you improve Google Maps?
- •Design a product for elderly users to manage their medication.
- •What is your favorite product and why?
What interviewers are evaluating
Whether you start with users before solutions. Whether you ask clarifying questions. Whether your thinking is structured without being mechanical. Whether you can identify the right problem before proposing a solution.
The 4-step product sense approach
Clarify the goal
Ask: what does success look like for the company, not just the user? A product for retention looks different from a product for acquisition.
Define the user
Name specific user segments, not 'all users.' Pick the most important segment and explain why.
Identify user needs
What jobs is the user trying to do? What is frustrating them? Stay in problem space before moving to solutions.
Prioritize and propose
Generate 3 solutions, score them against impact and effort, pick one, and explain the tradeoff explicitly.
Common eliminating mistakes
- ✕Jumping to solutions before defining the user or the problem.
- ✕Treating 'all users' as a valid segment.
- ✕Proposing features without connecting them to user outcomes.
- ✕Not asking a single clarifying question.
Analytical Questions
Questions about how you use data to make decisions, diagnose problems, and measure success.
Example questions
- •Retention dropped 20% last week. Walk me through how you would diagnose it.
- •How would you measure the success of Instagram Stories?
- •We are launching a new feature. What metrics would you track?
What interviewers are evaluating
Whether you can structure ambiguous problems. Whether you know which metrics matter and why. Whether you think about second-order effects. Whether you separate symptoms from root causes.
Metric drop diagnosis structure
Validate the data
Is the drop real or is it a tracking issue? Check for instrumentation errors, timezone bugs, or sampling changes before diagnosing the product.
Segment the drop
Is it across all users or a specific cohort? All platforms or one? All geographies or one region? The segment where the drop is concentrated points to the cause.
Check external factors
Did a competitor launch something? Was there a press event? Did a platform update change behavior? External factors cause many metric movements.
Form and test hypotheses
State two or three specific hypotheses with the data that would confirm or refute each. Do not settle on one hypothesis without testing alternatives.
Common eliminating mistakes
- ✕Jumping to a hypothesis before segmenting the data.
- ✕Forgetting to check for instrumentation or data collection errors.
- ✕Defining success metrics that are not measurable or are vanity metrics.
- ✕Not connecting metrics to user outcomes.
Execution Questions
Questions about how you manage projects, handle tradeoffs, and work with cross-functional teams.
Example questions
- •Engineering says they cannot ship the feature by the deadline. What do you do?
- •Two stakeholders have conflicting priorities. How do you decide?
- •How do you know when a product is ready to ship?
What interviewers are evaluating
Whether you default to data or politics when resolving conflict. Whether you understand the full product development process. Whether you can make hard calls and communicate them clearly. Whether you know what 'done' means.
Execution conflict resolution
Understand all perspectives first
Before proposing a resolution, understand what each stakeholder is optimizing for and why. The conflict is rarely about the stated issue.
Anchor to the shared goal
What is the business outcome everyone agrees on? Reframe the disagreement around that shared anchor before evaluating options.
Propose a criteria-based decision
Suggest evaluating the options against agreed-upon criteria (impact, effort, risk, reversibility) rather than having a debate about opinion.
Own the outcome
A PM who escalates every conflict is not doing the job. State your recommendation, explain the reasoning, and take ownership of the call.
Common eliminating mistakes
- ✕Treating every conflict as needing escalation.
- ✕Proposing compromise as the default resolution (splitting the difference rarely serves the user).
- ✕Not having a clear point of view on what the right answer is.
- ✕Defining 'ready to ship' as 'engineering is done' without addressing measurement.
Strategy Questions
Questions about market thinking, competitive positioning, and long-horizon product decisions.
Example questions
- •Should Spotify enter the podcast creation tools market?
- •What is the biggest threat to Airbnb over the next five years?
- •How would you build a product roadmap for a company entering a new market?
What interviewers are evaluating
Whether you can think beyond the immediate product. Whether you understand business models and competitive dynamics. Whether you can reason about uncertainty without pretending to certainty you do not have.
Market entry evaluation structure
Define the strategic goal
Why would the company enter this market? Is it for revenue, defense, user data, or something else? The goal shapes everything that follows.
Evaluate the market
TAM, growth rate, existing competition, and the specific capability advantage the company brings. Be honest about where the advantage is real and where it is assumed.
Assess the fit
Can the company's existing assets (users, data, distribution, brand) create a defensible position? Or would they be starting from zero against incumbents?
State a clear recommendation
Do not hedge. Say whether you would enter, why, and what the first move would be. Acknowledge the biggest risk in your recommendation.
Common eliminating mistakes
- ✕Analyzing the market without recommending an action.
- ✕Treating all markets as equally attractive without evaluating fit.
- ✕Ignoring the competition or assuming competitive moats are permanent.
- ✕Giving a recommendation without acknowledging the main risk.
Behavioral Questions
Questions about past experience, how you handle setbacks, and what drives your decisions.
Example questions
- •Tell me about a time you had to make a product decision without enough data.
- •Describe a product you shipped that failed. What did you learn?
- •How do you handle a stakeholder who disagrees with your roadmap decision?
What interviewers are evaluating
Whether you can reflect honestly on your work. Whether you learn from failure. Whether you take ownership without blame-shifting. Whether your instincts match the company's culture.
STAR with a twist
Situation (brief)
Set the context in two to three sentences. Do not spend more than 20% of the answer on setup.
Task (your specific role)
What were you personally responsible for? Be specific about your ownership versus the team's.
Action (the interesting part)
What did you actually do? This is where most of the answer should live. Be specific about the reasoning, not just the actions.
Result + reflection
What happened? What would you do differently? The reflection is what separates a story from an insight.
Common eliminating mistakes
- ✕Spending too long on the situation and not enough on the reasoning.
- ✕Using 'we' when the interviewer wants to know what you specifically did.
- ✕Choosing a story with no clear learning or outcome.
- ✕Not preparing stories in advance and improvising under pressure.
3-Week Prep Timeline
The minimum viable prep schedule for someone with limited time and a real interview coming up.
Foundations
- →Study the company's product deeply — use it, read their blog, understand their business model
- →Map the question types you are likely to face based on the company stage and role level
- →Start a story bank: 10 situations from your past that cover failure, conflict, data-driven decision, and cross-functional work
Frameworks
- →Practice product sense questions out loud — not in writing
- →Work through 5 metric diagnosis exercises using public company data
- →Drill your behavioral stories until they are concise and clear without sounding rehearsed
Mock interviews
- →Run at least 3 full mock interviews with someone who will give honest feedback
- →Record yourself answering one question per type and review for filler words and clarity
- →Prepare 5 specific questions for each interviewer based on their role and the product area
Reference
Product Frameworks — RICE, North Star, PMF, ICP and more
Templates
Free PM Templates — PRD, prioritization matrix, user interview guide
Preparing for a PM role at an early-stage company?
PM interviews at early-stage companies are different from those at large tech companies. If you want to think through the specifics, happy to connect.