How to Answer Tell Me About a Time You Received Criticism

STAR method answers “tell me about a time you received criticism” with a specific situation, your reaction, the behaviour you changed, and credible proof. CoPilot Interview recommends about 90 seconds to two minutes, with at least half covering change and proof to demonstrate Coachability.

What should I say first when asked about criticism?

An interview response might describe receiving feedback about moving too quickly to solutions in design meetings. I asked for examples, started pausing for questions before proposing an answer, and asked for follow-up feedback. The change helped my discussions become more balanced, and two colleagues later trusted me to lead design reviews.”

That answer works because it starts with the criticism itself. It then shows your response and the result. Do not open with a long project history or a general weakness. Do not turn the story into a failure story. The centre is received feedback.

Practise this line:

“The point is what I did after hearing it.”

Choose a recent, genuine example. Name the behaviour. State what you did differently. Finish with evidence that someone noticed, the work changed or the outcome improved. The linked article describes a five-step structure. One approach emphasizes explaining what happened after the criticism.

Speak naturally. Memorise the sequence, not every word. Aim for roughly 90 seconds to two minutes, depending on the interview context. A short answer can sound evasive. A long account can bury the change. The interviewer should hear the feedback, your response and credible proof without waiting for the point.

What is the interviewer really checking?

Then they assess self-awareness, emotional regulation, curiosity, judgment, follow-through and maturity, according to Career Test Prep’s interviewer-assessment table and HEAR-ACT guide.

Use this spoken diagnostic:

“I was surprised, but I did not dismiss the point. I asked what they had observed.”

A measured reaction shows emotional control. You heard the criticism without letting a fight-or-flight response take over. Asking for examples shows curiosity. Testing the evidence shows judgment rather than automatic agreement. A repeatable change shows follow-through. A later check with the critic, manager or team shows accountability. Together, these signals create maturity: you can absorb useful information and act on it.

The usual advice says to accept criticism, avoid defensiveness and show improvement. That remains sound when the feedback is accurate and relevant. It breaks down when interviewers treat coachability as obedience. A strong answer does not prove obedience to every criticism. It proves judgment by testing the feedback, accepting the valid part and explaining a respectful decision when the evidence does not support all of it.

If criticism seems unfair, you can explain your perspective assertively while remaining factual and respectful. Consider checking your understanding of feedback before acting on it. Use this line:

“I agreed with the concern about clarity, but not with the proposed fix, so I tested both views against the project evidence.”

Do not use disagreement to disguise defensiveness. Acknowledge the concern. Ask for evidence. Act on the valid part. Explain the decision without attacking the critic. Refusing to change when the evidence supports the criticism still signals poor coachability.

What structure keeps the answer focused?

(CoPilot Interview’s five-step structure and engineering examples)

Keep Situation short. Use the rest of STAR to explain the feedback, your reaction, the check you made, the change you introduced and the proof that followed. The sequence described in the linked article is feedback, reaction, check, change and proof. The interview answer should centre on the response, not the original flaw.

Its largest share goes to action. A simpler structure separates context, feedback, action and result. (Career Test Prep’s four-part timing structure) These are editorial conventions, not a single reconciled timing rule. The sources differ on how much space each part deserves.

The right story depends on what happened after the criticism.

Choose the right criticism story before you rehearse

Situation	What to say	What proof to use	Do not claim
Fair feedback from a manager or reviewer	Quote the behaviour. Explain the routine you changed.	A later review or changed outcome.	That agreement alone proves improvement.
Partly fair feedback	Separate the valid observation from the disputed conclusion. State the action you accepted.	A later observation or changed outcome.	That you accepted every proposed fix.
Feedback you rejected	Explain the evidence you checked, the respectful question you asked and why you retained your approach.	Project evidence or a later review.	That disagreement means the critic was incompetent.
Very recent feedback	State the first action taken and the next check-in.	The planned check-in, not a result.	That improvement already exists.
Repeated feedback	Show the pattern and the mechanism that finally changed it.	Later feedback or consistent behaviour.	That one attempt solved the pattern.
No numerical metric	Use later feedback, a changed review outcome, another person noticing or a clearer work result.	Credible non-numerical proof.	An invented number.

The decision rule is simple: describe only the proof you genuinely have. A useful response can show that you checked the feedback before acting, then describe the change and the evidence behind it. (CoPilot Interview; Career Test Prep HEAR-ACT guidance)

Use this fill-in script:

“In [setting], [person] told me [close paraphrase]. My first reaction was [honest but brief]. I checked [evidence], changed [specific behaviour], and saw [result or later observation].”

Choose a mechanism you could repeat: a design-document failure-modes checklist, stacked pull requests, a blocking/suggestion/nit review convention, a written status-update summary or a formal feedback loop. The mechanism turns “I improved” into something the interviewer can test. It also gives you a precise answer when they ask, “What did you change in practice?”

