Pushing Back on Your Manager or Senior Leaders Instead of Agreeing by Default

In a product manager interview, you are asked to describe a time when you stopped simply agreeing with your manager or senior leadership and pushed back instead. Use one real situation. The interviewer wants to hear what leadership wanted, why going along with it would have been a mistake, how you raised your disagreement, what was decided and what happened next, and how your working relationship with that leader held up. ```hint Give the pushback a basis Pick a moment where you knew something leadership did not, such as user evidence, an engineering cost or a launch risk, so the disagreement reads as judgment rather than defiance. Be ready to explain why you had been agreeing until then. ``` ### Clarifying Questions - Are you looking for one specific disagreement, or for a shift away from a habit of agreeing too readily with senior people? - Does the story still work if leadership heard me out and kept its original decision? - Should the leader be my direct manager, or does a skip-level executive or a senior stakeholder in another team count? ### What a Strong Answer Covers - A request or decision with real stakes, where agreeing would have hurt users, the product or the team - The evidence behind the disagreement and why it outweighed deference to seniority - How and where the concern was raised: timing, setting, options offered alongside the objection, and respect for the leader's goals - The decision and its outcome, including committing fully if overruled, and the effect on trust with the leader - Insight into why the candidate had been saying yes, and a lasting change in how they work with senior people ### Follow-up Questions - If your manager had listened and still kept the original plan, what would you have done next? - How do you decide which requests from leadership deserve a challenge and which you should simply execute? - What changed in your relationship with that leader afterward, and what evidence do you have?