In an office, burnout has a face. The slumped posture at the desk, the long lunch alone, the absence at Friday drinks. Remote-first teams don’t have those signals. Five things that do show up — if you’re paying attention.
1. Slack response cadence collapses
Not "they reply slower" — they reply at very different times of day than they used to. The midweek 11 a.m. messages stop. The replies arrive at 10 p.m. or 6 a.m. The work is being done outside normal hours because the normal-hours space has become unbearable. This is the single earliest signal and the easiest to spot.
2. Calendar grows holes around 1:1s
Sudden meeting cancellations or "let’s push to next week" patterns specifically around 1:1s and team retrospectives. They’re avoiding the conversations where the burnout would surface.
3. PR review tone changes
Engineers under burnout review code differently. Comments become shorter, more transactional, less "here’s an alternative". Approvals come faster than the diff size warrants. They’ve stopped engaging with the substance and started rubber-stamping to clear the queue.
4. The "all-hands silent" signal
In an all-hands or larger team meeting, the previously-vocal contributor stops contributing. Not "asks fewer questions" — completely silent for two consecutive sessions. They’ve withdrawn from the team performance, which precedes withdrawing from the team.
5. Days-since-last-PTO crosses 90
The simplest metric, often the most predictive. If someone hasn’t taken a day off in 90+ days and they’re not new to the company, that’s a flag worth a conversation. 120+ is a red flag worth scheduling actual leave for them.
What to do when you see two of these
Schedule a deliberate 1:1 (camera on, no agenda). Open with a specific behaviour you’ve noticed — not "I’m worried you’re burning out". Listen. Don’t propose solutions in the first 20 minutes. Most of the time the act of being seen is itself a meaningful intervention.