How Do You Handle Criticism? Best Interview Answers (Examples)

To answer "How do you handle criticism?", say that you treat feedback as information to improve, then prove it with one short, real story: what the feedback was, how you responded in the moment (you listened, asked questions, did not get defensive), what you changed, and what improved afterwards. Keep the tone calm and positive, give credit to the person who gave the feedback, and never pick an example that makes you sound careless or makes them sound unfair.

Below: why interviewers ask it, a simple structure, sample answers for freshers and experienced candidates, and the mistakes to avoid.

Why interviewers ask how you handle criticism

Every job involves feedback: from a manager in a review, from a senior on your code or report, from a client who is unhappy. Interviewers ask this question to find out whether you will be easy to coach. Someone who gets defensive or upset at every comment slows down the whole team.

They are listening for:

• Self-control. Do you stay calm and listen, or argue straight away?
• Willingness to learn. Do you actually change something after feedback?
• Judgement. Can you tell useful feedback apart from noise, and still stay polite?
• Honesty. Can you admit you got something wrong?

It belongs to the family of behavioural interview questions, so the interviewer wants a real past example, not a general promise.

Other ways the question is asked

• How do you handle criticism?
• How do you react to negative feedback?
• Tell me about a time you received constructive criticism.
• Describe a time your manager was unhappy with your work.
• How do you respond when someone disagrees with your work?
• What is the most useful feedback you have ever received?

The same prepared story answers all of these.

A simple structure for your answer

Use the STAR method, with an extra focus on what you changed:

The "what you changed" part is the heart of the answer. Many candidates say "I took the feedback positively" and stop there. That tells the interviewer nothing. Show the change.

How to pick the right example

A good example has a real mistake or gap, but not a serious one. It should be something you fixed and that is no longer a problem. Good areas to look at:

• A report, presentation or assignment that was too long, unclear or late.
• Code review comments on your first pull requests.
• Feedback that you were not updating your manager often enough.
• A professor's comments on your project or thesis.
• A customer or client complaint that turned out to be fair.
• Feedback from a mock interview or a group discussion.

Avoid examples about honesty, safety, rudeness, attendance or anything that would worry an employer. Also avoid stories where the criticism was "you work too hard". It sounds like a dodge.

Sample answers

These are illustrations written for this guide. Use them to see the shape of a good answer, and build yours from something that really happened.

Sample 1: Fresher, internship report

"I try to treat feedback as information, not as a judgement on me. During my internship at a small marketing agency, I submitted my first campaign report to my manager. It was 14 pages long. She told me it had good data but that a client would never read it, and that she could not find the main recommendation.

My first instinct was to explain why every section was needed, but I stopped and asked her what a good report looked like for that client. She showed me an older one: one page of findings and three recommendations on top, details in an appendix. I rewrote mine in that format the same evening.

She used my next two reports with the client almost unchanged. Since then, I always write the main point first, and I ask what format the reader needs before I start."

Sample 2: Fresher, college project

"In my final-year project review, our guide said our app worked but our documentation was so weak that nobody else could run it. I was in charge of documentation, so it was fair criticism of my part. I asked him which parts were the most confusing, then wrote a setup guide and asked a friend from another branch to follow it without any help. She got stuck twice; I fixed both steps. At the final review, the external examiner was able to run the project from our guide, and I still test my instructions on someone else before sharing them."

Sample 3: Experienced, code review

"In my first year as a developer, a senior engineer left over twenty comments on one of my pull requests, mostly about naming and missing tests. Honestly, I felt a bit embarrassed. I booked fifteen minutes with him to understand the team's standards instead of fixing comments one by one. He shared the style guide and a well-written module to follow. I made a checklist from it and ran through it before every review. Within a couple of months, my reviews were getting only a few comments, and later I used the same checklist to help a new joiner."

Sample 4: Experienced, client-facing role

"As an account executive, a client told my manager that my updates were confusing and arrived at random times. My manager shared this with me directly. I agreed it was fair; I had been sending updates whenever I had news. I asked the client what they needed, and we set a weekly update every Friday with the same three headings. The client mentioned in the next quarterly review that communication had improved, and I now set an update rhythm with every new client in the first week."

A short version for quick rounds

In a screening call or an HR round with little time, a 30-second answer is enough:

"I see feedback as a quick way to get better. When I get criticism, I listen first, ask for a specific example, and then change one concrete thing. For example, in my internship my manager said my reports were too long, so I started putting the key recommendation on top in one page. Her client used my later reports almost as they were."

If the interviewer wants more, they will ask a follow-up, and you can tell the full story.

What to say if the criticism was unfair

Sometimes the interviewer asks directly: "What do you do when you think feedback is wrong?" Answer calmly:

• You listen fully first, without interrupting.
• You ask for specific examples, so you understand what they saw.
• You take any part that is useful, even if you disagree with the rest.
• If you still disagree, you explain your view politely, with facts, and ideally in private.
• You accept the final decision if it is your manager's call.

This shows maturity. Never say a past manager "didn't understand anything" or "was always against me". The interviewer will wonder what you will say about them one day. The same rule applies when you talk about conflict at work.

Mistakes to avoid

• Saying you never get criticised. Nobody believes it, and it sounds like you don't listen.
• Saying "I take it positively" with no story. Give proof.
• Getting defensive while answering. Even in the story, don't spend time justifying why you were right.
• Blaming the person who gave feedback. Keep the story about what you did.
• Choosing a serious mistake. Missing a small formatting standard is fine; losing client data is not.
• No ending. Always say what improved and what you still do differently today.

How this connects to other interview questions

Your criticism story should fit with your other answers. If you say your weakness is writing long reports, the internship story above supports it nicely. If you have a failure story, make sure it is a different example, so the interview doesn't feel repetitive.

Practise the answer out loud in a mock interview, and ask the person to give you feedback on it. That is good practice for the question itself. If you need a fresh resume before applying, use the free resume builder.

Sources

This guide is interview advice, not a set of rules. The sample answers are illustrations written for this guide, not real candidates. Use examples that are true for you.