Describe a situation where you received criticism
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 received it, how deeply you understood it, and whether your behavior actually changed afterward. At higher levels, they also look for whether you build feedback loops for yourself and model healthy response to criticism for others.
Key Insights
- You do not need a dramatic failure story. A strong answer is often a real, meaningful piece of criticism that exposed a pattern you then worked to change.
- You should resist the urge to explain away the feedback. Even if the criticism was imperfectly delivered, interviewers want to hear what truth you extracted from it and what you did next.
- You should close the loop. Many candidates describe receiving feedback and making a one-time adjustment, but strong answers show sustained behavior change and some evidence that the criticism was actually addressed.
What interviewers probe atlevel
Top Priority
Show that you did more than comply with a comment; understand why the feedback happened so you could change the pattern.
Good examples
🟢When I was told my task estimates were often off, I looked at my last few assignments and noticed I wasn't accounting for setup and testing time.
🟢After hearing that my updates were confusing, I asked two teammates for examples and realized I was assuming people had the same context I did.
Bad examples
🔴After my mentor said my pull requests were hard to review, I just started making them smaller when I remembered to.
🔴My manager said to speak up more in meetings, so I made sure to talk at least once in every meeting.
Weak answers react to the surface instruction; strong answers investigate the underlying habit or assumption that produced the criticism.
Valuable
Example answers atlevel
Great answers
Early in my first internship, my mentor told me that my code reviews were hard to follow because my changes mixed bug fixes, refactoring, and formatting all in one submission. I initially thought the work itself was correct, but when he walked through one example, I saw that I was making it harder for others to review and support me. After that, I started breaking my work into smaller parts and adding a short summary of what changed and what I wanted feedback on. I also asked him to tell me if my next few reviews were still too hard to read. Within a couple of weeks he said they were much easier to review, and I noticed comments became more about the actual solution instead of asking me to reorganize everything.
At my second job at a small SaaS startup I was called out by our customer success lead for coming across as dismissive when customers reported bugs — I'd often reply "can't reproduce" without much follow-up. I was defensive at first, but I asked for examples and realized I wasn't putting in the effort to reproduce issues or explain what I had tried, which left customers and teammates frustrated. I started following a simple reproduction checklist, recording a quick screen capture when I couldn't reproduce locally, and including exact environment details and next steps in my replies, plus a short note acknowledging the user's frustration. I also invited the customer success rep to sit in on a few debugging sessions so we could align on expectations. Within a month we had fewer escalations and the rep told me customers appreciated the clearer updates and that trust between teams improved.
Poor answers
One time I got criticism that I asked too many questions when I started on a project. I understood where that was coming from, but I think it was mainly because the system was new and there wasn't much documentation. After that I tried to be more independent and not bother people as much. Things went pretty smoothly after that, and I was able to finish my tasks.
Question Timeline
See when this question was last asked and where, including any notes left by other candidates.
Early May, 2026
Mid February, 2026
Mid December, 2025
Hello Interview Premium
Your account is free and you can post anonymously if you choose.