'How Do You Handle Feedback You Disagree With?' Interview Answer: Examples

A strong answer to "how do you handle feedback you disagree with" shows a sequence: listen fully, find the part that is true, state your disagreement with evidence, agree a way to test it, and report back on the result. Interviewers ask because feedback you agree with is easy, and because both reflexive compliance and reflexive defence are problems. The question is a harder variant of tell me about a time you received critical feedback and how do you handle criticism, and it borrows its structure from disagreeing with your manager. This page explains what the interviewer is really asking, gives a structure that works, three sample answers of forty to eighty words to adapt, the mistakes that sink the answer, and a ten-minute practice routine.

What the interviewer is asking

Whether you can separate the feeling from the content, whether you look for the true part before defending the rest, whether you disagree with evidence rather than volume, and whether you can live with being overruled. They are also checking that you do not simply fold; a candidate who accepts all feedback regardless of merit is a candidate who will implement bad ideas. The strong story includes a disagreement, a test, and an outcome in which someone, possibly you, turned out to be wrong.

A structure that works

1. Listen and find the true part, out loud.
2. State the disagreement with evidence, once, calmly.
3. Agree a test: a trial period, a data check, a second opinion.
4. Report back with the result, whichever way it went.

Three sample answers

You were right

A manager told me my customer emails were too long and should be cut to three lines. I agreed the short ones worked for simple questions, and said that for billing disputes the detailed ones had cut repeat contacts. I proposed a two-week test: short replies on simple tickets, detailed on disputes, and we would check repeat-contact rates. The split held up in the data, and it became the team guideline. The useful part was that I had never measured it before she pushed.

You were wrong

A senior engineer said my service design was over-engineered. I thought he was wrong and said why: the extra layer handled a failure mode I had seen before. We agreed to build the simpler version behind a flag and watch it for a month. The failure mode never happened at our scale, and the simpler version was easier to maintain. I told him he was right in the team channel, which cost me nothing and bought a lot.

Partly both

My director said I was slow to escalate problems. I disagreed; I thought I escalated at the right time. I asked for the two cases she had in mind, and in one she was right and in one I still think I was. I started sending a short weekly risk note so she could see what I was tracking, which addressed her real concern, visibility, without my escalating things I could handle. The note is still going two years later.

Mistakes that sink the answer

• Agreeing with everything to seem coachable.
• Defending with volume rather than evidence.
• No test or follow-up; the story just ends.
• A story where you were right and the other person looks foolish.
• Not finding any true part in the feedback.

A ten-minute practice routine

1. Recall feedback that was wrong, or partly wrong; that is the story.
2. Write the sequence: true part, disagreement with evidence, test, result.
3. Say it aloud in sixty to ninety seconds; keep the tone respectful toward the person.
4. Answer it in the browser demo or a mock interview and compare with the structured answer.
5. Prepare a second story where you turned out to be wrong, in case the first makes you look infallible.

Where CoPilot Interview fits

CoPilot Interview is an AI interview assistant whose browser demo at /try lets you answer this question aloud and compare your answer with a structured one, free and with no signup, and whose free AI mock interview asks it in the context of your résumé and the job description and scores your spoken answer out of ten. The free plan gives 15 minutes a day of live help in sessions of up to 15 minutes, with AI mock interviews included. Practice is the use nobody objects to; if you consider live help in a real interview, follow your employer's rules.

Disclosure: CoPilot Interview is our product, so weigh what we say about it accordingly.

Frequently asked questions

How do you answer 'how do you handle feedback you disagree with'?

Listen and name the true part, state your disagreement with evidence, agree a test, and report back with the result whichever way it went.

Should the story end with me being right?

Not necessarily. A story where the test proved the other person right, and you said so, is often stronger.

How is this different from the critical-feedback question?

That one is about taking feedback on board. This one is about disagreement, so the evidence and the test are the heart of it.

How long should the answer be?

Sixty to ninety seconds.