8 Ways to Manage an Underperforming Engineer

Managing an underperforming engineer is the part of the job nobody practices until it’s urgent. Avoidance makes it worse. Here’s a clear path: diagnose, clarify, support, document, decide.

If coaching is not landing, escalate with a clear performance improvement plan before the situation drifts.

1. Separate skill, will, and system

Can’t do it, won’t do it, or blocked by chaos? Wrong diagnosis wastes weeks. Ask what changed, what they’ve tried, and whether the work itself is poorly scoped.

2. Get specific with examples — not vibes

“You’re not senior enough” is useless. “In the last three sprints, two of your projects slipped without early escalation, and the auth PR needed three rewrites for test coverage” is coachable.

3. Reset expectations in writing

What “good” looks like for the next 30 days: outcomes, quality bar, communication norms. Share it after the conversation. Ambiguous standards create endless arguments later.

4. Increase support without lowering the bar

Pairing, clearer tickets, more frequent check-ins, a mentor. Support is not “doing the work for them.” The bar stays; the scaffolding increases.

5. Meet more often, shorter

Weekly isn’t enough during a performance gap. Try twice-weekly 20-minute check-ins: progress, blockers, next proof points. Silence between meetings is where stories diverge.

6. Document as you go — fairly

Date, expectation, what you observed, what you agreed. Document strengths too. Fair documentation protects the person and the company — and keeps you honest.

7. Name the fork early

“If we don’t see X by [date], we’ll need a formal performance plan / role change conversation.” Surprises destroy trust. Clarity is kindness even when the message is hard.

8. Decide — don’t endlessly hope

Improvement, PIP, role change, or exit. Dragging a known mismatch for a year taxes the whole team. Your high performers are watching whether standards are real.

Need language for the conversation itself? Use the difficult feedback and copy-paste script guides — then come back to the plan.

Frequently asked questions

How long should you coach an underperforming engineer before a PIP?

Usually 4–8 weeks of clear expectations, support, and documented check-ins — unless the gap is severe or trust is broken. Don’t surprise anyone with a PIP after months of silence.

What’s the difference between a performance issue and a misfit?

Performance is “not meeting agreed outcomes.” Misfit is “capable elsewhere, wrong seat here.” Misfits often need role change or exit — not endless coaching on skills they already have.

Should underperformance discussions stay in 1:1s only?

Start in 1:1s, but document expectations and progress in writing. If you escalate to HR/PIP, you’ll need a clear timeline — memory isn’t a process.