Burnout doesn’t look like someone crying at their desk. It looks like someone who used to volunteer for the hard problem going quiet in planning. It looks like code review comments getting shorter and more clipped. It looks like someone who used to ship fast suddenly needing three days for a one-day task, not because they got slower, but because they stopped caring whether it was on time.

The early signals, in order of how easy they are to miss

1. Cynicism creeping into normal conversation. “Why bother, it’ll just get deprioritized anyway” said more than once.
2. Disengagement in meetings. Camera off, no questions, no pushback, on someone who used to have opinions.
3. Quality drops on routine work, not hard work. Someone who’s burnt out often still rises for the interesting problem and lets the boring maintenance ticket rot — a healthy engineer’s quality is more even across both.
4. Withdrawal from 1:1s. Shorter answers, less initiative, agenda items drying up.
5. Visible exhaustion talk that gets brushed off as a joke. “I’m so dead” said often enough that it stops registering as information.

By the time someone explicitly says “I’m burnt out,” they’ve usually been there for months. The value is in catching signal one or two, not signal five.

What actually helps

• Reduce load, don’t just say “take a break.” A single day off doesn’t fix a workload that snaps right back the day they return. Actually remove something from their plate, permanently, not just for a week.
• Ask what’s driving it, specifically. Burnout has different causes — too much work, unclear priorities, a bad team dynamic, feeling like the work doesn’t matter — and each needs a different fix. “More PTO” only solves one of these.
• Fix the process, not just the person. If burnout clusters around the same team or the same time of quarter, that’s a system problem, a launch cadence, an on-call rotation, a chronically understaffed team, not an individual willpower problem, and it’ll keep producing burnt-out people until you fix the system.

What makes it worse

• Praising the person who works through burnout as dedicated. This tells everyone watching that burning out is the path to recognition, and you’ll get more of it.
• An on-call rotation with no real recovery time built in after a bad week. A rough on-call week followed immediately by a normal-intensity week isn’t recovery, it’s just less bad.
• Treating a burnout conversation as a performance conversation. If someone hears “you seem checked out” as a warning about their job security, they’ll mask the signal harder next time instead of being honest with you.

The manager’s actual job here

Notice before they say it out loud, and when you do notice, address the workload and the system, not just the person’s attitude. A team where burnout gets caught at signal two instead of signal five is a team where people trust that raising it won’t cost them anything, and that trust is the only thing that makes early signals visible at all.

---