How do you handle criticism of your work?
answer
- one-sentence posture, not a slogan
- listen, restate, ask for a specific
- sort it: act now, park, verify
- thirty-second proof you acted
- invite the next round explicitly
basics
~10 sProbes coachability as a habit rather than a mood. Give a repeatable in-the-room routine — listen, restate, ask for a specific — plus one short example of criticism you acted on and confirmed.
how to answer
5 beats- your posture in one sentenceState the stance you actually hold — for example that criticism is information about the work rather than a verdict on you. One sentence only, in your own words. Borrowed slogans are the fastest way to sound rehearsed here.
- what you do in the roomGive the concrete moves: let them finish, restate the criticism back so they can correct your version, ask for one specific instance if you were handed an impression. Naming a short pause before you reply is credible and shows self-regulation.
- how you sort it afterwardsDescribe your triage out loud: what you act on immediately, what you park with a date, what you need to watch for or verify with a second person before you believe it applies to you.
- one short example of acting on itSpend about thirty seconds on a real instance — the criticism, the change, one piece of evidence. This is what stops the answer from being a philosophy. Keep it compressed; this prompt does not want a full narrative.
- how you keep the channel openClose by saying how you go back and invite the next round, and from whom. Feedback that only ever arrives from a manager is a narrower signal than feedback you have made easy for peers to give.
your answer
5 story prompts- Write your in-the-moment routine as three verbs you genuinely use, not three you admire.
- Pick one criticism from the last year that you acted on within a month.
- Note the smallest number that shows your change actually landed for someone else.
- Keep a second, lighter example ready in case they ask for another one.
- Decide in advance who besides a manager has criticized your work recently.
draft and rehearse your own answer in a learn session
go deeper
This probes coachability as a repeatable behavior rather than one dramatic episode. The interviewer wants the mechanics: how you receive criticism in the moment, how you decide what to act on, and how you confirm the change landed. It also tests self-awareness, since candidates who claim criticism never touches them read as unexamined.
My working rule is that criticism is information about the work and not a verdict on me, and the practical version of that is simply not to reply in the first ten seconds. I let the person finish, say the criticism back in my own words so they can correct my version of it, and ask for one concrete instance if all I have been given is a general impression. Afterwards I sort it. Some of it I can act on that week. Some of it I need to watch for myself before I believe it is a pattern. Occasionally I ask a second person whether they see the same thing. The most recent one was that my defect tickets were unusable. A developer on the squad told me he had burned thirty-six minutes trying to recreate the account state a bug needed, because my ticket said he should use the test customer and nothing else. That one landed badly, because I had thought of myself as the careful one on the team. I rewrote the template I work from: exact seed rows, which environment, and the time the run started. The next handful he picked up took him around nine minutes each to reproduce. A week later I asked him whether the new tickets were any better, and what was still missing. Asking that second part is the bit I used to skip.
Strong because the routine is specific enough to picture and the example is small, recent and verifiable by another person. The closing ask keeps it from being self-graded. Cutting the ticket example would leave only a stated attitude, which is what makes most answers to this prompt interchangeable.
I try to separate two questions fast: whether the criticism is accurate, and whether the way I delivered something made it worse than it needed to be. In the room I do not argue with the first version I hear. I ask what they saw, what they expected instead, and what fixed would look like to them — that last question is the one that turns a complaint into something I can work on. Then I put a horizon on it. If I can change it this week I change it and say so out loud, so the person is not left guessing. If it is structural I give them a date and hold myself to that date. The one that mattered most came when a claims program had its scope cut. The delivery lead told me the regression report I sent every morning was noise and that he had stopped opening it. He was right — two hundred and forty rows, and it never said what was blocked. I asked what decision he was trying to make from it, which I should have asked months before, and rebuilt it around exactly that: blocked flows, owner, and the seeding time each one still cost us. Fixture setup fell from forty-seven minutes to twelve as a side effect, because rebuilding the report exposed how much of it was waiting on data. I asked him to tell me the next time something I sent him was noise. He has.
Carried by the triage-with-a-date and by asking the critic what decision the artifact was meant to support, which converts a complaint into a design brief. The final line shows the channel stayed open. Without the number, this would read as a pleasant conversation rather than a change.
Give a concrete routine you actually use in the moment — what you do before you reply — and one real example from the last year. A named routine plus one example outperforms any amount of stated open-mindedness.
Show triage. Make clear how you decide what to act on this week, what to park with a date, and what you need to observe again before you believe it. Then show how you confirm with the peer that the change landed.
Volunteered criticism dries up as you get more senior, so the interesting part is what you built to keep it coming: a question you ask in one-on-ones, a retro format, a regular skip-level. Describe the source you set up, not just how you react.
Talk about criticism aimed at your decisions and your influence, and about how you make it survivable for people several levels below you to voice it. Name the mechanism and name a time it produced something you did not want to hear.
saying these in an interview costs you the question
- Answering with a slogan such as feedback is a gift and stopping there
- Claiming criticism never bothers you, which reads as unexamined
- Describing an attitude with no routine and no example underneath it
- The only example is criticism you received and then quietly dismissed
- All feedback comes from managers, never peers or people you lead
- No mention of ever checking whether the change actually landed
- When was the last time someone criticized your work?Have a recent, dateable answer ready — within the last few months if you can. A blank or a hunt for one suggests either that you are not close enough to anyone to hear it or that you have not been noticing. Give the criticism plainly, then what you did with it, in about thirty seconds.
- How do you get feedback when nobody is volunteering any?Describe a specific ask you use, not a general willingness. Narrow questions get answers where open ones do not, so quote the question you actually ask and say who you ask it of. Naming a recurring slot where you ask it is stronger than describing an open door.
- What do you do when the feedback is vague?Say that you convert it into something observable before you act: ask for one instance, ask what they expected instead, or ask what fixed would look like to them. Add that you check with a second person when the pattern is not visible to you, and that you avoid guessing at a change nobody asked for.