Tell me about a time when you had to go against management or your colleagues
Asked at:
Meta
Try This Question Yourself
Practice with feedback and follow-up questions
What is this question about
Interviewers use this question to assess whether you can disagree constructively when power, status, or team consensus is pointing another direction. They want to see judgment: was the issue worth pushing on, did you understand the other side's constraints, and could you influence without becoming combative or self-righteous. For more senior levels, they also look for whether you can protect outcomes and relationships at the same time.
“Tell me about a time you disagreed with your manager. What did you do?”
“Describe a situation where you pushed back on a decision from your team or leadership.”
“Have you ever had to challenge a direction that others around you supported?”
“Walk me through a time when you were not aligned with colleagues on an important decision.”
“What's an example of a decision from management or peers that you opposed? How did you handle it?”
Key Insights
- Conflict here does not have to mean an argument. A strong answer often centers on a substantive disagreement in priorities, risk tolerance, or tradeoffs, and shows how you explored those differences instead of treating others as obstacles.
- You should explain why you chose to push back at all. Interviewers are listening for judgment about when disagreement is necessary versus when alignment, compromise, or simple deference is more appropriate.
- Do not frame the story as 'I was right and they were wrong.' Strong answers show respect for management or colleagues' perspective, even if you ultimately changed the decision.
What interviewers probe atlevel
Top Priority
Show that you got curious before pushing harder; interviewers want to see maturity, not reflexive contradiction.
Good examples
🟢Before pushing back, I asked my tech lead what risk they were worried about and learned they had seen similar changes break a downstream workflow before.
🟢I set up a quick follow-up with my teammate to understand why they opposed the change, and it turned out they were covering support issues I had not been exposed to.
Bad examples
🔴My teammate said no to my idea, and I assumed they were just being resistant because they did not want to change anything.
🔴My manager asked me to do it differently, and I focused on explaining why my way was better without really asking what concern they had.
Weak answers flatten others into blockers; strong answers treat others as informed partners with legitimate context.
Pick a real disagreement with meaningful impact, not a preference battle over something tiny.
Good examples
🟢I was asked to ship a change without basic error handling, and I pushed back because a failed request would have broken a customer workflow we already knew was sensitive.
🟢A teammate wanted to skip testing to save time before release, and I raised concerns because we had recently seen regressions in the same area.
Bad examples
🔴My teammate wanted a different variable naming style, but I felt my style was clearer, so I pushed back until we used my version.
🔴My manager asked me to use a certain library, but I preferred another one I'd seen online, so I argued for that because it seemed more modern.
Weak answers make the candidate seem attached to personal preference; strong answers show they can recognize when a disagreement affects reliability, users, or team risk.
Valuable
Show that the relationship still worked afterward and that you learned how to disagree better next time.
Good examples
🟢After we shipped, I checked in with my teammate to make sure there were no hard feelings, and we ended up using the same review approach on later work.
🟢I learned to ask more questions up front before defending my idea, and that made later disagreements with the team smoother.
Bad examples
🔴Afterward we just moved on, and I did not really think about the interaction since the task got done.
🔴The decision changed, so I considered it resolved even though my teammate and I did not talk much after that.
Weak answers end at the decision; strong answers show relationship awareness and a growth loop.
Interviewers want to know whether you knew when to keep discussing, when to defer, and how to move forward after the decision.
Good examples
🟢Once I shared the concern and we agreed on a safer version, I supported the final decision and helped implement it without lingering tension.
🟢When my lead explained the broader context and decided to proceed differently, I accepted it, documented the risk, and stayed engaged in making the plan successful.
Bad examples
🔴After we still disagreed, I kept revisiting the decision over the next few days because I wanted to make sure my view was not ignored.
🔴I escalated to our manager pretty quickly because I did not think there was a point continuing the discussion with my teammate.
Weak answers show poor calibration after the disagreement; strong answers show the candidate can push back, then align and execute.
Example answers atlevel
Great answers
In my first year, I was working on a small change to our internal dashboard, and my teammate suggested we skip validation on one input so we could finish before the sprint ended. I was uncomfortable with that because the same field fed into a report used by operations, and bad data would have been hard to unwind later. I asked if we could talk through the risk, and I learned they were under pressure because another task had slipped and they were trying to protect the deadline. I suggested a smaller version of the feature that kept the validation but reduced some nonessential polish, and I put together a quick test to show it would not add much time. We went with that plan, shipped on time, and avoided the riskier shortcut. Afterward, my teammate thanked me for raising it directly, and I learned that when I disagree, it helps to understand what's driving the push before defending my own view.
At a previous startup I was asked to build a small interactive widget for our product landing page and the product manager wanted a full-screen animation that ran on load and prevented interaction until it finished. I knew that would be a poor experience for people using keyboard navigation or screen readers, so I raised my concern with the PM and designer and showed them a quick demo of how the animation broke focus and hidden content. Instead of just saying no, I proposed and implemented a compromise: let the animation play but include a visible "skip" control, preserve logical focus order, and add proper labels for assistive tech. We shipped on time with those changes, and support tickets about accessibility dropped; I learned that bringing a concrete demo and a low-cost fix makes it much easier to go against the plan and get buy-in.
Poor answers
I had a time when my manager wanted me to implement a feature using a different library than the one I wanted. I had read that the one I liked was newer, so I kept pushing for it in our chat and showed a few articles saying it was better. Eventually my manager agreed to let me use it. It worked out, so I felt good about sticking to my opinion instead of just doing what I was told.
Question Timeline
See when this question was last asked and where, including any notes left by other candidates.
Early December, 2025
Meta
Mid-level
Late August, 2024
Meta
Senior
Tell me about a time when you had to go against management or your colleagues
Hello Interview Premium
Your account is free and you can post anonymously if you choose.