AlgoMaster Logo

Giving constructive feedback

Last Updated: June 4, 2026

High Priority
6 min read
AI Mock Interview

Practice this question in a realistic, spoken behavioral interview.

A constructive feedback story is one where someone did something differently because of what you said. Pick a moment where the behavior mattered to the work. Walk through why you decided to raise it, how you chose the timing and setting, what concrete suggestion you offered, and what changed in the work afterward.

What Makes the Feedback Constructive

This version of the feedback question is about helping someone develop:

  • The intent was growth: Frame the conversation around helping the person improve, not proving that you were right.
  • The feedback was behavioral: Point to the specific action, pattern, or example. Avoid personality labels.
  • The suggestion was actionable: Good feedback gives the person something concrete to try next time.
  • The setting protected trust: Private, timely, and calm beats public, delayed, or performative.
  • The "why" connected to their goals: Tie the change to quality, team speed, user impact, or the person's own growth.

Where This Answer Usually Goes Wrong

The most common slip is delivering the feedback in public. A meeting or a PR comment thread turns feedback into a callout, and the story loses the care that makes it work. A close second is the complaint dressed up as feedback: "I told them their code was a mess" names a frustration, not a behavior or a change you asked for.

Two more failures are about substance. Naming the problem without offering a path forward leaves the person stuck with nothing to try, and saving the conversation for the performance review means it arrives six months too late to help. Vague framing has the same effect. "You should improve your communication" is hard to act on, while "in standup yesterday, the API change you mentioned needed more context for the frontend folks" gives the person something specific to change.

The "Radical Candor" Sweet Spot

Good feedback sits at the intersection of "Caring Personally" and "Challenging Directly," a concept from Kim Scott's book Radical Candor. In the story, make both visible: the person should not feel attacked, and the work issue should not be softened until it disappears.

  • Caring personally: Your motivation is positive. You want to help the other person succeed.
  • Challenging directly: You are clear, specific, and don't sugarcoat the message to the point where it loses meaning.

A story that is all challenge and no care sounds aggressive. A story that is all care and no challenge sounds like ruinous empathy, where you're too cautious to give the feedback that would help.

How to Make the Feedback Land

The Action section should sound like a real conversation rather than a verdict. Describe the specific behavior, ask for their perspective so it becomes a dialogue, then suggest a concrete change and explain why it helps.

Premium Content

This content is for premium members only.