8 Tips for Giving Difficult Feedback to Engineers

Difficult feedback is how good engineers get better — and how mediocre patterns get stopped before they become PIPs. Softening into mush helps no one. Here’s how to be direct without being cruel.

Steal the exact wording from our plug-and-play feedback scripts so you are not improvising under pressure.

1. Don’t wait for “the right time”

There isn’t one. Schedule a 30-minute 1:1 within a few days of the incident. Context fades; resentment doesn’t.

2. Private by default

Corrective feedback in Slack threads or group meetings creates shame, not change. Praise can be public. Course-correction is one-to-one.

3. Lead with facts, not labels

“Careless” and “not a team player” are judgments. “The PR shipped without tests we agreed on, and it caused a Sev-2” is feedback they can act on.

4. Use SBI, then make one clear ask

Situation → Behavior → Impact → Request. One request per conversation. “Improve your attitude” is not a request.

5. Separate the person from the pattern

You’re coaching a behavior in a context, not rewriting their identity. Engineers hear “you’re bad” even when you mean “this PR.” Be precise.

6. Invite their view — then don’t fold on the standard

“How did you see it?” surfaces constraints you missed. Listen. Then restate the bar. Empathy isn’t the same as lowering expectations.

7. Agree on a check-in date

Hard feedback without follow-up is theater. Put a date on the calendar. Review evidence together. Adjust support, not the standard.

8. Document as you go

Shared notes: what was said, what’s expected, by when. Protects them from surprise reviews and protects you if performance management escalates.

Need the words? Use the 10 copy-paste feedback scripts and adapt them to your situation.