How a PM earns engineers' trust: what an engineering team needs from its product partner

An interviewer asks what engineers need from their product manager and what they expect of one. Give your answer, and support it with how you work with engineering teams. ```hint Sit in the engineer's seat Picture a sprint from an engineer's side: where do they lose time, get surprised, or see their work go to waste? Each of those moments points to something the PM owes them. ``` ### Clarifying Questions - Should I answer for a team shipping user-facing features or for a platform or infrastructure team whose customers are other engineers, since the expectations differ? - Would you like a broad view of what engineers expect, or one concrete example of a time I met or missed one of those expectations? - Should I also cover what a PM can fairly expect from engineers in return, or stay on the engineers' side? ### What a Strong Answer Covers - Concrete needs across the product lifecycle: the problem and the reason behind the work, clear priorities and stable scope, fast decisions, and unblocking. - Engineers treated as partners: involved early in discovery, with real input on prioritization, estimates and technical debt, and shared credit for results. - Honest handling of trade-offs with stakeholders, including saying no and committing only to what the team agreed. - Evidence from the candidate's own work, such as a time they got this right or wrong and what changed afterward. - Awareness that needs vary with the type of team and the engineers' seniority. ### Follow-up Questions - An engineering lead tells you the team feels like it only takes tickets. What would you change in the next month? - How do you handle an engineer who repeatedly challenges the priorities you set? - When should a PM shield engineers from stakeholder noise, and when does shielding hide context they need?