Tell me about a time you had to give constructive feedback to a teammate and how you handled 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 can handle a delicate interpersonal moment without damaging trust or avoiding the issue. They want to see judgment about when feedback is necessary, empathy for the other person's perspective, and enough ownership to help the situation improve rather than just delivering criticism. At higher levels, they also look for whether your approach matched your scope and whether the feedback made the broader working relationship stronger.
Key Insights
- You do not get points just for being 'direct.' Strong answers show that you first understood what was behind the behavior and chose an approach that the other person could actually hear.
- Pick a consequential example. Feedback about something small or purely stylistic often makes you look nitpicky unless you can explain why it materially affected delivery, quality, or collaboration.
- You should describe what happened after the conversation. Interviewers are listening for whether you followed through, adapted your approach, and helped produce change rather than simply delivering the message once.
What interviewers probe atlevel
Top Priority
At junior level, it is enough to show simple follow-through: you did not just voice a complaint, you helped create a better next step.
Good examples
🟢We agreed on a simple check-in before merges that touched both our work, and I followed that for the next few weeks to make sure it stuck.
🟢After the conversation, I sent a short summary of what we'd each do differently and checked back after the next handoff to confirm it was working better.
Bad examples
🔴After I shared the feedback, I left it with them because I felt they understood what to do from there.
🔴I told them to be more careful next time, and after that I assumed the issue was resolved.
Weak answers stop at delivery; strong answers include a concrete next step and some follow-through.
Valuable
Example answers atlevel
Great answers
On a small feature project, I was paired with another engineer who was updating an API I depended on. A couple of times they merged changes without telling me, and I only found out when my part stopped working, so after it happened twice I asked if we could talk after standup. I explained one concrete example, shared how it affected my work, and asked how they were handling their changes on their side. It turned out they didn't realize I was pulling from that branch during development, so we agreed to message each other before merging anything that affected the shared interface. After that, the last part of the project went much smoother, and they actually started giving me a quick heads-up proactively.
In my part-time role on a university web team, I was working with a designer who kept sending me polished mockups only a day before the deadline, which made it hard for me to test and implement them well. I asked for a quick one-on-one and told them I really appreciated the quality of their work, but that the late handoffs were making it tough to do my part without rushing. I suggested we try a simple checkpoint halfway through the week so I could catch any technical limitations earlier, and I made sure to frame it as helping both of us avoid last-minute stress. They were receptive, and after we started doing that, we caught a few issues sooner and the final pages matched the design much better. I learned that being direct is easier when you focus on the shared goal and the specific behavior, not on blaming the person.
Poor answers
I had a teammate who kept writing things in a way I didn't prefer, so I gave them feedback pretty directly. I told them my approach was cleaner and would save everyone time if they just stuck to it. I usually like being transparent, so I put the suggestion in our team chat where everyone could see it and follow the same pattern. They didn't say much back, but I think it helped because there wasn't really more discussion after that.
Question Timeline
See when this question was last asked and where, including any notes left by other candidates.
Late July, 2026
Hello Interview Premium
Your account is free and you can post anonymously if you choose.