Tell me about a time when you received constructive feedback and how you responded to it
Try This Question Yourself
Practice with feedback and follow-up questions
What is this question about
Interviewers use this question to assess whether you are coachable, self-aware, and able to turn feedback into changed behavior. They are usually less interested in the feedback itself than in how honestly you received it, how deeply you understood it, and whether your response led to a credible improvement over time. At higher levels, they also look for whether your response matched your scope and responsibilities.
Key Insights
- You do not need to pick a dramatic failure. A strong answer is often a real, bounded weakness that mattered and that you addressed thoughtfully.
- Don't stop at 'my manager told me X and I did X.' Show how you examined the feedback, separated symptom from root cause, and changed your behavior in a way that stuck.
- You should make the improvement legible. Interviewers want evidence that the change lasted, not just that you intended to improve.
What interviewers probe atlevel
Top Priority
Pick a genuine piece of feedback that mattered to your work, not a fake weakness or a trivial preference.
Good examples
🟢Early in my first project, my mentor told me I waited too long before asking for help, which caused me to lose time debugging the wrong thing. That was affecting delivery on a real task.
🟢I got feedback that my pull requests were hard to review because I mixed refactoring with feature changes. It was a fair point because it slowed down teammates and caused rework.
Bad examples
🔴The main feedback I got was to speak up a little more in standup, so now I give longer updates. It wasn't a big issue, but I fixed it quickly.
🔴Someone once told me I'm too detail-oriented because I care a lot about code quality. I took that as constructive feedback and kept balancing speed and quality.
Weak answers choose feedback that is either flattering, cosmetic, or low-stakes; strong answers choose a real issue that affected execution and was suitable for an early-career engineer to own.
Valuable
Example answers atlevel
Great answers
In my first few months as an engineer, my mentor gave me feedback that I was waiting too long before asking for help when I got stuck. I thought I was being independent, but when we looked at a recent task together, it was clear I'd spent almost a full day chasing the wrong issue instead of surfacing what I had tried and where I was blocked. After that, I made a rule for myself that if I was stuck for about thirty minutes without a clear next step, I would write down what I'd tested and ask for help with that context. I also started breaking my changes into smaller pieces so it was easier to get quick feedback earlier. Over the next few tasks, I was getting unstuck faster, and my mentor specifically told me my questions had become much more focused and easier to help with. The main thing I learned was that asking for help early is not a lack of ownership if you do the prep work first.
At my last internship, I built a small internal dashboard for the operations team, and my manager told me the first version was too focused on what I thought was interesting rather than what would actually help people use it quickly. That stung a little, but it was fair, because I had added extra charts and filters before I had really checked what the team needed day to day. I responded by sitting down with two of the people who would use it, asking what questions they were trying to answer most often, and then simplifying the dashboard around those tasks. I also started sending shorter updates earlier so they could react before I spent too much time polishing the wrong thing. By the time we shared the next version, they said it was much easier to read, and my manager pointed out that I was now thinking more about the user than the feature itself. It taught me that good feedback is not just about code quality, but about whether the work is solving the right problem.
Poor answers
One piece of feedback I got was that I should speak up more in meetings. I took that seriously, so now I make sure I always say something during standup and project discussions. I think it helped because people knew I was engaged, and after that I didn't really get that feedback again. For me it was a good reminder to be more visible.
Question Timeline
See when this question was last asked and where, including any notes left by other candidates.
Mid August, 2026
Late July, 2026
Mid June, 2026
Hello Interview Premium
Your account is free and you can post anonymously if you choose.