What should three different candidates say?

Graduates should show learning. Experienced candidates should show judgement. Career changers should show transfer. (CoPilot Interview’s graduate, mid-level and senior examples; Remote Rocketship’s software, marketing, senior and career-change examples; Career Test Prep’s academic, retail and placement examples)

Early-career candidate: code review

Example script. 92 words.

In my first software placement, a reviewer told me my code reviews focused on style and missed risks. I felt embarrassed because I had spent time writing detailed comments, but I asked for examples. I asked what a stronger review looked like and changed my process. I started checking data flow, edge cases and error handling before commenting on formatting. On my next reviews, I caught a real bug in a smaller pull request, and the team adopted a clearer review checklist. The experience taught me to check impact before appearance.

This works for a graduate because the evidence comes from a changed review habit and a real bug, not from overstated seniority. (CoPilot Interview’s graduate, mid-level and senior examples)

Experienced candidate: design review

Example script. 98 words.

During a design review, two engineers told me I was jumping to solutions before hearing competing concerns. My first reaction was defensive because I knew the system well. I reviewed the meeting notes and saw that I had interrupted several risk discussions. I changed the agenda: first, I ask each person for constraints and failure modes; then I offer my proposal. I now ask for competing views before proposing mine. Later, colleagues asked me to facilitate design reviews, and the discussions produced clearer decisions. I still bring a strong view, but I make space for better evidence first.

This answer presents judgement rather than obedience. The candidate accepts the observed behaviour, changes the meeting mechanism and shows later trust. (CoPilot Interview’s graduate, mid-level and senior examples; Remote Rocketship’s software, marketing, senior and career-change examples)

Career changer: customer calls

Example script. 96 words.

In my previous teaching role, a customer told me that my calls included too much background before reaching the decision. I was surprised because I wanted people to have full context. I checked my call notes and found that customers often asked me to repeat the next step. I began opening with the decision, followed by three short points and a written summary. Calls became shorter, and customer satisfaction moved from the middle of the team to the top three within one quarter. I now lead with the action, then provide detail when the listener needs it.

These examples show transferable change without pretending that the old role was identical. (Career Test Prep’s academic, retail and placement examples)

How should the story change for the role you want?

Company principles and the interview format can inform your emphasis, but they do not dictate a single required answer.

For a management example, describe how feedback changed a team process as well as your own behaviour. In a performance review, say: “I changed the review process so people could raise concerns earlier.” Then name the mechanism. You added a pre-review question, invited dissent in one-to-ones or created a short team follow-up. An incident postmortem can show the same judgement. Explain what changed and what the team noticed later.

A senior individual contributor should show judgement and influence through a design review. Describe a design-document failure-modes checklist, a changed feedback loop or a clearer decision record. Engineering candidates can describe concrete process changes and observable evidence from their work. Say: “I tested the feedback, kept the valid part and changed the decision process.”

Graduates can use coursework, group projects, placements or part-time work when professional evidence is limited. Academic and early-career experiences may be appropriate sources of examples. A career changer should name the transferable behaviour. They should not pretend that the original setting matched the new role.

Choose proof that fits the target job. CSAT is one possible customer-facing signal. Median time-to-merge is one possible engineering signal. Neither is a required outcome. Use the truthful metric your situation produced, or use a later review comment, changed decision, follow-up invitation or another person’s observation.

Microsoft’s growth mindset can serve as a prompt, but it does not establish a preferred script. A HireVue interview format provides context, but it does not endorse a particular framework.** Build the story from what actually happened.

Which answers should you avoid, and why?

“I care too much about quality” gives the interviewer no observable change or proof (Remote Rocketship).

Avoid the humblebrag. Replace “I care too much about quality” with a behaviour that affected other people. Then name the mechanism you changed: “I added a review checklist and agreed priorities before starting.”

Avoid blank denial. “I have never received criticism” sounds implausible and leaves no evidence to assess. Say: “The most useful recent feedback I received was…” Use a real example from work, study, volunteering or a placement.

Avoid the blame script. Do not say, “My manager was wrong and did not understand the situation.” Say: “I checked the examples, agreed with the concern about clarity, and explained where the proposed solution did not fit.” If criticism seems unfair, you can respond assertively, while keeping the answer factual and measured.

Avoid vague proof. “I worked on it and became better” proves nothing. Say: “I introduced a review checklist, asked for feedback after the next cycle and received a clearer assessment.”

Exclude serious misconduct, core incompetence, confidential details and a trivial typo. Do not invent a story. Do not invent an example; use a truthful experience or explain that you would need to choose a different example. If memory fails, say, “I need a moment,” then draw on a real project, placement or group experience.

