Tell Me About a Time You Received Difficult Feedback: Complete Graduate Interview Guide 2026

"Tell me about a time you received difficult feedback" (also phrased as "describe a time you were criticised", "how do you respond to constructive criticism?" or "tell me about feedback you disagreed with") is a staple of graduate and early-career interviews. The reasoning is practical. Early in a career, most of your improvement comes from other people telling you what to do differently: managers reviewing your work, clients pushing back on a draft, senior colleagues rewriting your analysis. An employee who bristles, argues or quietly ignores feedback learns slowly and is hard to manage. One who listens, clarifies and adjusts becomes useful quickly.

The question also tests honesty. Everyone has received feedback that stung, so an answer claiming you have never really been criticised sounds either evasive or unaware. Interviewers are not trying to catch you out; they want to see how you behave when your self-image takes a small knock. The table below shows what is usually being assessed as you speak.

This question sits close to "tell me about a time you failed" and to the weaknesses question. If you have prepared those, you already have raw material; see our guides to answering the failure question and strengths and weaknesses. The difference here is that the spotlight is on your reaction to another person's view, not on the mistake itself.

A good feedback story has three ingredients. First, the feedback must have been genuinely difficult: it touched something you cared about, or it was blunt, or you initially disagreed. Second, it must have been specific and fair enough to act on, such as "your presentation lost the audience in the middle" rather than "you are not a good communicator". Third, you must be able to show a visible change afterwards, ideally one that a second person noticed.

Graduates often worry they have no suitable story because they have limited work experience. In practice, academic and extracurricular settings produce excellent examples, because feedback is built into them: dissertation supervisors, lab leads, society treasurers, sports coaches and part-time shift managers all give it regularly.

Avoid the two extremes

Do not choose feedback so trivial that it shows nothing, such as "I was told I'm a perfectionist". Interviewers recognise this as the weaknesses cliché in disguise. Equally, avoid feedback that would worry an employer about the core of the job. A candidate for an audit role who describes being repeatedly told they were careless with numbers is giving a hard story to recover from. The ideal is a real weakness that is not central to the role, which you have clearly worked on. If you are unsure how to calibrate this, our weaknesses interview question guide covers the same balance.

STAR works well, but on feedback questions candidates tend to spend almost all their time on the Situation (what went wrong) and almost none on what they did. HEAR-ACT keeps STAR's discipline while weighting the answer towards your response. The first half covers how you received the feedback; the second half covers what you did with it.

Worked through in one paragraph

"On a group presentation, a teammate told me afterwards that I had dominated the Q&A and that quieter members felt they had nothing to add (Headline). I was a bit defensive at first because I thought I was helping, but I thanked her and asked for an example (Emotion, Ask). She pointed to two questions I had answered that were really aimed at others. After thinking it over, I accepted that my enthusiasm was crowding people out, although I still felt answering quickly had kept the session flowing (Reflect). For the next project I agreed roles in advance, pointed questions towards the person who owned that section, and held back my own answers until others had spoken (Act). In the follow-up I asked the same teammate for feedback, and she said the Q&A felt much more balanced; our module mark also noted strong team coordination (Check). I now agree who leads each topic before any presentation (Take-away)."

Notice that the example includes an honest flash of defensiveness. That is deliberate: interviewers trust a candidate who admits an initial reaction and then shows how they moved past it far more than one who claims to have welcomed all criticism with a smile. For help structuring concise stories in general, see our guide to answering "tell me about yourself".

The examples below illustrate structure; they are not scripts. The details are invented for demonstration, and your own answer must come from real experience, because interviewers will probe with follow-ups. Use them to see how the framework adapts to different backgrounds.

Example 1: The essays that described rather than argued

"In my second year, my history supervisor returned an essay and said it was well researched but read like a summary rather than an argument (Headline). I was disappointed, because I had worked hard on the reading. I asked her to show me a paragraph where the argument was missing, and she pointed out that I had listed three historians' views without saying which I found most convincing (Emotion, Ask). I realised I had been treating more reading as a substitute for taking a position (Reflect). For the next essay I wrote a single-sentence argument first, structured each paragraph as evidence for it, and sent her the plan before I wrote the full draft (Act). She said the plan was far clearer, and my mark rose by a full grade band on that essay and held on the next (Check). I now draft the conclusion first for any written piece (Take-away)."

Example 2: The till errors

"Working in a shop, my manager took me aside and said I was fast but made too many small errors on the till, which cost her time at close (Headline). I felt a bit embarrassed because speed was what I was proud of. I asked how often it was happening, and she showed me the last two weeks of discrepancies (Emotion, Ask). I accepted that the pattern was real and that I was skipping a final check to save seconds (Reflect). I introduced a quick read-back of each order before confirming, and practised until it did not slow me noticeably (Act). Over the next month my discrepancies fell to almost none, and she later asked me to train a new starter in the same habit (Check, Take-away)."

Example 3: Using the table as a prompt

The placement example follows the same pattern: the key move is that you rewrote the emails and then watched whether replies sped up, rather than just promising to be clearer. Write each story out in full and time it. If you run out of detail, either your real experience has more to offer or you should choose a different story. Our competency-based interview guide shows how to build a bank of stories like these.

The question is worded similarly across employers, but each organisation emphasises slightly different qualities. Do not claim to share a company's values cynically. Use what employers say publicly to decide which part of your story to lead with.

Amazon's Leadership Principles are published on its careers site, so read them there and choose a story that maps naturally to one or two. Our Amazon online assessment guide covers the wider process, and the Microsoft online assessment guide does the same for Microsoft.

At professional-services firms, expect follow-ups such as "how did you feel at the time?" and "how do you ask for feedback now?". The Big Four process commonly combines online tests, a video interview and a final round, and you can see how one firm structures it in our PwC assessment centre guide. Feedback attitudes are also observed live at assessment centres, where assessors note how you respond to a challenge from other candidates; see the group exercise guide.

Interviewers rarely use identical phrasing. If you know what each variation is really probing, you can reuse the same prepared story and shift the emphasis.

The "feedback you disagreed with" variant needs care. The wrong answer is to describe how you proved the other person wrong. The right answer shows that you asked for evidence, accepted what was valid, and respectfully explained your view on the rest. A related competency, staying composed under scrutiny, is covered in our guide to handling pressure in interviews, and a wider set of prompts appears in our resilience interview questions.

These are the patterns that most often turn a promising example into a weak one.

Mistake one is the most common among well-prepared candidates, and interviewers have heard it many times. The remedy is to be specific and slightly vulnerable. Instead of "I care too much", say "I was told my reports were too long for senior readers to use", which is real, fixable and credible.

To rehearse, record yourself and listen for these patterns, or ask a friend what they remember afterwards. If nerves are a problem on the day, the techniques in our guide to managing SHL test anxiety also work well in interviews.