We launched the State of Developer Burnout 2026 survey a few days ago. We're heading toward 500 responses — but even the early data is revealing. Here's what the first 28 engineers told us.
This is a growing dataset. The live results page updates as new responses come in. What you're reading here is a snapshot of where things stand now.
The average burnout score is 7.4 out of 10
We asked engineers to rate how burned out they feel right now on a scale of 1 to 10. The average across our first 28 responses is 7.4. That's not a number that suggests mild stress. It's a number that suggests most respondents are operating at or near their limit.
What's striking is the distribution. Very few people rated themselves below 5. The responses cluster in the 7–9 range — high burnout, sustained over time.
71% have been burning out for 6 months or more
This is the number that stays with you. Nearly three quarters of respondents said they've been feeling this way for at least six months. A third said over a year.
Burnout that has lasted this long doesn't resolve on its own. It requires actual change — in workload, in conditions, in how someone spends their recovery time. A vacation won't fix six months of chronic stress. Neither will a long weekend.
Always-on culture is the biggest driver
We asked respondents to name the biggest driver of their burnout. Always-on culture came out on top — cited by over 70% of respondents. Unclear priorities came second, followed by too many meetings and AI pressure to do more.
The AI pressure finding is worth noting. It didn't exist as a meaningful burnout driver two years ago. It's now in the top four. Engineers are feeling the expectation — explicit or implicit — that AI tools mean they should be able to do significantly more. For many, that expectation is landing as additional pressure rather than relief.
68% say their manager doesn't know
We asked whether respondents' managers knew they were burned out. 68% said no — either their manager didn't know, they hadn't told them, or they weren't sure whether what they were experiencing counted as burnout.
This is the visibility problem. Burnout is largely invisible to everyone except the person experiencing it — and sometimes even they don't name it clearly. By the time it becomes visible, it's usually in the form of resignation or a breakdown. Both are expensive and avoidable.
What engineers say would actually help
The answers here are more practical than you might expect. Fewer meetings came first, followed by clearer priorities and more autonomy. These aren't requests for wellness programs or meditation apps. They're requests for structural change — less noise, more clarity, more control.
That's consistent with what the research on burnout consistently shows: the most effective interventions address the conditions that cause burnout, not the symptoms. Telling someone to meditate while their on-call rotation still interrupts their weekends is not a solution.
This data is still growing
We're heading toward 500 responses. The more data we have, the more reliable these findings become — and the more we can segment by role, company size, and experience level.
If you work in tech and haven't filled in the survey yet, it takes 3 minutes and is completely anonymous. The results are published publicly — you can see exactly how your responses compare to everyone else's.
The full live results are at rechargedaily.co/state-of-burnout-2026. Take the survey at this link.