PM behavioral: winning engineering buy-in to build a feature you championed

Describe a situation in which you, as a product manager, persuaded the engineering team to build a particular feature. Explain the context, how you brought the engineers along, and what happened as a result. ```hint Pick a story with real resistance Choose an example where engineering had a genuine reason to say no, such as limited capacity, technical risk or a competing priority. That lets you show how you understood and answered their reason instead of relying on a title or a deadline. ``` ### Clarifying Questions - Does the example need to involve engineers who first pushed back, or does any feature you championed count? - Should it be your own team's engineers, or may it be a team you had no formal claim on? - Does a story count where you changed the feature's scope or design after hearing engineering's concerns, rather than winning the original request outright? ### What a Strong Answer Covers - A specific feature and a clear account of why it needed engineering's agreement (a full roadmap, technical cost, doubts about its value) - How the candidate learned engineering's point of view and objections before arguing their case - The evidence used, such as customer data, usage, revenue or a cost-of-delay estimate, and how the case was framed for engineers - Influence without authority: scoping, trade-offs, involving engineers in the solution, and escalation only when warranted and done openly - A measurable result, the effect on the working relationship, and what the candidate would do differently ### Follow-up Questions - What would you have done if the engineering lead still said no after hearing your case? - How did you make sure the feature you pushed for did not quietly displace something more important? - Did the feature deliver what you promised? If not, how did that affect your credibility with the team?