PM Behavioral: Working Through Conflict With an Engineer, Designer or Peer
Company: Google
Role: Product Manager
Category: Behavioral & Leadership
Difficulty: medium
Interview Round: Other
You are interviewing for a product manager role. When you and a colleague, such as an engineer, a designer or another PM, want different outcomes, how do you work through the disagreement and reach a resolution?
```hint Find what the disagreement is really about
A dispute over a decision often hides a difference in goals, information or ownership. Show how you would find out which one you are facing before you try to settle it.
```
### Clarifying Questions
- Should I describe my general approach, or walk through one disagreement I have actually handled?
- Is the colleague a peer, someone on my own team, or a partner in another organization with different goals?
- Is the disagreement about a product decision, such as scope, priority or how to read the data, or about how we work together?
### What a Strong Answer Covers
- Diagnosing the source of the disagreement before arguing for a position
- Understanding the colleague's goals and constraints, and showing they were heard
- Moving the discussion to shared goals, evidence and agreed decision criteria
- A clear way to reach a decision when consensus fails, including escalation and committing to the outcome
- A concrete example with its result, the state of the relationship afterwards and what was learned
### Follow-up Questions
- The decision went your way, and later it turned out you were wrong. What did you do?
- When do you escalate a disagreement to your manager, and how do you do it without damaging trust with your colleague?
- Tell me about a time you lost the argument and still had to lead the work. How did you commit to it?
Overview: A behavioral product manager question about how you resolve a disagreement with a colleague such as an engineer, designer or fellow PM. It tests diagnosing the real source of a conflict, using shared goals and evidence to reach a decision, knowing when to escalate, and backing the approach with a concrete example.