If you sometimes respond defensively to feedback, explain the behavior you noticed and the steps you use to understand the feedback before reacting. The goal is not to agree with every comment. It is to evaluate it fairly and respond with evidence.

Use this topic only if it reflects your experience. Do not claim a personality label or invent a conflict. Focus on a specific work habit you are changing.

What does the limitation look like?

Perhaps you began explaining your intentions before listening to the concern, or treated a request for clarity as a challenge to your competence. Describe the behavior without blaming the reviewer for raising it.

Keep the example bounded. You do not need to disclose a private performance review or identify a colleague. A permitted discussion about a document or feature can be enough.

What process can help?

  1. Pause before replying.
  2. Restate the concern in your own words.
  3. Ask for an example if it is unclear.
  4. Decide what change or check would address it.
  5. Review the result with the person where appropriate.

This is a practical method, not a guarantee that all feedback is correct. If evidence contradicts a suggestion, explain that respectfully and keep the conversation on the work.

Illustrative answer

Fictional sample: “I have sometimes explained my reasoning too quickly when receiving feedback, before checking that I understood the concern. In a review of a written explanation, I realized I was defending the content while the reader was asking for a clearer structure. I now restate the feedback and ask for a specific example before proposing a revision. I am still practicing that pause, especially when I have spent a long time on the work.”

Use a real example of your own. Do not claim the revision was praised or improved a metric unless that actually happened.

How do you show progress?

Describe a later case where you understood the concern, made a focused change and checked whether it helped. The evidence might be that the reader could now follow the explanation or that a test addressed the identified risk.

Do not turn the answer into a story about proving the reviewer wrong. Even when a suggestion was not adopted, explain how you evaluated it and reached a constructive decision.

What if feedback is vague?

Ask what the person observed and what a better outcome would look like. “Can you point to the part that was hard to follow?” is more useful than guessing at a complete rewrite.

Keep tone and content separate. A poorly delivered comment can still contain a valid issue, but you do not need to accept inappropriate behavior as a condition of learning. Use the organization's appropriate support process if needed.

Prepare for the follow-up

Be ready to describe feedback you accepted and a case where you discussed an alternative. That shows thoughtful evaluation rather than automatic compliance.

A strong weakness answer identifies the reaction, its effect, a repeatable pause-and-clarify process and an honest current state. It should leave the listener understanding how your next review conversation would be different.

References and next practice

careerservices.fas.harvard.edu — career · career.virginia.edu — star

Browse interview topics · Practise a question in Interview Challenge · Strengths and Weaknesses Interview Answers That Use Real Evidence