What was a situation where you didn't agree with your manager or superior's decision?
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.
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
You do not need authority to disagree well; you need clarity, professionalism, and emotional control.
Good examples
🟢I said I saw a risk with the plan and wanted to walk through my reasoning, while making it clear I understood my manager had more context than I did.
🟢I raised the concern privately and framed it around the impact I expected rather than attacking the decision or the person.
Bad examples
🔴I told my manager the approach made no sense and that we were going to regret it.
🔴I brought it up in the team meeting because I wanted everyone to see there were problems with the decision.
Weak answers signal ego or public escalation; strong answers show directness without disrespect.
Valuable
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
Early June, 2026
Mid May, 2026
Hello Interview Premium
Your account is free and you can post anonymously if you choose.