Most conversations about developer burnout are anecdotal. Someone shares their story. People nod. Nothing changes. What's been missing is data — not survey data collected once a year, but real signals tracked consistently over time.
That's what the Recharge Burnout Index is. Anonymous daily check-ins from engineers and tech workers, aggregated into a live score that updates every hour. Here's what 30 days of that data tells us.
The overall score is 57 out of 100
A score of 57 puts the industry in elevated risk territory. It's not critical — that would be above 75 — but it's well past the moderate range. In plain terms: most engineers in our dataset are carrying more stress than they can comfortably sustain.
What makes this number meaningful is that it's not a one-time snapshot. It's a rolling 30-day average built from daily check-ins. It accounts for bad weeks and good weeks. It smooths out noise. A score of 57 means that on most days, for most engineers, burnout signals are elevated.
Recovery is the weakest signal
Across all five signals — energy, stress, motivation, boundaries, and recovery — recovery scores the lowest. This matters because recovery isn't just about sleep or weekends. It's about whether the time you spend away from work actually restores you.
When recovery is consistently low, it means rest isn't working. Engineers are taking breaks but not feeling restored by them. That's one of the clearest early indicators that burnout has moved past tiredness into something more systemic.
Engineering managers score higher than individual contributors
In our data, engineering managers show higher burnout scores than software engineers. This runs counter to the common assumption that ICs carry the most stress. Managers are absorbing stress from two directions — the demands coming down from leadership and the struggles coming up from their teams.
They also tend to have less visible burnout. They're expected to be stable. They don't always have a safe place to say they're struggling. The data suggests they're burning out quietly.
Motivation tracks closely with stress — but with a lag
One pattern that emerges clearly over 30 days: stress spikes first, then motivation drops about a week later. The implication is that sustained stress depletes motivation — but not immediately. There's a lag.
This is important for managers watching their teams. By the time someone seems disengaged or demotivated, the stress that caused it has already been building for a while. The window to intervene is earlier than it looks.
What this data can't tell you
The burnout index is aggregate data. It tells you how the industry is doing on average. It can't tell you how you specifically are doing, or whether the pattern you're experiencing is typical or unusual for your role and situation.
That's what daily tracking is for. The engineers in our dataset who have the most useful data are the ones who have been checking in consistently — not just when things feel bad, but every day. Consistency is what turns individual data points into a pattern you can actually act on.
The live burnout index is updated hourly at rechargedaily.co/burnout-index. Recharge is a private daily check-in tool for engineers and tech workers.