Working Through a Conflict Between Product and Engineering
Company: Salesforce
Role: Product Manager
Category: Behavioral & Leadership
Difficulty: medium
Interview Round: Other
Describe a time you disagreed with your engineering team or an engineering counterpart. What was the disagreement about, how did you work through it, and what happened?
```hint Show both sides of the trade-off
Be ready to explain engineering's concern in plain technical terms, not only the product side, and to say what made their position reasonable.
```
### Clarifying Questions
- Should the disagreement be about a technical decision, such as architecture or tech debt, or can it be about scope, estimates or a launch date?
- Is a disagreement with one tech lead or engineering manager fine, or are you looking for one with a whole team?
- Does it matter whether the outcome went my way or engineering's?
### What a Strong Answer Covers
- A real disagreement with stakes, with engineering's position stated accurately in its own technical terms
- Enough technical understanding to engage with the substance: cost, risk, effort or reliability, not just the schedule
- How the two sides reached a decision: the shared goal, the evidence, the options considered and who made the call
- The result for users and the product, and the state of the working relationship afterward
- What the candidate learned about partnering with engineers
### Follow-up Questions
- How do you decide when to accept an engineering estimate and when to challenge it?
- If the tech lead had refused to move, would you have escalated, and to whom?
- How do you make room for tech debt or reliability work on a roadmap you are measured on?
Overview: A behavioral question for product managers about a disagreement with engineering. It probes how you partner with engineers, whether you understand the technical side of a trade-off such as scope, quality or tech debt, how the decision was reached, and how the working relationship held up afterward.