How to Screen Senior Product Managers: 9 Questions and What to Listen For Screening Interview Template

In three or four sentences, what is the strategy for the product area you own today? What does it say you will not do, and what would have to be true for it to be wrong?

What this assesses: A strategy that excludes nothing is a wish list, and that is what most candidates will send you. Strong answers are short and they choose: a segment they serve and one they deliberately do not, a problem they are betting on, and a reason that bet beats the obvious alternative. Then they name the condition that would break it, such as the mid-market segment never converting at a usable rate or a platform change removing their wedge. That second half shows they hold the strategy as a hypothesis rather than a slogan. Weak answers restate the company mission, list four goals at equal priority, or describe a roadmap and call it a strategy. If the candidate cannot say what they are not doing, nobody on their team can either.

Roughly how did your teams' capacity split last year across new bets, improving the core product, and maintenance or technical debt? Who set that split, and what would you change about it?

What this assesses: This is the question that shows whether the candidate actually runs a portfolio. Strong answers give rough percentages without hesitation, explain why that split fit the stage of the product, and describe a moment it was contested: a quarter they protected time for debt against pressure for features, or a bet they starved and later regretted. They also know who could override the split. Weak answers have never thought about capacity as a number, or describe every quarter as all new features, which usually means someone else absorbed the maintenance cost and the candidate never saw the bill. Be cautious with a perfectly balanced answer like a third each. That is a framework, not a history.

Tell me about a product, feature line, or customer segment you retired or walked away from while customers were still using it. What did it cost, and how did you handle the customers who were left?

What this assesses: Retiring something live is harder than killing a project in development, because real customers are attached to it and someone has to tell them. Strong answers give the cost in numbers, whether that is revenue walked away from, accounts that churned, or support hours, and explain why it was worth paying: engineering time freed for the core, a segment that never fit, a maintenance burden that grew every release. They describe the mechanics in detail, including notice periods, a migration path, and what they did with the largest account that pushed back. Weak answers describe a feature nobody used, which costs nothing to retire, or a decision someone above them made. A senior PM who has never subtracted anything has only been adding weight to the product.

Have you owned a pricing or packaging change? What changed, what did you expect to happen, and what actually happened to conversion, expansion, or churn?

What this assesses: Not every senior PM has owned pricing, and saying so plainly is a good answer. What you are screening for is whether the candidate knows the difference between owning it and attending the meetings. Strong answers name the change, such as a new tier, a usage-based component, or moving a feature up a plan, then give the prediction they made beforehand and the result, including second-order effects like longer sales cycles or a spike in billing tickets. They mention how existing customers were handled, since grandfathering decisions are where most pricing changes quietly fail. Weak answers say they partnered closely with finance and marketing, give no numbers, or claim a revenue lift with no baseline. If the role you are filling touches pricing, weigh this question heavily.

Tell me about a time you tried to change your leadership team's mind about a direction they had already committed to. What did you bring, how did you bring it, and did it work?

What this assesses: Senior PMs spend more of their week persuading upward than anyone outside the role expects. Strong answers describe a real commitment, not a rough idea, and a specific case they built: usage data, a set of customer conversations, a written memo laying out the cost of staying the course. They usually talked to the key executives one at a time before the meeting rather than walking in cold. Losing is a fine outcome if they can say what they did next, which should be committing to the decision and executing it properly, not quietly slow-walking it. Weak answers pick a disagreement they won easily, describe going around their manager, or cannot name a single time they pushed back. A senior PM who always agrees with leadership is an expensive project manager.

Describe a bet that depended on another team shipping something they had not prioritized. How did you get it done, or what did you do when it did not happen?

What this assesses: At senior levels the work that matters most usually crosses a team boundary, and the PM has no authority over the other team. Strong answers describe what they offered in exchange, whether that was their own engineers doing part of the work, dropping a request the other team hated, or making the case to the leader who owned both roadmaps. An answer where they re-scoped the bet to remove the dependency entirely is just as strong. They also say when they escalated and what the escalation cost the relationship. Weak answers describe waiting, asking for status every week, or blaming the other team for the delay. Be cautious with a story where escalation was the first move rather than the last.

Have you managed or mentored other PMs? Tell me about one whose work you had to correct. What was wrong, and what did you do about it?

What this assesses: Even an individual contributor at the principal level is expected to raise the bar for the PMs around them, so ask this whether or not the role has reports. Strong answers name a specific craft gap, such as specs that described the request instead of the problem, a PM who could not say no to sales, or launch plans with no success metric, and then describe what they did: reviewed drafts line by line, sat in on a hard stakeholder conversation, or set a standard and held the line. They describe the result honestly, including a PM who did not improve. Weak answers talk about empowering the team and giving autonomy with no example, or describe rewriting the other PM's work themselves, which fixes one document and teaches nothing.

Pick a bet that needed more than two quarters to show results. What leading indicator did you commit to in advance, what did it show at the first checkpoint, and what did you decide?

What this assesses: Long bets are where senior PMs either earn the title or burn a team's year. Strong answers name a leading indicator chosen before the work started, such as weekly use by the target segment, pilots converting to paid, or activation inside the first week, plus a threshold that would have ended the bet. Then they say what the checkpoint showed and what they did, including cases where they continued despite weak numbers and can explain why. Weak answers pick the metric after the fact, move the goalposts when the early numbers come in soft, or describe a bet that was simply given more time until everyone stopped asking. Ask for the numbers. A candidate who ran the process remembers them.

What scope do you want next: how many teams or PMs, what product stage, and how close to revenue? Do you want to manage people or stay an individual contributor, what would make you turn this role down, and what base and variable are you targeting?

What this assesses: At this level, mismatched expectations are the most common reason a good candidate falls apart at the offer stage or leaves inside a year. Strong answers are specific: two or three teams, a product past early fit but before a platform rewrite, direct influence on pricing, and a plain statement of whether they want to manage PMs or stay on the principal track. They name real constraints and a real number. Be cautious with a candidate who is open to anything, which usually means a constraint is being held back until there is leverage. Be cautious too with someone who wants a people-management title but has never managed anyone, since your role may be where they learn. Ask every applicant the same questions in the same order and score them against a shared [interview scorecard](/glossary/interview-scorecard) rather than reading answers in isolation.