What is the last constructive criticism you received?
Asked at:
Meta
Macquarie Group
Amazon
Anthropic
Try This Question Yourself
Practice with feedback and follow-up questions
What is this question about
Interviewers use this question to assess self-awareness, coachability, and whether you can turn uncomfortable feedback into better performance. They are usually less interested in the criticism itself than in how honestly you describe it, how well you understood the underlying issue, and whether your behavior actually changed afterward.
“Tell me about a piece of feedback that changed how you work.”
“What's a tough piece of feedback you've gotten recently, and what did you do with it?”
“Describe the most useful constructive criticism you've received in the last year.”
“Have you ever been told something difficult but fair about your work? What was it?”
“What's an example of feedback you received that led you to change your behavior?”
Key Insights
- You do not need to pick a dramatic failure. A strong answer is often a real, believable piece of feedback that mattered and led to durable behavior change.
- You should explain how you validated and interpreted the feedback, not just that someone told you something. Strong candidates show they looked for the pattern behind the comment and acted on that pattern.
- You will get more credit for demonstrating an ongoing improvement loop than for presenting yourself as instantly fixed. Show what changed, how you practiced it, and what evidence told you it was working.
What interviewers probe atlevel
Top Priority
Name concrete habits you changed, not just a general intention to improve.
Good examples
🟢I started posting a short update by midday if I was blocked for more than thirty minutes, and I began bringing one proposed next step instead of just the problem.
🟢I set a rule for myself that if I had tried two approaches and was still unsure, I would ask for help rather than spend the rest of the day spinning.
Bad examples
🔴After that, I just made an effort to communicate better and be more careful.
🔴I kept the feedback in mind and tried to avoid doing it again.
Weak answers describe intentions; strong answers describe repeatable new behaviors.
Show that you tried to understand the pattern behind the feedback instead of treating it like a one-off instruction.
Good examples
🟢After hearing it, I asked my mentor for two recent examples so I could see when I was missing the signal that I was stuck.
🟢I started tracking when I sent updates and compared that with when blockers were discovered, which helped me see that I was often waiting until the end of the day to mention risk.
Bad examples
🔴My lead mentioned it in our check-in, so after that I just tried to be better about it.
🔴Once I got the comment, I took it as a note to remember next time and moved on.
Weak answers are passive and generic; strong answers show curiosity, pattern-finding, and effort to diagnose the real issue.
Valuable
Even at junior level, close the loop by showing how you knew you were improving.
Good examples
🟢My lead later called out that my updates were much easier to act on because they included the blocker and the next step.
🟢A few sprints later, I was getting help earlier and my tasks stopped slipping at the very end, which was the main pattern we wanted to fix.
Bad examples
🔴I think it got better because no one brought it up again.
🔴After that project, it didn't really come up much, so I assume I fixed it.
Weak answers rely on silence as proof; strong answers provide concrete signs that the behavior and outcomes changed.
At staff level, your story should have consequences for multiple engineers or teams because that is the box you're expected to operate in.
Good examples
🟢I was told that I was resolving ambiguity through informal influence in a way that worked for me but did not scale for teams that needed durable shared context.
🟢The feedback was that my involvement improved decision quality but also made some teams too dependent on me to move complex work forward.
Bad examples
🔴The criticism was that I should organize my personal notes better so I could find things faster in meetings.
🔴A teammate told me my comments on one design doc were too short, so I started writing more detail.
Weak stories sound like an individual contributor at a lower level; strong stories fit the influence footprint expected of staff.
Example answers atlevel
Great answers
The last constructive criticism I got was from my team lead during a project where I was building a small internal tool. He told me I tended to stay quiet when I was blocked, so from his perspective my work looked on track until a task suddenly slipped. I asked him for examples, and we realized I was often spending too long trying to solve things on my own because I didn't want to interrupt people. After that, I started sending a short update if I was blocked for more than about thirty minutes, and I always included what I had already tried. Over the next few weeks, I got help earlier, and in our next check-in he mentioned that my progress was much easier to track and there were fewer last-minute surprises. It also taught me that asking for help early is part of being reliable, not a sign that I'm not independent.
The most recent constructive feedback I got was from a senior reviewer who pointed out that my pull requests were hard to review because they mixed refactors, bug fixes, and formatting changes together and had minimal descriptions. I asked him to show a couple of examples and realized I was committing whatever I touched to the same branch to move fast, which ended up creating noise for reviewers. Since then I’ve started breaking work into focused branches, writing a short summary of the change, why it’s needed, and steps to test in the PR description, and I avoid unrelated formatting edits in the same change. That made reviews noticeably quicker and reduced back-and-forth, and my teammates told me it’s easier to trace where a behavioral change came from — a small habit change that improved team momentum and long-term maintainability.
Poor answers
The last criticism I received was that I ask a lot of questions at the beginning of a task. I actually took that as a sign that I'm thorough, but I did try to cut down a bit so I could move faster. Usually I prefer to figure things out myself anyway, so it wasn't a big adjustment. Since then I've just been more careful about when I ask things.
Question Timeline
See when this question was last asked and where, including any notes left by other candidates.
Early March, 2026
Meta
Senior
Late July, 2025
Meta
Manager
Late July, 2025
Meta
Manager
Hello Interview Premium
Your account is free and you can post anonymously if you choose.