How do you practise the answer out loud in two minutes?

An answer of about two minutes can be divided between context, feedback, action and result; recording yourself can help you review the delivery.

Aim for this practice split:

• Opening: State the setting, the criticism and your first reaction.
• Middle: Explain what you checked and the behaviour you changed.
• Close: Give the proof, then name the lesson you carry forward.

Keep the change and proof longer than the setup. Consider giving the action and outcome at least half of the answer so the response shows what changed and how you assessed it.

Use a STAR story builder with five prompts:

• What exactly did the person say?
• What did I feel first?
• What evidence did I check?
• What behaviour or process did I change?
• How do I know the change worked?

Record one complete answer. Do not restart after a stumble. Listen once for pace, filler words, defensive emphasis, vague verbs and excessive setup. Mark every phrase such as “I improved” or “I worked on it”. Replace it with evidence: a later review comment, a changed outcome, a colleague’s observation or a follow-up invitation.

Practise again without reading. Keep the sequence, not the wording.

Then add follow-up questions. Start with:

“What did you disagree with?”

Answer:

“I accepted the observation, tested the proposed fix and kept the part that best matched the evidence.”

Rehearse these probes aloud:

• “What is the most recent feedback you received?”
• “Would you do anything differently?”
• “How did the other person know you changed?”
• “What if the criticism was repeated?”
• “What did you do before you had a result?”

An AI mock-interview tool may support spoken-answer practice and provide an answer score out of 10; treat that score as one feedback signal rather than a definitive assessment (Tell Me About a Time You Received Critical…). An AI interviewer may use an interactive format with follow-up questions and an answer score; use those results as practice feedback rather than a definitive assessment. A recorded interview likewise benefits from a concise structure, specific evidence and a clear explanation of what changed. Answer aloud, review the recording and repeat without memorising every sentence.

Razen Rehearsal Sandbox: The criticism story under panel pressure

You are interviewing for a senior product manager role after leading a £180,000 client launch due on 30 June. The panel wants to know whether you accept feedback thoughtfully or simply agree with whoever has authority, so this answer must show both coachability and judgment.

Setting. A final-stage interview in a glass meeting room. Maya is the candidate; Daniel is the hiring manager; Priya is the second interviewer, focused on stakeholder judgment.

Cast

• Maya, Candidate answering the criticism question. At stake: She needs to show growth without sounding obedient or defensive.
• Daniel, Hiring manager testing coachability. At stake: He needs evidence that Maya responds well when senior stakeholders challenge her.
• Priya, Second interviewer probing judgment. At stake: She wants to know whether Maya can separate useful feedback from a poor proposed fix.

The Wrong Way

Daniel: Tell me about a time you received criticism.

(He leans forward and leaves the question open; his voice stays neutral.)

Maya: My director said I was too focused on my own view during the June launch. I realised she was right, so I changed my whole approach and started agreeing with stakeholders earlier.

(She speaks quickly, nods repeatedly and keeps both hands clasped.)

Daniel: What specifically did you change?

(He tilts his head and waits; one finger rests on his notebook.)

Maya: I listened more. I stopped pushing back so much, and the launch went well. I think the team appreciated that I was more flexible.

(Her pitch rises on the final sentence; she glances down before saying “went well.”)

Priya: Did you think any part of the criticism was unfair?

(She looks up from her notes and asks without smiling.)

Maya: Not really. She was my director, and she knew the account better than I did. I probably should have followed her direction from the start.

(Maya gives a small laugh and lifts both palms, as if closing the subject.)

Daniel: How did you know the change worked?

(He pauses, then taps the page once.)

Maya: There weren't any complaints after that. So I took it as a sign that I had improved.

(She fills the silence immediately and shifts in her chair.)

Why it fails. Maya turns a partly fair criticism into a story about obedience. The lines “I stopped pushing back so much” and “there weren't any complaints” show no test, specific behaviour or credible proof. Priya's question exposes the missing judgment, and Maya gives authority more weight than evidence.

The Right Way

Daniel: Tell me about a time you received criticism.

(He leans forward and leaves the question open; his voice stays neutral.)

Maya: During a review of the June launch, my director said I moved too quickly to solutions and shut down debate. I was surprised, but I checked the meeting notes and asked for two examples before responding.

(She slows on “shut down debate,” keeps her shoulders still and looks from Daniel to Priya.)

Daniel: What did you find?

(He writes one short note, then looks back at her.)

Maya: The observation was fair. I had answered two risks before the team had finished describing them. I changed the meeting format: ten minutes for objections first, then I proposed options. I also asked my director to review the next session.

(Her hands separate to mark the two stages; she pauses after “fair.”)

Priya: Did you accept her proposed fix as well?

