Behavioral: Earning Buy-In from a Resistant Engineering Partner as a Product Manager

Describe a time when a technical stakeholder, such as an engineering lead, architect or platform owner whose work your product depended on, was hard to get aligned with you. What made the situation difficult, what did you do about it, and what was the outcome? ```hint Find the reason behind the resistance Choose a story where the pushback had a real technical or workload reason, and show how you uncovered that reason before you tried to change their mind. ``` ### Clarifying Questions - Should the stakeholder be an engineer on my own team, or can it be a technical owner outside my reporting line, such as a platform or security team I depended on? - Is a story acceptable where the engineer's objection turned out to be right and I changed my plan, or do you want one where I brought them around? - How deep should I go into the technical disagreement itself, for example the architecture or reliability concern, versus the way the decision was reached? ### What a Strong Answer Covers - A concrete situation with real stakes: what the stakeholder controlled and what their resistance put at risk - Diagnosis of the stakeholder's actual concern and incentives, described fairly rather than as a personality problem - Specific actions the candidate personally took, including engaging with the technical substance and offering options with explicit trade-offs - A clear outcome for the product and for the working relationship, ideally with evidence - Reflection on what the candidate learned and now does differently with technical partners ### Follow-up Questions - If the stakeholder had still refused after your best effort, what would you have done, and at what point would you escalate? - How did you judge whether their technical objection was valid, given that you were not the one building the system? - How did you keep leadership and the rest of the team informed while the disagreement was unresolved?