Questions covering product strategy, prioritisation, stakeholder management, and data-driven decision making.
Structure your answer as: Problem identified, approach taken, cross-functional collaboration, launch outcome, and metrics.
Strong answers show end-to-end ownership: identifying the opportunity, defining requirements, working with engineering and design, making trade-offs, launching, and measuring results. Look for specific metrics (adoption, revenue, retention) rather than vague claims of success.
Establishes baseline PM experience. Watch for whether they describe their role specifically or take credit for team efforts. Ask "What would you do differently?" to assess self-reflection.
Name your framework, show how you gather data for it, and explain how you communicate "no" to the stakeholders whose items are deprioritised.
Look for a structured framework: RICE, MoSCoW, value vs effort matrix, or custom. Best answers combine quantitative signals (impact estimates, user data) with qualitative input (strategic alignment, customer interviews). Candidates should mention communicating decisions and managing disappointed stakeholders.
Core PM skill. Red flags: purely gut-driven decisions, or purely data-driven without strategic thinking. Best candidates balance both and explain their reasoning clearly.
Define your north star metric, 2-3 supporting metrics, and at least one guardrail metric before you launch anything.
Strong answers define a metric hierarchy: north star (activation rate), leading indicators (step completion rates, time-to-value), and guardrail metrics (support tickets, drop-off rates). Candidates should mention A/B testing methodology, statistical significance, and setting targets before launch.
Tests analytical rigour. Weak candidates pick vanity metrics. Strong candidates think about what "good" looks like before measuring, and account for potential negative side effects.
Frame your answer around reversibility and learning: a quick version to validate demand is different from a quick version that creates permanent debt.
Best answers explore context: what is the urgency? Is this a one-way door or reversible? What technical debt would accumulate? Can we ship the quick version to validate demand, then invest properly if it works? Look for nuanced thinking rather than always choosing speed or always choosing quality.
Reveals how the candidate partners with engineering. Do they respect technical concerns? Can they think in terms of sequencing (validate, then invest)? Red flag: always defaulting to speed without considering consequences.
Show three versions of the same roadmap: outcome-focused for leadership, detailed for engineering, and problem-focused for customers.
Strong candidates tailor their message: executives care about strategic alignment and business outcomes, engineers need technical context and "why", customers want to know how their pain points will be addressed. Best answers mention the difference between commitment and exploration, and how they handle roadmap changes.
Senior PM skill. Tests communication range and stakeholder empathy. Ask follow-up: "What do you do when the roadmap changes significantly mid-quarter?"
Be honest about what you got wrong, not just external factors. Show how the failure changed your approach going forward.
The best answers show genuine accountability, not blaming others. Look for: what signals they missed, how they identified the failure, what they did about it (pivot, sunset, iterate), and specific lessons applied to future work. Candidates who claim no failures lack self-awareness.
Crucial question. Ability to fail, learn, and iterate is core to product management. Red flag: blaming engineering, market timing, or stakeholders without self-reflection.
Frame "no" as "not now" or "here is what we can do instead" - always offer an alternative path forward.
Strong answers show courage with diplomacy: acknowledged the stakeholder's perspective, explained the reasoning with data, offered alternatives, and maintained the relationship. Look for evidence that they protected the team and product integrity without being confrontational.
Tests backbone and political skill. PMs who cannot say no build bloated products. PMs who say no without tact burn bridges. Look for the balance.
Reframe the conflict from "whose priority wins" to "what outcome are we all trying to achieve for the user?"
Best answers show facilitation skills: bringing all parties together, reframing the discussion around user outcomes rather than departmental goals, finding creative solutions that partially satisfy all parties, and getting genuine buy-in rather than forced compliance.
Core PM responsibility. Watch for whether the candidate positions themselves as a neutral facilitator or takes sides. Best PMs find the underlying user need that unites competing priorities.
Show that you use data to reduce risk around intuitive bets, not as a substitute for product judgment.
Strong answers recognise that data informs but does not decide. Good examples: using data to validate an intuition-driven bet, or overriding data when qualitative research revealed the "why" behind surprising numbers. Beware of candidates who are purely data-driven or purely gut-driven.
Reveals PM philosophy. The best PMs know when to trust data and when to trust their judgment. Ask: "When would you ship something the data says not to?"
Describe your regular rhythm: weekly support ticket reviews, monthly user interviews, quarterly on-site visits - show it is a habit, not a one-off.
Look for multiple channels: regular user interviews, support ticket reviews, NPS analysis, session recordings, dogfooding where possible, customer advisory boards. Best candidates have a systematic practice rather than ad-hoc customer contact.
Customer empathy is non-negotiable for PMs. Red flag: candidates who only look at dashboards. Good sign: candidates who can name specific customers and their pain points.
Show that you test assumptions before building. Describe the cheapest way you validated demand: a landing page, a Wizard of Oz prototype, or concierge testing.
Strong answers show a structured discovery process: problem framing, customer interviews, competitive analysis, prototyping, and risk assessment (value, usability, feasibility, viability). Best candidates mention dual-track development and specific techniques like opportunity solution trees or assumption mapping.
Tests product thinking depth. Weak candidates skip straight to building. Strong candidates have a systematic way to reduce risk before committing resources. Ask: "What do you do when discovery results are ambiguous?"
Acceptance criteria should be testable and specific. "Page loads fast" is vague; "Page loads in under 2 seconds on 3G" is verifiable.
Good answers cover the user story format (As a... I want... So that...) but also go beyond it: including context, success metrics, edge cases, and clear acceptance criteria. Best candidates discuss the conversation around the story being more important than the written artefact, and mention INVEST criteria.
Fundamental PM skill. Red flag: writing requirements in isolation without talking to engineering. Good sign: treating stories as conversation starters with clear, testable acceptance criteria.
Removing features is a product skill. Show how you used data to identify unused features and communicated the sunset to affected users.
Strong answers distinguish product debt from technical debt: outdated features that confuse users, redundant functionality, accumulated complexity. Best candidates discuss audit practices, usage data to identify debt, sunset processes, and the courage to remove features. They should mention migration paths for existing users.
Senior PM question. Most PMs only add features. The best ones also remove. Ask: "What feature have you sunset and how did you handle user pushback?"
Show that you define the "what" and "why" while trusting designers with the "how." Give an example of a time you changed your mind based on a designer's insight.
Best answers show mutual respect: PMs define the problem and constraints, designers own the solution space. Key practices include early involvement in discovery, shared understanding of user needs, design critiques with constructive feedback, and respecting design expertise rather than dictating pixel-level decisions.
Reveals collaboration style. Red flag: PMs who design in their specs or override designers without user evidence. Good sign: genuine partnership with specific examples of learning from design colleagues.
Show the full launch plan: beta users, enablement for sales/support, marketing coordination, metrics monitoring, and your rollback plan if things went wrong.
Strong answers cover: launch planning with marketing and sales, beta programmes and early adopter feedback, phased rollout strategies, documentation and enablement, success metrics definition, and post-launch monitoring. Best candidates coordinate across functions and plan for things going wrong.
Tests execution and cross-functional coordination. PMs who "throw features over the wall" to marketing are incomplete. Look for orchestration skills and contingency planning.
Show that you track competitors systematically but decide based on your users' needs. "We chose not to copy X because our users need Y" demonstrates strategic confidence.
Best answers show systematic tracking (feature matrices, positioning maps) combined with strategic filtering. Strong candidates monitor competitors but make decisions based on their own user needs and vision. They distinguish between competitive parity features and differentiators, and know when to follow versus lead.
Tests strategic independence. Reactive PMs build whatever competitors build. Strong PMs use competitive intelligence to inform, not dictate, their roadmap. Ask: "When have you deliberately ignored a competitor feature?"
Show that you think about pricing as a product decision, not just a finance decision. How you price signals how you position.
Strong answers consider: value-based pricing (willingness to pay research), competitive positioning, cost structure, customer segmentation, packaging and tiering, and experimentation. Best candidates mention the relationship between pricing and positioning, and how pricing affects product perception.
Senior PM question. Many PMs avoid pricing. Those who engage with it demonstrate business acumen. Ask: "How do you test price sensitivity?" to gauge depth.
Always translate feature requests into problems. "They want an export button" might really mean "they need to share data with finance" - which might have a better solution.
Best answers: thank sales for the intelligence, dig into the underlying problem (not just the requested solution), assess whether the requests align with product strategy, check if other customers share the need, evaluate the revenue opportunity against the development cost, and communicate the decision back with rationale.
Critical B2B PM skill. Candidates who build everything sales asks for create Frankenstein products. Those who ignore sales lose deals. The balance is translating requests into validated needs.
Be specific about how you use AI tools in your workflow today, not just theoretical possibilities. Also discuss how you evaluate AI features for your product.
Strong answers show genuine engagement with AI tools and their impact: using AI for user research synthesis, prototype generation, data analysis, and writing. But also recognising what AI cannot replace: judgment, user empathy, strategic thinking, and stakeholder relationships. Best candidates discuss specific tools they use and how they evaluate AI features for their products.
Timely question that reveals adaptability and curiosity. Red flag: dismissing AI entirely or uncritically embracing everything. Good sign: practical adoption with critical evaluation of where AI adds value.
Name multiple quantitative and qualitative signals. No single metric proves PMF - show you triangulate across retention, NPS, organic growth, and qualitative feedback.
Look for multiple signals: retention curves flattening, organic growth, the Sean Ellis survey (40%+ "very disappointed"), strong engagement metrics, low churn, and qualitative signals like users recommending the product. Best candidates discuss the difference between early traction and true PMF, and how they iterate toward it.
Core PM concept. Candidates who only cite the Sean Ellis survey lack depth. Those who discuss the journey toward PMF and the iterating process demonstrate real experience building products.
Find the shared goal beneath the disagreement. If one stakeholder wants speed and another wants quality, the shared goal might be sustainable growth. Start there.
Strong answers show facilitation: identifying shared goals beneath surface disagreements, using data and user evidence to ground the conversation, creating frameworks for ongoing alignment, and documenting agreed principles. Best candidates build durable alignment processes rather than resolving conflicts one at a time.
Tests influence and facilitation skills. PMs who escalate every disagreement to leadership are not doing their job. Those who find common ground and build consensus are invaluable. Ask for a specific example with named constraints.
For every metric you track, define a counter-metric. If you optimise for sign-ups, track activation too. Show you guard against unintended consequences.
Strong answers demonstrate understanding of Goodhart's Law: when a measure becomes a target, it ceases to be a good measure. Look for candidates who think about leading vs lagging indicators, counter-metrics to prevent gaming, and metric hierarchies. Best candidates have concrete examples of replacing vanity metrics with actionable ones.
Tests analytical maturity. PMs who pick metrics without considering second-order effects create perverse incentives. Ask follow-up: "How do you get a team to care about a metric they did not choose?"
Frame technical debt in business terms leadership understands: "Our deployment takes 3 hours, costing 15 engineering hours per week. Two sprints of investment saves 700 hours per year."
Strong answers show partnership with engineering: understanding the business impact of tech debt (velocity loss, incident frequency, recruitment challenges), allocating a sustainable percentage of capacity, framing debt reduction in business terms, and tracking improvement over time. Best candidates avoid treating tech debt as an engineering-only concern.
Tests engineering partnership. PMs who ignore tech debt lose engineering trust. Those who can quantify its business impact and advocate for investment earn deep credibility with their teams.
Come to sprint planning with a prioritised list and clear acceptance criteria. When capacity is tight, present trade-offs to stakeholders rather than overcommitting the team.
Strong answers show preparation: refined backlog with clear priorities, estimated stories, defined acceptance criteria, and realistic capacity awareness. When demand exceeds capacity, best candidates facilitate trade-off conversations with stakeholders rather than pressuring the team or silently dropping commitments.
Tests basic PM execution and integrity. PMs who overcommit their teams erode trust on both sides. Those who facilitate honest conversations about trade-offs build sustainable delivery rhythms.
Give specific examples of growth levers you would embed: referral mechanics, viral sharing features, or freemium-to-paid upgrade moments triggered by genuine value realisation.
Look for understanding of PLG mechanics: viral loops, freemium conversion funnels, in-product onboarding, network effects, and self-serve expansion. Best candidates discuss the relationship between product experience and acquisition, the role of time-to-value, and how PLG complements rather than replaces sales-led or marketing-led growth.
Tests modern product strategy thinking. PLG is not just a buzzword - candidates should understand the mechanics. Ask: "How does PLG change the PM's relationship with marketing and sales?"
Test when the cost of being wrong is low and traffic is sufficient. For strategic product direction, make a judgment call and measure outcomes over a longer horizon.
Strong answers show pragmatism: A/B tests for reversible decisions with measurable outcomes and sufficient traffic, judgment calls for strategic direction, low-traffic features, or irreversible decisions. Best candidates discuss sample size requirements, test duration, and the risk of testing everything rather than making bold product bets.
Tests analytical pragmatism. Over-testing PMs move slowly; under-testing PMs make expensive mistakes. Look for candidates who understand when testing is valuable and when it becomes a crutch for avoiding decisions.
Describe your specific rituals: weekly cross-functional standup, shared launch checklist, monthly customer insight review. Show how each one solved a real communication gap.
Look for intentional communication design: regular cross-functional syncs, shared documentation, launch coordination processes, feedback channels from support to product, and scaling practices as the organisation grows. Best candidates discuss when to add process and when to remove it.
Tests organisational thinking. As products scale, communication breaks down between functions. PMs who proactively design communication systems prevent costly misalignment.
Give affected users ample notice and a clear migration path. Communicate the "why" honestly and offer support during the transition. How you sunset reflects your product values.
Strong answers cover the full sunset lifecycle: quantifying the maintenance burden, identifying affected users and their alternatives, creating a migration path, communicating with empathy and advance notice, supporting users through the transition, and measuring the impact post-sunset. Best candidates show courage balanced with user empathy.
Senior PM skill. Adding features is easy; removing them requires courage and empathy. Ask: "How did affected users react and how did you handle the pushback?" to test resilience.
Regularly prune your backlog. If an item has sat untouched for six months, either prioritise it or delete it. A bloated backlog is not a roadmap - it is a graveyard of good intentions.
Strong answers describe a regular cadence: grooming sessions with engineering, pruning stale items, adding acceptance criteria, splitting large stories, and ensuring the top of the backlog is always sprint-ready. Best candidates mention the danger of an ever-growing backlog full of items nobody will ever build.
Tests execution discipline. PMs with messy backlogs waste team time in planning sessions. Those who maintain a clean, prioritised backlog enable smooth sprint planning and honest stakeholder communication.
Use both top-down (industry data) and bottom-up (customer count x average spend) approaches, then triangulate. When the numbers diverge, investigate why.
Strong answers show both top-down and bottom-up approaches: TAM from industry reports and total addressable spend, SAM from realistic segment targeting, SOM from current capabilities and go-to-market reach. Best candidates acknowledge the uncertainty in market sizing and describe how they validated assumptions with real data.
Tests business acumen. PMs who cannot size an opportunity struggle to prioritise investment decisions. Ask: "How did your market sizing influence the go/no-go decision?" to see if it was genuinely used.