(She raises one eyebrow and keeps her pen still.)

Maya: Not entirely. She wanted every decision to wait for a full group discussion, but that would have put the 30 June launch at risk. I accepted the concern about debate, tested a shorter discussion block and kept the decision deadline.

(Maya lowers her voice on “not entirely,” then meets Priya's eyes.)

Daniel: What showed you the change worked?

(He closes his notebook and gives her the full pause.)

Maya: My director said the next review was more balanced, and the engineering lead started raising risks before I asked. We still made the launch date. The lesson was to change the behaviour the evidence supported, not surrender the decision itself.

(She takes a breath before the result, then finishes with both feet planted.)

Why it lands. Maya accepts the valid observation, names the evidence she checked and keeps the part of the plan that protected the deadline. Her line “Not entirely” costs her the easy approval of total agreement, but it proves respectful disagreement. Priya changes the outcome by inviting that distinction, while Daniel receives a clear action and two forms of proof.

<aside class="razen-coach-card" data-razen-scenario="the-criticism-story-under-panel-pressure"> <p class="razen-coach-card__title"><strong>Practice this live.</strong></p> <p><a class="razen-coach-card__button" href="https://razenai.com/coach?scenario=the-criticism-story-under-panel-pressure&amp;article=how-to-answer-tell-me-about-a-time-you-received-criticism&amp;utm_source=razen_blog&amp;utm_medium=rehearsal_sandbox&amp;utm_campaign=how-to-answer-tell-me-about-a-time-you-received-criticism">Click here to boot up the Razen AI voice coach for this exact scenario.</a></p> </aside>

Delivery playbook

Tone shifts

• Start factual and compact when naming the June launch and the criticism. Shift to a lower, steadier tone on “The observation was fair,” then become firmer on the retained decision deadline.
• Sound curious, not apologetic, when saying “I checked the meeting notes.” Use a measured downward finish on “Not entirely” so the disagreement does not sound like a challenge.
• Let the final lesson sound reflective rather than polished: slow slightly on “the behaviour the evidence supported” and avoid raising your pitch at the end.

Pause placement

• Pause for 2 seconds after Daniel asks the opening question, then begin with “During a review of the June launch.”
• Pause for 1 second after “The observation was fair” before explaining the two examples and the meeting change.
• Pause for 2 seconds after Priya asks whether you accepted the proposed fix. Use that space to stop yourself from saying an automatic “yes.”
• Pause for 1 second before “We still made the launch date,” so the result lands as evidence rather than a boast.

Physiological cues

• Keep both feet flat when Daniel asks for proof; do not rock forward to fill the silence.
• On “Not entirely,” release your clasped hands and hold Priya's eye line for one full sentence, then return your gaze to Daniel.
• Breathe out through your nose before naming the disputed fix. Suppress the quick laugh and upward shoulder lift that signal discomfort.
• Use one hand to mark “ten minutes” and the other to mark “then options”; stop gesturing once you reach the result.

Recovery moves

• If you say, “I agreed with everything,” correct it immediately: “Let me be more precise. I agreed with the concern, but I tested the proposed fix against the launch deadline.”
• If you give vague proof such as “the launch went well,” say: “The stronger evidence was my director's next-review comment and the engineering lead raising risks before I asked.”
• If Priya sounds sceptical, say: “You’re right to test that. The change was not simply listening more; it was changing when I invited objections while keeping the decision date.”
• If you lose the sequence, say: “The short version is: I heard the criticism, checked two examples, changed the meeting structure and confirmed the result at the next review.”

Watch it explained

Frequently asked questions

How long should my answer to “Tell me about a time you received criticism” be?

Aim for about 90 seconds to two minutes. Keep the setup short and spend at least half the answer on the behaviour you changed and the proof that the change worked. The exact timing is editorial guidance, not a fixed interviewer rule.

What if I partly disagree with the criticism?

Separate the valid observation from the disputed conclusion. Say what evidence you checked, what you changed and what you retained. For example: “I accepted that my updates lacked context, but the proposed format was too long, so I tested a shorter written summary.”

What if I have no numerical result?

Use credible non-numerical proof. A later review comment, a changed outcome, another person noticing the behaviour or a follow-up invitation can show progress. Do not invent a metric simply to make the story sound stronger.

Can graduates use university criticism examples?

Yes. Coursework, group projects, placements, part-time work, sport and volunteering can work when professional experience is limited. Experienced candidates should prefer a recent workplace example when one exists, because it gives the interviewer more relevant evidence.

How do I avoid sounding rehearsed?

Memorise the sequence, not every sentence. Practise the five prompts—feedback, reaction, check, change and proof—then answer aloud in different words. Record one take and remove filler, excessive setup and defensive wording.