Interview scorecard
Product Owner
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.
Backlog management
Keeps the backlog current, clear, and ordered so the team always knows what to build next.
Questions
- Tell me about a backlog you inherited that was messy. What did you do first?
- How do you decide when to remove or merge old items?
- Tell me about a time the backlog got out of date. How did you catch it?
1: Below the bar
Describes the backlog as a pile of ideas. Cleans it rarely and can't say how the team knows what's next.
3: Meets the bar
Reviews the backlog on a regular schedule and removes stale items. Keeps the next few sprints ready, though some upkeep happens late.
5: Above the bar
Sets clear rules for adding and removing items, keeps upcoming work ready ahead of time, and checks the backlog's health with the team.
Requirements definition
Turns a vague need into clear, testable requirements that engineers and stakeholders read the same way.
Questions
- Tell me about a vague request you turned into clear requirements. How did you start?
- How do you decide a requirement is clear enough for engineers to build?
- Tell me about a requirement that was misunderstood. What did you change afterward?
1: Below the bar
Passes along requests as stated. Can't say how they check that others understand or how they'd know it's done.
3: Meets the bar
Asks questions to clarify the need and writes acceptance criteria. Fixes misunderstandings once they surface during the build.
5: Above the bar
Uncovers the underlying problem, writes testable criteria, and confirms shared understanding with engineers before work starts. Cites how it prevented rework.
Prioritization
Ranks competing work by value and cost, and explains the choice to people who wanted something else.
Questions
- Tell me about a time you had more requests than the team could deliver. How did you choose?
- Describe a priority call you made with little data. What did you rely on?
- Tell me about a time you changed priorities mid-sprint. What triggered it, and what did you drop?
1: Below the bar
Ranks by who asks loudest or by gut feeling. Can't name what was dropped or why.
3: Meets the bar
Uses clear criteria such as value, effort or deadlines. Explains the trade-off made and what was postponed.
5: Above the bar
Uses explicit criteria, tests assumptions with data, and names what was cut. Reviews the outcome afterward and adjusts the approach.
Stakeholder management
Keeps people with competing interests informed, aligned and willing to accept decisions, including ones they dislike.
Questions
- Tell me about a time two stakeholders wanted opposite things from your product. What happened?
- Tell me about a time you said no to a senior stakeholder. How did you do it?
- How do you keep stakeholders informed so they are not surprised by changes?
1: Below the bar
Avoids conflict or gives in to the loudest voice. Stakeholders learn about decisions late or from someone else.
3: Meets the bar
Listens to each side, explains the decision and keeps people updated. Handles conflict, though mostly after it surfaces.
5: Above the bar
Spots conflicts early, talks to each side before deciding, and explains the reasons so even disappointed stakeholders stay supportive.
Working with engineers
Partners with engineers to shape solutions, respecting technical limits and keeping the team clear on the goal.
Questions
- Tell me about a time an engineer said your request was harder than expected. What did you do?
- Describe how you involve engineers before work is committed to a sprint.
- Tell me about a disagreement with an engineer over how to build something. How did it end?
1: Below the bar
Hands over finished requests and treats engineer pushback as delay. Describes disagreements as who won or lost.
3: Meets the bar
Brings engineers in before work starts and listens to concerns. Adjusts scope after pushback, though sometimes late.
5: Above the bar
Involves engineers early, asks about cost and options, and trades scope for speed. Describes disagreements that ended in a better shared plan.
Overall recommendation
Decide on your own, before you compare notes with the rest of the panel.