The IT Industry Doesn't Have a Burnout Problem. It Has a Culture Problem.
Every few months, another article appears about burnout in tech. The symptoms are catalogued with clinical precision: exhaustion, cynicism, declining performance. Then comes the advice which is borderline insulting: meditate more, take walks, set boundaries. And then everyone goes back to their Helpdesk queues.
We keep treating burnout like a personal failing dressed up as a wellness issue. It isn’t. It’s the entirely predictable output of an industry that romanticises overwork and punishes people for having limits.
“Passionate” is a word that does a lot of heavy lifting
Job postings in IT love the word passionate. They want someone passionate about technology, passionate about the mission, passionate about shipping. What they mean is: we’d like someone who won’t clock-watch. Who’ll answer messages at 10pm because they care.
Passion is a great substitute for fair compensation and reasonable hours,at least for a while. The industry discovered this early and then built a culture around it. It has been dining out on this ever since.
When you frame work as a vocation rather than a job, you make it socially awkward to protect your time. Asking for a real lunch break starts to feel selfish. Taking holiday becomes an act of mild courage.
The on-call treadmill
Here’s something that would seem bizarre in almost any other industry: a large chunk of IT workers are expected to be reachable, and responsive, outside of contracted hours. And this is often with no meaningful compensation, and almost always without a formal end date.
On-call rotations were designed for genuine emergencies. In many organisations they’ve quietly expanded to cover anything the business finds inconvenient to wait for. The systems are always critical and the deadlines are always immovable. Every escalation is always considered urgent.
Living in a state of low-grade alertness doesn’t just affect work. It colonises sleep, weekends, and the mental space where rest is supposed to happen. This isn’t a bug in how some companies operate. For many, it’s a feature.
The “Move fast” body count
The mythology of Silicon Valley sold speed as a virtue with no downside: Move fast. Ship. Iterate. The companies that hesitate are the companies that lose.
What this philosophy produces in practice is teams running permanently close to capacity, where there’s no slack to absorb the unexpected. A difficult quarter, a major incident, a member of staff who gets ill. When something goes wrong (and it always does), it doesn’t slow the team down. It buries them.
Sustainable pacing is treated as a competitive weakness. Rest is something you earn, not something built into the system. The result is predictable, and the industry has the attrition numbers to prove it.
What actually needs to change
This isn’t an argument for doing less or caring less. It’s an argument for honesty about what the culture asks of people and whether that asking is fair.
The companies with the best long-term engineering cultures tend to have something in common: they treat recovery time as part of the production process, not as dead time. They plan with realistic capacity. They staff on-call rotations properly. They notice when people are running on empty before those people hand in their notice.
Burnout is not an individual failure of self-care. It’s a structural outcome. Fixing it requires structural thinking — not a meditation app subscription and a suggestion to take more breaks.
Until the industry is willing to have that conversation honestly, the think pieces will keep coming. And so will the burnout.