Interview scorecard
Product Manager
Score each skill from 1 to 5. A 1 is below the bar for this role, a 3 meets it, and a 5 is above it. The examples show what each sounds like. Use 2 and 4 for answers that fall in between.
Prioritization
Chooses what to build first and what to drop, using clear criteria and trade-offs.
Questions
- Tell me about a time you had too many requests and room for only a few.
- Describe something you chose not to build. How did you explain that decision?
- Tell me about a time priorities changed mid-project. What did you do?
1: Below the bar
Lists everything as important or follows the loudest voice. Can't explain why one item came before another.
3: Meets the bar
Uses a clear reason such as impact or effort to rank items. Explains what was dropped but with little trade-off detail.
5: Above the bar
Sets criteria before ranking, names what was cut and its cost, and revisits the order when facts change.
Product sense
Identifies real user problems and shapes product ideas that solve them in a way users value.
Questions
- Tell me about a product you improved. Who was it for and what problem did it solve?
- Tell me about a time you learned something about users that changed your plan.
- Pick a product you use daily. What would you change, and why?
1: Below the bar
Starts with features, not users. Cannot say who the product is for or what problem it solves.
3: Meets the bar
Names the user and the problem, and links the idea to them. Considers few alternatives or user limits.
5: Above the bar
Describes users in specific detail, tests the problem before the solution, and explains why they chose one idea over others.
Stakeholder management
Aligns people with competing interests around a plan and keeps them informed as it changes.
Questions
- Tell me about a time two stakeholders wanted opposite things from you. What did you do?
- Describe a time you had to say no to a senior person. How did it go?
- Tell me about a time a stakeholder was surprised by a change. What did you do afterward?
1: Below the bar
Avoids conflict or gives in to the loudest voice. Stakeholders learn about changes late or from others.
3: Meets the bar
Listens to each side and reaches a workable agreement. Updates people on changes but mostly after the fact.
5: Above the bar
Understands each side's goals before they ask, finds a shared outcome, says no with reasons, and updates people early.
Decisions from data
Uses evidence to choose a product direction and stays honest about what the numbers cannot show.
Questions
- Tell me about a product decision you made using data. What did the data show?
- Tell me about a time the data was unclear or conflicted. What did you do?
- Tell me about a time data changed your mind or proved you wrong.
1: Below the bar
Cites numbers loosely or after the fact to justify a choice. Cannot say what the data did or did not prove.
3: Meets the bar
Picks relevant data and links it to a clear decision. Notes some limits but rarely checks the result afterward.
5: Above the bar
Frames the question before pulling data, weighs its limits, and checks the outcome. Shares a time they changed course.
Execution
Gets planned product work shipped on time by managing scope, risks, and daily follow-through.
Questions
- Tell me about a product launch you took from plan to release. How did you keep it on track?
- Tell me about a time a project slipped. What did you do next?
- How do you track work across a team day to day? Give me an example.
1: Below the bar
Describes work as happening to the team. Learns of delays late and can't say what they did to recover.
3: Meets the bar
Names a clear plan and regular check-ins. Spots delays and adjusts scope or dates, though often after the slip has started.
5: Above the bar
Names risks early, owns the plan, cuts scope or reroutes work before dates slip, and shares concrete results afterward.
Overall recommendation
Decide on your own, before you compare notes with the rest of the panel.