Behavioral: Pushing Back on a Decision and Holding a Position Under Pushback

This question comes from a competency-based behavioral round for a senior engineering role, where a few questions receive an hour of follow-ups. Two of the reported prompts probe the same competency, disagreeing constructively and standing behind a position, so they are combined here as two parts. Use a different story for each part. ### Constraints and Clarifications - Use real experiences; expect detailed probing on what you said, to whom, and when. - At a senior level, the disagreement should involve meaningful stakes and people with real influence over the outcome. ### Clarifying Questions - Can Part 1 involve pushing back on my own manager, or on a request from a customer or another team? - In Part 2, does it matter whether my position turned out to be right? - Should I include a case where I was overruled? ### Part 1 — Pushing back on a decision or request Tell me about a time you pushed back on a decision or a request. Why did you disagree, how did you raise it, and what happened? ```hint Disagree with evidence Prepare the specific risk or evidence you raised, how you framed it for the person who owned the decision, and what you would have done if they had kept the original plan. ``` #### What This Part Should Cover - The decision or request and why it was a problem - How the disagreement was raised: timing, channel, framing and evidence - An alternative offered, not only an objection - The outcome, and commitment to the final decision whichever way it went ### Part 2 — Holding a position despite pushback Tell me about a time you insisted on a course of action even though others pushed back. How did you decide it was worth holding firm, and how did you bring people along? ```hint Know why you held Separate the evidence that made you confident from your attachment to the idea, and be ready to say what would have changed your mind. ``` #### What This Part Should Cover - Why the candidate believed the course was right, with evidence - How the objections were heard and addressed - How support was built rather than forced - The result, including any part where the critics turned out to be right ### What a Strong Answer Covers - Disagreement grounded in data, risk or customer impact rather than personal preference - Raising concerns early, respectfully and through the right channel - Openness to changing one's mind, with a clear sense of what evidence would do it - Full commitment once a decision is made, including decisions that went the other way - Attention to the working relationship as well as the outcome ### Follow-up Questions - Tell me about a time you pushed back and were overruled. What did you do next? - How do you decide whether a disagreement is worth raising at all? - How do you push back on a request from someone far more senior than you? - Looking back at Part 2, what would have happened if you had given in?