Give me an example of a tough or critical piece of feedback you received.
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 feedback itself than in how honestly you describe it, how deeply you understood the root issue, and whether your behavior actually changed afterward.
Premium video
Sign in & purchase Premium to watch the full video.
Key Insights
- You do not need to pick a catastrophic failure. A strong answer is usually a real, meaningful weakness that had consequences, not a disguised strength or a trivial nit.
- You should show more than compliance. Strong answers explain how you interpreted the feedback, validated it, changed your approach, and checked whether the change actually worked.
- If the feedback was hard to hear, say so without becoming defensive. Honest discomfort followed by mature action is often a stronger signal than pretending the conversation was easy.
What interviewers probe atlevel
Top Priority
Do not stop at 'they told me X so I did X'; show that you asked why the feedback mattered and what behavior caused it.
Good examples
🟢I asked for examples and learned the real issue was not silence in general, but that I tended to disappear for hours when blocked and then surface the problem too late.
🟢After hearing the feedback, I spoke with my mentor and another teammate and saw that I was treating uncertainty as something to hide rather than something to communicate.
Bad examples
🔴My manager said I needed better communication, so I just started sending more updates.
🔴I was told to ask for help earlier, so after that I tried to message people more often.
Weak answers apply a surface fix; strong answers uncover the specific behavior or mindset underneath the feedback.
Valuable
Example answers atlevel
Great answers
One tough piece of feedback I got during my first few months was that I waited too long to ask for help when I was stuck. My mentor pointed out that I would spend hours trying to debug something on my own, and by the time I raised it, the ticket was already at risk. That was hard to hear because I thought being independent was the right thing to do, but I realized I was optimizing for looking self-sufficient instead of making steady progress. After that, I started writing down what I had tried and asking for help once I had exhausted two reasonable approaches or been blocked for more than an hour. I also began posting short updates when I hit uncertainty instead of waiting until the end of the day. A month later, my mentor told me my updates made it much easier to unblock me early, and my work stopped slipping for that reason.
Early in my first job a lead pulled me aside and said my pull requests were too large and detailed — they took too long to review and hid important changes, which caused integration delays. That stung because I pride myself on delivering complete, well-tested work, but I realized I was trading thoroughness for slow feedback cycles. I started breaking features into smaller, runnable increments, adding concise PR descriptions that called out the risk areas, and including focused tests so reviewers could trust the change quickly. Within a few sprints reviews were much faster, I caught integration issues earlier, and the product team appreciated that I was delivering usable progress more frequently.
Poor answers
The toughest feedback I got was that I care too much about doing things well and sometimes spend extra time making sure everything is correct. I understood the comment, but I think that is mostly a good problem to have, especially as a newer engineer. Since then I have tried to move a little faster when needed, but I still think quality should come first. Overall it did not really change much because my work was already strong.
Question Timeline
See when this question was last asked and where, including any notes left by other candidates.
Late July, 2026
Late July, 2026
Mid May, 2026
Hello Interview Premium
Your account is free and you can post anonymously if you choose.