Top 3 Questions You Should Ask In Your Product Owner Interview

A job interview should be a two-way conversation. While the hirer is trying to determine if you are a good fit for the position you, the candidate, should use the interview to figure out if the company is a place where you want to work. 

A few well-phrased questions can yield fantastic insights.

Questions #1: What is the span of accountability and authority that I would have in this role? 

The effectiveness of the Product Owner, and of the overall Scrum implementation, depends on how much accountability and authority a Product Owner has. Let’s look at four situations where you might be called a Product Owner but have different accountability and authority:

Ordertaker – You’re primarily going to administer the Product Backlog, collect the requirements from the stakeholders and translate them into user stories for the people doing the work. You’ll be more like a Business Analyst. Your authority and accountability is very limited. This is NOT a type of Product owner the Scrum Guides describes.

Middleman – Similar to the Ordertaker Product Owner, the Middleman Product Owner has more authority and responsibilities than an Ordertaker Product Owner. You’ll be more like a Project Manager. You can expect that the major decisions, such as the business goals, scope, and desired outcomes, are still determined by the principal stakeholders such as the business owner, sponsors, or steering committees. You’re the middleman. You’re going to get frustrated daily. 

Cat Herder  – This type of Product Owner is well aware of the business context, market, and customers. A good example of this is when a traditional Product Manager is expected to step into a Product Owner role. This type of Product Owner will have limited autonomy since the sponsors have the real authority and the final say. Managing sponsors with competing needs is like herding cats. Expect that for sure! 

Real Product Owner – Contrary to the authority bestowed upon the Cat Herder Product Owner, the real Product Owners have their own budget to spend and much more authority. This is the type of Product Owner described in the Scrum Guide. This type of Product Owner role has the maximum impact on the product, customers, and organization. They own the product and are fully accountable for maximizing the value of the product. Those wanting to change the Product Backlog can do so by trying to convince you, not the other way around. 

Here’s a visual way to look at it. 

This should be the first question that you ask and based on what you find out, all of your responses will need to be contextualized.

Questions #2: Who are the customers and users of the product and what are their needs?

By asking questions related to the needs of the customers and users, you will get a better understanding of what problems the product is trying to solve and for whom. You want to get a sense of how your role or position fits into the rest of the company. The main accountability of a Product Owner is to ensure that the product brings value to its customers and users. Customer and user can be the same person, but don’t have to. This is important because as a Product Owner you often need to show different value to customers than to actual users. For instance, when my wife buys a bike for herself, she’s both a customer and the user. When she buys a bike for my five-year-old son, she’s the customer, and my son is the user. My son cares that it’s a spider-man bike with awesome graphics. As a customer, my wife cares about the price, his safety, the quality, etc. As a CFO and a stakeholder, I make sure that they’re both happy and that they’re not spending a crazy amount of money on things they buy. 

Question #3: Who are the main people and groups I’d be collaborating with?

This helps you understand your place in the organizational structure better than titles do. Position titles vary so much from company to company and entity to entity. This question has the potential to expose the dependencies and help you get a sense of how work gets done at this company.

Write notes during the interview. If the interview goes well and it looks like it’s a fit for both parties, you can use your answers to these questions as notes for the thank you note and follow-up note you’ll write later to assure your strong candidacy.