Top 10 Questions You'll Face in a PM Interview

As a Technical Interview Assessor, I've evaluated hundreds of PM and PO candidates for recruitment agencies and hiring managers. The questions are often similar. The answers that stand out are those that are specific, honest, and structured.

Here are the 10 questions I ask most often, and what good answers look like.

1. Walk me through a product you've built or managed from 0 to 1.

Good answers describe the problem, the constraints, the decisions made, and the outcome. They include failure and what was learned.

2. How do you prioritise a backlog?

Good answers name a framework (RICE, MoSCoW, Kano) and explain when to use it — not just describe it theoretically.

3. Tell me about a time you pushed back on a stakeholder.

Good answers show calm confidence. The candidate disagreed respectfully, explained their reasoning, and either won the argument or lost gracefully.

4. How do you handle conflicting priorities between engineering and business?

Good answers show the candidate can facilitate, not just escalate. They look for underlying interests, not just stated positions.

5. What metrics do you track for your product?

Good answers are specific to the product type. Not "DAU and MAU" as a default, but a thoughtful choice of leading and lagging indicators.

6. Describe your process for writing a user story.

Good answers include acceptance criteria, edge cases, and how they get feedback from engineering before refinement.

7. How do you work with a development team that pushes back on estimates?

Good answers show empathy and curiosity — not impatience. The candidate explores the reason for the pushback, not just the resolution.

8. What does done mean to you?

Good answers reference the definition of done and explain how they establish it with the team.

9. Tell me about a product that failed.

Good answers are honest. Candidates who claim their products never failed are lying or haven't shipped enough.

10. Why do you want this role?

Good answers are specific to the company and role — not generic. They show the candidate has done research.

Prepare structured answers to all of these before your next interview.