Behavioural interview
Answering 'Tell me about a time you disagreed with your manager'
“Tell me about a time you disagreed with your manager.”
Reviewed by Saadan Naqvi
Direct answer
Answer by describing a technical or architectural disagreement where you prioritised project outcomes over personal bias. Explain how you gathered objective data, presented your case constructively, respected their final decision, and worked collaboratively to deliver the software, demonstrating professional maturity and technical leadership.
Practising this one out loud? It comes up in the General track in Ranked Arena. Or check your own written answer ↓
What the interviewer is actually assessing
- Ability to disagree constructively using technical data and metrics rather than emotion.
- Professional maturity to support a decision once a final direction is chosen.
- Communication skills when translating complex technical trade-offs to management.
- Focus on project delivery and team alignment over being right.
A weak answer, and why it falls short
The answer below was written to be typical, not terrible. Here is where it comes apart. Everything after it is real output from the same grader the tool on this page uses — the verdict, the diagnosis, and the rewrite were produced by running that answer through it.
Typical answer · Senior Software Engineer
When I disagree with my manager, I always try to keep things focused on the technical facts. In my last role, we often had disagreements about architecture, like whether to migrate our core database to a NoSQL solution or stick with PostgreSQL. My manager was really pushing for the NoSQL database because of scalability promises, but I felt our relational schema was actually saving us from a lot of data integrity issues. Usually, in these situations, I don't just say 'no.' I like to set up a quick proof of concept and put together a comparison document that highlights the latency, cost, and maintenance overhead of both options. Then we sit down and go through the data together. It really helps de-escalate things and keeps the focus on what's best for the project. We usually end up finding a compromise that works for both of us and keeps the timeline on track.
What they answered instead
Their general philosophy and routine process for handling technical disagreements, using a recurring database debate as a hypothetical backdrop.
Missing piece
A specific, single instance of the disagreement, including the actual decision made, the resolution process for that exact event, and the final outcome.
Why
The candidate described a recurring topic of disagreement (Postgres vs. NoSQL) but shifted to explaining their general, habitual approach ('Usually, in these situations...') instead of walking through one concrete, completed story.
Stronger rewrite
In my last role, my manager wanted to migrate our core database to NoSQL for scalability, while I believed staying on PostgreSQL was critical for our data integrity. To resolve this, I built a quick proof of concept simulating our peak write loads on both databases and compiled a comparison document detailing latency, cost, and maintenance overhead. I sat down with my manager to review the data, which showed that NoSQL would increase our maintenance overhead by 30% without significant latency gains. Based on this evidence, we agreed to keep PostgreSQL but optimized our indexing strategy, which successfully handled our traffic spike without any data integrity issues.
Practise tip: When asked 'Tell me about a time,' use the STAR method and stick to a singular event. Avoid words like 'usually,' 'often,' or 'generally' which turn a specific story into a generic process description.
Now check your own answer
Paste how you would answer this question. You get the same thing you just read — the verdict, what you answered instead, the missing piece, and a rewrite — on your own words. No account needed.
This grades what you wrote. Ranked Arena grades what you say, on a timer.
Ranked Arena
Typing it is easy. Saying it under a timer is the interview.
Ranked Arena puts questions like this one in front of you on a countdown, on camera and mic, and grades what you actually said — structure, specificity, and impact. Every match earns Interview Points and moves you up the ladder from Wood to Cracked. The General track carries purely behavioural prompts — leadership, conflict, ownership.
Three ranked battles a month on a free account, drawn from a bank of 500+ questions. No webcam needed — mic-only still gets graded and ranked.
Common questions
Should I choose a technical or a personal disagreement?
Always choose a technical, architectural, or process-related disagreement. Discussing personal conflicts suggests a lack of professionalism. Focus on topics like system design, tooling, or resource allocation, where the disagreement stems from a shared desire to deliver high-quality software.
What if my manager was wrong and the project failed?
Frame the outcome constructively without blaming your manager. Focus on how you mitigated risks after the decision was made, what the team learned from the post-mortem, and how you worked together to resolve the resulting issues.
How do I show that I respected their authority?
Explain that you presented your evidence clearly but accepted their final decision without resentment. Senior engineers must demonstrate 'disagree and commit' behaviour, showing they can work diligently to make a project succeed even if they preferred a different technical path.
More questions like this