OfferDrill.

Interview questions

The hard ones

How to answer "how do you handle criticism at work?" with a real example.

This question is a trap for anyone who answers it with a personality trait instead of a story. Here's how to pick one real piece of criticism you got, say what you did about it, and land it in under ninety seconds.

Why they ask it

They want to know what happens to their feedback after they give it. Every manager has told someone the same thing three times and watched nothing change. That's expensive, and it's slow, and they're trying to find out now whether you'll be that person.

They're also checking your ego. Not whether you have one — everyone does — but whether it gets in the way. Do you argue? Go quiet for a week? Tell everyone else on the team what your manager said? Or do you take it in, ask a question or two, and adjust?

And there's a quieter thing underneath. If you can describe real criticism you received, you're telling them you've been close enough to real work to get some. People who've never been corrected have usually never been trusted with anything that mattered.

What not to say

"I love feedback. I see it as a gift."

Everybody says this and it proves nothing. The interviewer has heard it forty times this month. It also sets you up badly, because the next thing out of their mouth is "can you give me an example?" and now you're scrambling.

A fake-weakness example, like being told you work too hard or care too much.

They can tell. It reads as either dishonest or as someone who's never gotten real feedback, and both hurt. It also wastes your one shot at looking like a person who grows.

An example where the criticism turned out to be wrong.

Stories that end with "and then they realized I was right" answer a different question. You've shown them how you defend yourself, not how you take correction. Pick one where the feedback was fair and you changed something.

Criticism you clearly still resent.

The tone gives it away — a little edge on the word "apparently," a shrug, an explanation of why your old boss was difficult. Interviewers hear it instantly and assume you'll talk about them that way someday. If a piece of feedback still stings, don't use it as your example.

How to build a strong answer

  1. Pick feedback that was real and a little uncomfortable.
    Go through the last few years and find a moment someone told you something you didn't want to hear. A review comment. A peer who said your emails were too blunt. A client who said your updates came too late. It should be specific enough to repeat in one sentence, and small enough that fixing it didn't require becoming a different human being. Avoid anything involving a firing, a formal warning, or a conflict that got ugly — you don't need those stakes to answer this question well.
  2. Say the criticism out loud, in their words, without softening it.
    This is the part most people skip, and it's the part that earns you credit. "My director told me my status updates were so long nobody read them." Not "I got some feedback around communication." Vague framing makes it sound like you're hiding something. The plain version makes you sound like someone who can hear a hard thing and stay standing.
  3. Describe what you actually did — the mechanics, not the mindset.
    Not "I took it to heart." What did you change on Monday? A template. A weekly check-in. A rule that you'd read anything sharp out loud before sending it. One or two concrete moves. If you asked a follow-up question to understand the feedback better, say what you asked — that's a strong detail and it shows you didn't just nod.
  4. Close with what changed, then stop.
    Give the result in one sentence. If you have a number, use it. If you don't, a human signal works fine: "my manager brought it up in the next review as something that had turned around," or "the complaints stopped." Then be quiet. The silence after a finished answer is not your problem to fill.

Examples to adapt

These are shapes, not scripts. Say them in your own words with your own facts — anything in brackets is a detail only you know, and it has to be the true one.

Mid-career, got direct feedback from a manager on how you communicate.

About two years ago my director pulled me aside and told me my project updates were too long — that he'd stopped reading past the first paragraph, and so had most of the team. That was hard to hear, because I'd thought of thoroughness as the thing I was good at. I asked him what he actually needed from an update, and he said three things: what's blocked, what he needed to decide, and the date. So I rebuilt the format around that. Headline at the top, three bullets, detail in a linked doc for anybody who wanted it. Within about a month he was forwarding them to his own leadership, and other people on the team started using the same structure. I still write the long version for myself. I just stopped making everyone else read it.

The criticism is quoted plainly, including the part that stung. The fix is mechanical and repeatable. The result is observable. Adapt the shape, not the words — your version needs your actual feedback and your actual fix.

Early career, one internship, worried you don't have a big enough example.

During my internship at [the company] I was writing up research summaries, and after the second one my supervisor sat me down and said I was burying the recommendation at the bottom and she couldn't tell what I thought she should do. My first reaction was that I didn't think it was my place to recommend anything — I was the intern. But she said that was exactly what she wanted from me. So for the rest of the summer I led every summary with a one-line recommendation and then backed it up. She told me at my exit review it was the biggest change she'd seen over the twelve weeks. It also changed how I think about writing anything now. I put the point first.

Small stakes, real feedback, honest about the initial hesitation. Admitting "my first reaction was" shows self-awareness without making you look defensive, because you moved past it in the next sentence.

The feedback came from a peer or a client, not a boss.

Last year a client on [the account] told our account lead that I was hard to get hold of. It got passed back to me and it was fair — I was treating email as something to batch at the end of the day, and to them it looked like silence. What I changed was simple. I set a rule that anything from a client got a response within four hours, even if the response was just "got it, I'll have an answer Thursday." That one habit did most of the work. The same client renewed at the end of the year, and when we did the wrap-up call, responsiveness was one of the things they called out as improved.

Shows you take feedback seriously no matter who it comes from, and the fix is one clear rule anyone can picture. Use your own client, your own turnaround time, your own outcome.

What comes next

Answer this one well and the interviewer usually goes here:

  • Can you tell me about a time you got feedback you disagreed with?
  • How do you give criticism to someone else?
  • What's the hardest feedback you've ever gotten?
  • What would your last manager say you need to work on?
  • How do you know when your work is good enough?
  • Have you ever gotten the same feedback more than once?

Say it out loud before it counts.

Reading a good answer and giving one are different skills, and the gap shows up in the room. Offer asks you this question out loud, on a clock, and tells you what landed. The first one is free.

Practice this out loud

You've been corrected at work and you fixed something — that's all this question is asking for, and you already have the story.