What was a situation where you didn't agree with your manager or superior's decision?
Asked at:
DoorDash
Meta
Lyft
Amazon
Try This Question Yourself
Practice with feedback and follow-up questions
What is this question about
Interviewers use this question to assess how you handle disagreement with authority, especially when you do not control the final decision. They want to see whether you can challenge respectfully, understand the reasoning behind a decision, and respond productively after the decision is made. The best answers show judgment, emotional maturity, and an ability to balance conviction with collaboration.
“Tell me about a time you disagreed with your manager. How did you handle it?”
“Describe a situation where you pushed back on a decision from your boss or team lead.”
“Have you ever seen things differently from your manager on an important decision? What happened?”
“Walk me through a time you challenged a direction set by someone above you.”
“What's an example of a decision from a superior that you did not initially support?”
Key Insights
- Disagreement does not need to be dramatic. A strong answer often involves different risk tolerance, priorities, or incomplete information rather than a personal clash.
- You should show both sides of the equation: why you disagreed and why your manager's view was reasonable in context. If your story makes them sound foolish, you usually lose points.
- Do not stop the story at 'I pushed back.' Interviewers care a lot about what you did after the decision: whether you aligned, adapted, followed through, and learned anything.
What interviewers probe atlevel
Top Priority
Show curiosity first; interviewers want to know you did not treat disagreement as proof your manager was wrong.
Good examples
🟢I asked what deadline or constraint was driving the decision because I realized I only saw my implementation concerns, not the bigger picture.
🟢Before pushing back, I checked whether there was customer or business context I was missing and used that to frame my response.
Bad examples
🔴I knew the decision was a bad idea, so I explained why and kept defending my position until my manager stopped arguing.
🔴I had already worked on similar things before, so I didn't think I needed more context from my manager.
Weak answers assume disagreement equals superior judgment; strong answers show the candidate actively searches for missing context.
Do not just say you objected; show that you helped move the work forward in some practical way.
Good examples
🟢I suggested a smaller rollout and additional checks so we could still meet the timeline while reducing the risk I was worried about.
🟢I offered to do a short investigation and bring back options instead of just saying the current plan was wrong.
Bad examples
🔴I explained why I disagreed and then waited for my manager to decide what we should do.
🔴Once I made my concerns clear, I felt my part was done because the decision was above my level.
Weak answers stop at objection; strong answers add practical options, mitigations, or next steps.
Interviewers want to know whether you can disagree, then align and execute once a decision is made.
Good examples
🟢Once the decision was made, I committed to making it work and focused on reducing the risks I had identified instead of relitigating it.
🟢I aligned quickly after the discussion and helped execute the plan well, while keeping my manager updated on the outcomes we cared about.
Bad examples
🔴After my manager chose the other approach, I implemented it but kept pointing out along the way that my idea would have been better.
🔴I followed the decision, but only did exactly what was asked since I had already said I disagreed.
Weak answers show compliance without commitment or subtle sabotage; strong answers show professional alignment and follow-through.
Valuable
Even if you still think your manager was wrong, show that you learned something about how to handle disagreement better.
Good examples
🟢I learned to ask more questions before forming a strong view because I had initially underestimated the deadline pressure my manager was balancing.
🟢The experience taught me how to raise concerns earlier and with clearer evidence instead of waiting until the discussion was already tense.
Bad examples
🔴The main lesson was to trust my instincts because I had been right about the decision.
🔴What I took away was that managers do not always listen to engineers, so you have to push harder.
Weak answers turn the story into self-validation; strong answers show reflection on process, judgment, or communication.
Pick a real disagreement that had some consequence, but stay within the scope expected for someone still learning.
Good examples
🟢I disagreed with shortening test coverage to hit a deadline because I thought it would create avoidable production risk for a feature I was implementing.
🟢My manager wanted me to start building immediately, but I believed a short investigation was needed first because the requirements were still changing.
Bad examples
🔴I disagreed that we should use tabs instead of spaces, so I explained my preference for a while until we changed it.
🔴My manager wanted me to send updates in a shared document instead of chat, and I felt chat was faster, so we went back and forth on that.
Weak stories center on preferences or minor process annoyances; strong stories involve tradeoffs that reasonably affect quality, risk, delivery, or learning.
Example answers atlevel
Great answers
In my first year on a product team, my manager wanted us to ship a small feature by the end of the week, and I was worried we were skipping too much testing for a change that touched a checkout flow. I asked if there was a hard deadline I was missing, and he explained that support tickets on this issue were climbing and we needed a quick response. I still shared my concern, but instead of just arguing, I suggested a narrower release behind a flag and offered to add a few targeted tests that same day. He agreed to that version, and we shipped on time with lower risk. What I liked about that situation was that I learned to ask for the broader context first and then bring a practical alternative rather than treating it like a yes-or-no disagreement.
At a small startup I was asked by our product lead to add a third-party analytics script right before a public beta so they could get detailed user funnels. I was uneasy because the script collected more user identifiers than our consent flow covered and I worried about privacy and compliance down the line. Instead of saying no, I built a tiny alternative that captured only anonymized event counts we needed for the immediate funnels and proposed we gate the full analytics behind a feature flag pending a legal review. My manager agreed to that compromise — marketing got the basic metrics for the beta, and we avoided shipping unnecessary user data while we completed the review. From that experience I learned how to raise principled concerns by pairing them with a concrete, low-risk solution.
Poor answers
One time my manager wanted me to follow an existing pattern in the codebase, but I thought my way was cleaner. I explained that the old approach was kind of outdated and kept making the case in our meeting because I wanted to make sure we did it right. In the end we used the existing pattern, and I implemented it, although I still think my approach would have been better. It was useful because I showed that I'm willing to speak up even when I disagree with my manager.
Question Timeline
See when this question was last asked and where, including any notes left by other candidates.
Early June, 2026
Amazon
Senior
Early June, 2026
Amazon
Senior
Mid May, 2026
Lyft
Mid-level
Hello Interview Premium
Your account is free and you can post anonymously if you choose.