Burnout Mental Health

Cross-cutting · CC08

CC08: Burnout & Mental Health in IT Roles

A deep-dive on occupational burnout and mental health across IT specializations, grounded in 2024-2026 evidence.

Why This Matters: IT's Burnout Crisis

Burnout is not a personal failing. It is an occupational phenomenon officially recognized in the WHO International Classification of Diseases (ICD-11, code QD85), defined as "a syndrome conceptualized as resulting from chronic workplace stress that has not been successfully managed" and characterized by three dimensions:

  1. Energy depletion or exhaustion
  2. Increased mental distance from one's job, or feelings of negativism or cynicism
  3. Reduced professional efficacy

The tech industry faces a burnout epidemic:

  • 2025 Stack Overflow Developer Survey: 80% of professional programmers report job dissatisfaction. One in three actively hate their job; nearly half report "survival mode." Only 20% claim to be somewhat happy—though 2025 saw a slight improvement to 24% happiness.

  • LeadDev 2025 Report: 22% of engineering leaders and developers report critical burnout levels. 46% of tech professionals overall report burnout (up from 31% in 2024). Of those "very burned out," 70% are actively job-searching.

  • 2025-2026 Layoff Aftermath: 2026 has already seen 249 layoffs affecting 95,878 workers (864 people/day). Survivors report "Survivor Syndrome"—expanded workloads, job insecurity, and moral injury. 49% of layoff survivors report declined morale; recovery takes 4+ months.

The stakes are personal and operational: "Rest culture" collides with performance demands. This document is honest about both.

Per-Role Burnout Risk Profiles

Burnout risk varies by role, schedule, organizational maturity, and whether you control your own boundaries.

🟢 LOW BURNOUT RISK

Tech Writer (corporate, established company)

  • Stable deliverables (documentation, blogs, videos)
  • Clear definition of done
  • Asynchronous-friendly work
  • Burnout risk: 1–2 years of overload or understaffing can still trigger it, but the role itself is not inherently burnout-prone
  • Watch for: Being sole tech writer; always "catching up to engineering" changes

Data Analyst (corporate, analytics-focused)

  • Defined projects, metrics, clear success criteria
  • Typical 40-45 hour weeks
  • Minimal on-call or crisis mode
  • Risk increases if: dashboards break frequently, stakeholders demand real-time changes, or expectations creep into executive-level pressure

Solutions Architect (steady SaaS company)

  • Design-phase work; implementation handled by others
  • Recurring revenue = stable business
  • Can push back on unrealistic timelines
  • Risk: Increases in chaotic pre-sales or high-touch customer situations

Senior Sysadmin (mature enterprise)

  • Seasoned team, runbooks in place
  • Automation handles routine work
  • Experience = confidence
  • Risk: Understaffing, legacy systems nobody understands, or constant cost-cutting can flip this to MEDIUM/HIGH quickly

Salesforce Administrator (stable deployment)

  • Defined admin scope, clear process workflows
  • Low 24/7 risk
  • Burnout risk: Only if organization treats the role as 100% support (no admin work), or if Salesforce customization work expands beyond admin scope into dev territory

🟡 MEDIUM BURNOUT RISK

Software Engineer (varies by company)

  • Google/Meta/stable startup: 40-50 hour weeks, clear scope, career growth = MEDIUM
  • Chaotic startup: undefined scope, always-on culture, pivots = HIGH/VERY HIGH
  • Big Corp: bureaucracy, meetings, slow progress = MEDIUM
  • Risk drivers: Unclear priorities, deadline pressure, testing quality, code review culture

Network Engineer (enterprise)

  • Reactive troubleshooting when networks fail (high urgency, low frequency)
  • Risk from: BGP disasters, DDoS events, upgrade windows
  • 24/7 on-call expectations in some orgs
  • Medium risk in stable orgs; escalates to HIGH with understaffing

DevOps Engineer (without on-call)

  • Tooling, CI/CD pipelines, infrastructure-as-code
  • Medium risk if: CI/CD pipelines break frequently, deployments are high-stress, or on-call rotations exist
  • Low risk if: Systems are stable, good runbooks, team shares load fairly

Cloud Engineer (platform / infrastructure focus)

  • Migration projects = finite, bounded work
  • Operations & support = ongoing, open-ended
  • Risk escalates with customer hostility, unclear scope, or being the only cloud expert

🟠 HIGH BURNOUT RISK

Security Operations Center (SOC) Analyst, Level 1

  • 70% of SOC L1 analysts with ≤5 years' experience leave within 3 years (SANS 2025 Detection & Response Survey)
  • Shift work (24/7 SOC rotations): sleep disruption, circadian misalignment, isolation from day-shift team
  • Alert fatigue: Organisations face 960–3,000+ alerts daily; 73% of SOCs list false positives as their #1 challenge
  • 71% of SOC analysts experience burnout; 64% consider leaving within a year
  • Low autonomy, high surveillance, repetitive pattern-matching
  • Customer-facing blame when incidents occur

Helpdesk / Tier 1 Support

  • Average tenure: 2.5 years before departure (IT Help Desk Burnout research)
  • 40.6% annual turnover rate—double the all-job average
  • Chronic stress visible in 3–6 months; significant burnout by 9–12 months
  • 74% of contact center agents at risk of burnout
  • Drivers: high call volume, repetitive scripts, customer hostility, metrics surveillance (AHT, CSat), low pay ($39,600 entry), high replacement cost ($29,700 per person)
  • "Survivor" phenomenon: team shrinks, remaining agents handle 2x load

Mid-Level Developer at Startup

  • Fast growth = undefined scope, context-switching, broken promises
  • "Move fast and break things" culture can mean broken-on-production deploys
  • Limited QA, testing responsibility falls on dev
  • Equity-based comp means staying through burnout feels "necessary"
  • No real mentorship; expected to figure it out

🔴 VERY HIGH BURNOUT RISK

Site Reliability Engineer (SRE) with On-Call Rotations

  • On-call is a unique stressor that doesn't respect working hours, weekends, or sleep cycles
  • Pager can go off at 3 AM; incident response takes 30–40% of bandwidth during on-call shifts
  • Google's SRE book recommends max 2–3 incidents per shift; reality often far exceeds this
  • 65% of engineers report burnout; on-call stress is a major driver (State of Engineering Management 2024)
  • Post-incident trauma common: "Why didn't alerting catch this?" "I was the one who broke it." PTSD-like symptoms after major outages
  • Exhausted engineers make slower decisions, miss subtle signals, increase risk of cascading failures
  • Solution requires systems design (alert quality, runbook quality, rotation fairness), not personal heroism

Chief Information Security Officer (CISO)

  • Average tenure: 18–26 months (Heidrick & Struggles 2024 CISO Survey)
  • 47% of CISOs lack adequate internal successor (succession-planning gap)
  • 71% identified stress as most significant personal risk (up from 59% in 2022)
  • 54% identified burnout as most significant personal risk (up from 48% in 2022)
  • Board expectations vs. budget reality; always "too big a job for one person"
  • Compliance deadlines immovable; breach risk existential
  • Hyper-visibility; scapegoating when incidents occur
  • Expanding scope: cloud, AI/ML risks, supply-chain security, privacy, ESG

Penetration Tester / Red Team

  • 51% of cybersecurity professionals have sleep trouble due to work stress; 47% work 41–90 hours/week
  • High-intensity projects: "get in, find everything, report everything"
  • Adversarial engagement stress: repeatedly testing assumptions of defenders who may become hostile
  • Unique mental health harm from role intensity and interpersonal friction
  • Many red-teamers are contractors; no employer mental health benefits
  • Finding vulnerability you "should have found earlier" = guilt, rumination

Incident Response (IR) Lead During Major Incidents

  • Crisis mode: communication breakdowns, executive pressure, media scrutiny
  • Post-incident: blame assignment, root-cause analysis (RCA) culture can feel punitive rather than learning-focused
  • Sleep deprivation during response; adrenaline crash after resolution
  • "Whoever is paged owns it" mentality
  • Risk of moral injury if blamed unfairly or if systemic failures aren't addressed

Founder / CTO at Startup

  • No boundaries: 60–80 hour weeks normalized
  • Financial stress (runway, funding); personal identity fused with company success
  • Hiring/firing stress; responsible for every person's career
  • Technical decisions haunting you years later
  • Isolation at top; no one to talk to about real problems
  • Burnout often goes unnoticed until collapse

Specific Burnout Factors by Role

On-Call Rotations (SRE, Ops, IR)

The Problem:

  • Pager anxiety: hypervigilance even off-hours
  • Sleep fragmentation: woken at 2 AM, can't fall back asleep
  • "Incident debt": unresolved incidents create rumination
  • Unfair rotation → resentment

Evidence:

What Helps:

  • Rotation fairness: no one on-call >1 week/month
  • Runbook quality: incident triage in <5 min, clear escalation
  • Async handoff: context transfer between shifts
  • Blameless postmortems: focus on process, not blame
  • Stipend for incident time: "you own the incident, you own the recovery cost"

Alert Fatigue (SOC L1, NOC, DevOps)

The Problem:

  • 960–3,000+ alerts daily; 99% false positives or trivial
  • Analyst develops "alert blindness": ignores real signals
  • Guilt: "I'm the safety net; how did I miss this one?"
  • Metrics pressure: "close alerts faster" encourages dismissal

Evidence:

What Helps:

  • Alert quality over quantity: tune rules to reduce false positives
  • Tiered response: level-1 auto-response, level-2 escalation
  • Human review: reviewers rotate through SOC to understand analyst experience
  • Runbooks per alert type: analyst isn't guessing next step

Crisis Mode (CISO, IR Lead)

The Problem:

  • Breach response: 72+ hours of no sleep possible
  • Existential stakes: "Did I cause this? Should I have prevented it?"
  • Stakeholder pressure: board, legal, PR all demanding answers
  • Post-incident: blame search rather than learning

Evidence:

  • SANS Incident Handling 2024 Report: Mean time to contain (MTTC) pressure drives overwork and blame culture
  • CISOs: 54% identify burnout as most personal risk (up from 48% in 2022)

What Helps:

  • Pre-incident tabletop exercises: reduces response chaos
  • Clear incident commander authority: one voice, not five
  • Blameless postmortems: psychological safety = better learning
  • Post-incident recovery: mandatory time off after major incidents
  • Rotation: no one on IR team 24/7/365

Adversarial Mindset (Pentester, Red Team)

The Problem:

  • You are paid to find flaws and blame defenders
  • Role creates tension: "We're the good guys, but we're attacking"
  • Interpersonal friction: defenders may become defensive, hostile
  • Emotional labor: "I have to empathize with their defensiveness while maintaining professional distance"
  • Red teamers often lack employer-sponsored mental health due to contractor status

Evidence:

What Helps:

  • Rotate off red team: mix in defensive/arch work
  • Psychological safety: orgs that don't shoot messengers
  • Peer communities: industry meetups, OSMI groups
  • Sabbaticals: every 3–5 years, step away from adversarial work

Bus Factor (Mainframe Sysadmin, Sole Specialist)

The Problem:

  • You are the only person who understands the legacy system
  • Vacation = dread: what will break while I'm gone?
  • Job security paradox: indispensable = can't leave, can't promote, can't delegate
  • Knowledge hoarding (intentional or not) = resentment from team

Evidence:

What Helps:

  • Knowledge transfer: mandatory documentation, pair programming
  • Rotation: ensure 2+ people understand each critical system
  • Mentorship: bring in junior, cross-train
  • Career path: sole specialists often hit ceiling; create arch or lead role

Productivity Surveillance (Helpdesk, Call Center, BPO)

The Problem:

  • Keystroke loggers, call recordings, AHT (Average Handling Time) metrics
  • Bathroom breaks monitored; "not productive" = disciplined
  • Autonomy eroded: script-bound, no discretion
  • Dehumanizing: reduced to metrics, not people

Evidence:

  • Helpdesk Burnout Research: Chronic stress visible in 3–6 months; 40.6% annual turnover
  • Productivity surveillance correlates with depression, anxiety, turnover

What Helps:

  • Trust-based metrics: outcome (tickets closed, satisfaction), not surveillance
  • Autonomy: agents can deviate from script if justified
  • Career path: helpdesk as entry point, not endpoint
  • Team culture: "we're in this together," not "you're being watched"

Shift Work (24/7 SOC, Global On-Call)

The Problem:

  • Circadian rhythm disruption
  • Sleep quality degrades; chronic fatigue
  • Social isolation: night shift while friends sleep
  • Family strain: holidays and weekends not yours

Evidence:

  • Matthew Walker, "Why We Sleep": Sleep deprivation = cognitive impairment equivalent to 0.08% BAC (legal drunk threshold). 6 hours/night for 10 days = same impairment as 24-hour no-sleep
  • Night-shift workers have 40% higher depression risk, higher cardiovascular disease, higher cancer risk

What Helps:

  • Rotation fairness: no one on nights >2 weeks/quarter
  • Light therapy: bright light in morning, dark sunglasses evening
  • Sleep tracking: monitor and optimize
  • Off-shift recovery: genuinely off, no messages
  • Compressed schedule: 3×12 hour shifts = fewer transitions than 5×8

Customer Hostility (Helpdesk, Support, Solutions Architect)

The Problem:

  • Absorb customer's frustration; not your fault, but you're the target
  • "It must be your system" (often it's user error, but you can't say that)
  • Emotional labor: smile and apologize even when unjustly blamed
  • Escalation: only way out is to pass the buck

Evidence:

  • Giva on Helpdesk Burnout: Chronic stress + customer blame = high turnover
  • Contact center burnout driven partly by "emotional dissonance": you feel angry/frustrated but must appear helpful/calm

What Helps:

  • Training in de-escalation and empathy (genuine, not fake)
  • Caller volume limits: quality over quantity
  • Call listening: managers listen to calls and coach (not to blame, to support)
  • "Permission to hang up": if customer becomes abusive, end call professionally
  • Peer support: "you handled that well" after difficult call

Outage Trauma (SRE, Ops)

The Problem:

  • Major outage (customers down, revenue lost): "I failed"
  • Blame cycle: RCA becomes witch-hunt
  • PTSD-like symptoms: hypervigilance, intrusive thoughts ("what if we break again?")
  • Team fracture: blame spreads, trust erodes

Evidence:

  • Rootly On-Call Burnout: Post-incident trauma common; exhausted engineers make slower decisions, increasing risk of cascading failures
  • Blameless postmortems reduce PTSD; punishment-focused cultures create moral injury

What Helps:

  • Blameless postmortem: "What can we learn?" not "Who messed up?"
  • Runbook updates: concrete actions to prevent recurrence
  • Post-incident recovery: mandatory time off (24–48 hours minimum)
  • Team debrief: psychological safety to discuss fears, not just technical fixes
  • Leadership: "outages are learning opportunities, not career-ending"

Imposter Syndrome (Junior at FAANG, New to Senior Role)

The Problem:

  • Surrounded by "smart" people; you feel like an impostor
  • Visibility: code reviews by senior engineers, status meetings with directors
  • Perfectionism: fear of shipping broken code
  • Compare-and-despair: everyone else seems to "get it" faster

Evidence:

  • OSMI Survey on Mental Health in Tech: 77% of tech workers with mental health issues report impact on daily work
  • Imposter syndrome and anxiety common among junior and senior ICs in large tech

What Helps:

  • Mentorship: explicit, regular 1-on-1s
  • Code review culture: feedback as learning, not criticism
  • Vulnerability: senior engineers openly discuss struggles
  • Wins board: celebrate shipped features, not just avoided bugs
  • Therapy: imposter syndrome often rooted in perfectionism, anxiety, worth-tying to output

The 2024-2026 Layoff Aftermath

The tech industry witnessed massive workforce reductions:

  • 2024: ~386,000 jobs cut across IT, healthcare, banking, insurance
  • 2025: 783 layoffs affecting 245,953 people (674 people/day)
  • 2026 (to April): 249 layoffs affecting 95,878 people (864 people/day)

Survivor Syndrome:

  • 65% of developers reported expanded responsibilities after layoffs; only 3% saw decreased scope
  • 40% now manage more direct reports (thrust into leadership unprepared)
  • 46% report critical burnout (up from 31% in 2024)
  • 49% of layoff survivors report declined morale; recovery takes 4–12 months
  • Job insecurity: 54% of workers report stress from job insecurity significantly impacts mental health
  • "Why am I still here?" guilt; moral injury from seeing colleagues terminated

What Companies Can Do:

  • Transparent communication: why? timeline? next steps?
  • No "quiet firing" of remaining staff through overwork
  • EAP expansion: acknowledge mental health impact
  • Career development: help survivors see a future
  • Buddy system: peer support groups, psychological safety

Tech Industry Mental Health Crisis

WFH Isolation

Remote work benefits (autonomy, flexibility) are offset by:

  • Boundary blur: work laptop always there; always "on"
  • Social isolation: no incidental interactions, harder to form bonds
  • Surveillance creep: keystroke loggers, active monitoring
  • 77% of remote workers say: "Key to success is setting boundaries" (GitLab All-Remote Handbook)
  • Yet: constant use of mobile tech to stay connected drives emotional exhaustion

"Always-On" Slack Culture

  • Slack = interruption-driven work: context switching = cognitive load
  • Async communication broken: message comes in 11 PM, expected response by 9 AM
  • Fear of missing out: if you don't respond quickly, you're not engaged
  • Burnout symptom: "I can't turn Slack off; my job disappears if I'm unavailable"

What Helps:

  • No expectations outside hours: Slack do-not-disturb enforced 5 PM–9 AM
  • Async-first: important decisions documented, not announced in Slack
  • Response-time SLA: "best effort" not "immediate"

"Hustle Culture" Critique

The 2010s valorized overwork: "sleep when you're dead," "passion = sacrifice," "real founders never sleep." This has aged poorly.

Recent pushback:

Honest tension:

  • Some people do love intense work; it's not toxic for everyone
  • Context matters: startup momentum vs. established company
  • Power imbalance: junior people can't opt out; seniors set the tone

Mental Health Resources & Support

Crisis & Immediate Support

988 Suicide & Crisis Lifeline (US)

  • 988lifeline.org
  • Call, text, or chat 24/7, confidential
  • Trained counselors; interpretation in 240+ languages
  • Over 200 local contact centers

South African Depression and Anxiety Group (SADAG)

  • sadag.org
  • National helpline: 011 234 4837
  • SMS and WhatsApp support available
  • 7 days/week, 365 days/year; up to 400 calls/day
  • Free, confidential counseling

Crisis Text Line

  • Text HOME to 741741 (US)
  • Anonymous, 24/7 support

Mental Health Organizations & Communities

Mental Health America (MHA)

  • mhanational.org
  • Screening tools, resources, referrals
  • Workplace mental health initiatives

National Alliance on Mental Illness (NAMI)

  • nami.org
  • Support groups, education, advocacy
  • Peer support and family resources

Open Sourcing Mental Illness (OSMI)

  • osmihelp.org
  • 501(c)(3) dedicated to mental health in tech
  • Annual surveys, corporate resources, peer support
  • Founded 2013 by Ed Finkler (web developer, open source advocate)
  • Key stat: 77% of tech workers with mental health issues report impact on daily work

DevsAtRest

  • Peer community for developers, rest-focused
  • Slack/Discord communities for sharing experiences

Not-Big-Tech.com

  • Community exploring alternatives to FAANG burnout culture
  • Job board, discussion forums

r/cscareerquestions, r/ExperiencedDevs (Reddit)

  • Large communities; read carefully, take armchair advice with grain of salt
  • Useful for: "Is this normal?" questions, peer perspective

Therapy & Counseling Options

Employer EAP (Employee Assistance Program)

  • Most employers offer free, confidential counseling (3–5 sessions)
  • Often includes referrals, financial planning, legal consultation
  • Use it: it's paid, it's private, it doesn't go in your HR file

BetterHelp, Talkspace

  • Online therapy; start in days, not months
  • Insurance accepted or out-of-pocket
  • Licenses vary by state; research your provider

NAMI, MHA Local Chapters

  • Low-cost/free counseling referrals

Therapist Directory

  • Psychology Today, TherapyDen, Zencare
  • Filter by insurance, specialty (burnout, anxiety, imposter syndrome, etc.)

Books on Burnout & Stress Management

"Burnout: The Secret to Unlocking the Stress Cycle"

  • Authors: Emily Nagoski, PhD and Amelia Nagoski, DMA
  • Key insight: "Burnout isn't about doing too much—it's about not completing the stress cycle"
  • Explains why women experience burnout differently; universally applicable frameworks
  • Published 2019; continues relevant in 2024+

"The Burnout Epidemic: The Rise of Chronic Stress and How We Can Fix It"

  • Author: Jennifer Moss
  • Focus: Systemic workplace issues, not personal failure
  • Named one of Thinkers50's 10 Best New Management Books (2022)
  • Argues: Self-care is not enough; orgs must fix root causes
  • Key stat from Moss 2024: 85% of global workforce reports declined well-being; burnout now exceeds 2020 levels in some sectors

"Why We Sleep: Unlocking the Power of Sleep and Dreams"

  • Author: Matthew Walker, PhD (UC Berkeley neuroscientist)
  • Critical for on-call, shift-work roles
  • Sleep deprivation = cognitive impairment equivalent to 0.08% BAC (drunk threshold)
  • 6 hours/night for 10 days = 24-hour no-sleep impairment
  • Note: Book received some academic criticism for overgeneralization, but core sleep science is solid

"Atomic Habits: An Easy & Proven Way to Build Good Habits and Break Bad Ones"

  • Author: James Clear
  • Practical: build sleep, exercise, mental health practices in incremental steps
  • Useful for: "I want to meditate but can't stick with it"

"Deep Work: Rules for Focused Success in a Distracted World"

  • Author: Cal Newport
  • Addresses: context-switching burnout, Slack/email interruptions
  • Strategies: time-blocking, notification silence, focus rituals
  • Useful for: developers in chaotic environments

Industry Models & Guides

GitLab All-Remote Handbook

Basecamp / 37signals "It Doesn't Have to Be Crazy at Work"

  • Philosophy: Calm company = better software, better retention
  • 4-day workweeks, no hero culture, sustainable pace
  • Controversy: Basecamp 2021 (remote-first policy reversal); mixed reviews on execution

Four-Day Workweek Trials

  • Nature Human Behaviour (July 2025): 2,900 workers, 141 orgs, 6 countries
  • Results: Burnout ↓, job satisfaction ↑, mental health ↑, productivity maintained
  • Adoption: 90%+ of companies kept policy after trial
  • Key drivers: reduced fatigue, better sleep, less work stress

Per-Role Recovery & Prevention Strategies

For SREs & On-Call Roles

During on-call:

  • Incident triage <5 minutes: is this real or alert noise?
  • Sleep protection: pager on phone (not laptop), keep phone out of bedroom if possible
  • Runbooks: fastest time to context = fastest time to fix
  • Stipend: paid incident time; you're "at work" during response even at 3 AM

Off on-call (recovery):

  • Genuinely off: no Slack, no email scanning
  • Recharge ritual: something that breaks work mental state (exercise, podcast, nature)
  • Post-incident debrief: blameless, learning-focused
  • Rotation fairness: no one >1 week/month, no stacking (on-call + late meetings)

Systemic:

  • Alert quality: tune to reduce false positives 50%+
  • Automation: auto-remediate common incidents
  • Runbook updates after every incident
  • Manager check-in post-incident: "How are you doing?"

For SOC Analysts

During shift:

  • Alert prioritization: high-confidence alerts only
  • Context clarity: analyst shouldn't have to guess next step
  • Shift buddy: someone to talk to during slow periods
  • Break rotation: mandatory 15-min breaks every 90 min

After shift:

  • Real separation: job ends; go do something non-work
  • Sleep: 7–9 hours (night shift = harder; sleep hygiene critical)
  • Physical exercise: proven anxiety reducer

Systemic:

  • False-positive reduction: 50% reduction in 6 months is achievable
  • Career path: SOC analyst → threat intelligence, forensics, incident response (escape alert fatigue)
  • Mental health screening: "How are you doing?" check-in every quarter
  • Peer support: analysts talk to analysts, not just managers
  • Pay competitively: $50k+ for L1 (above call center average) signals you value the role

For Helpdesk / Support Roles

Self-protection:

  • Script flexibility: you can deviate if justified (customer needs it)
  • Call limits: cap at 30–40 calls/day or 4 hours talk time (rest = documentation, training)
  • Tone management: it's okay to end abusive calls
  • Documentation: write down how you solved it; builds knowledge, pride in work

Systemic:

  • No surveillance metrics (keystroke logging, constant monitoring)
  • Autonomy: agent can say "let me research and callback" (reduces false confidence)
  • Career visibility: helpdesk as entry point to sysadmin, network, cloud roles (not dead end)
  • Wage: competitive ($45k+) for skilled support roles
  • Turnover cost awareness: replace a helpdesk agent for $29,700; keep them for $45k = wins

For CISOs

Personal survival:

  • Succession planning: identify and mentor internal successor (explicit, ongoing)
  • Board education: realistic scope, timeline, budget
  • Peer network: CISO roundtables, anonymized problem-sharing
  • Therapy: specialized in executive burnout and imposter syndrome

Systemic:

  • Balanced workload: no one CISO + VP Risk + Privacy Officer (split roles)
  • Incident response: clear escalation; CISO doesn't debug network outages
  • Clear wins: celebrate compliance program, security training completion (not just incident response)
  • Post-incident: debrief and learning, not blame
  • Sabbatical planning: take 2 weeks uninterrupted every 12 months (not checking email)

For Developers (All Levels)

Personal practice:

  • Define work hours: respect them (easier said than done)
  • Vacation truly off: no Slack, no "quick bug fixes"
  • Sleep: 7–9 hours non-negotiable (critical for focus, creativity)
  • Exercise: 30 min/day, 5 days/week (proven anxiety/depression reducer)
  • Hobby or learning outside work: identity not fused to job

Red flags (time to look for new job):

  • Chronic >50 hour weeks without comp time
  • Manager says "we're not monitoring hours" but culture says otherwise
  • On-call without rotation, stipend, or automation
  • Post-incident: blame not learning
  • Rapid turnover in your team (people voting with feet)

Systemic (if you're a manager):

  • Model boundaries: leave at 5 PM, take vacation
  • Celebrate completion, not hero responses
  • Code review as teaching, not criticism
  • 1-on-1s: "How are you doing?" without agenda
  • Clear expectations: what does done look like?

Honest Tensions & Tradeoffs

"Rest Culture" vs. "Performance Culture"

Rest Culture Argument:

  • Humans aren't machines; burnout is real
  • Sustainable pace = better long-term output
  • Self-care, mental health, boundaries = professional

Performance Culture Argument:

  • Some roles (IR during breach, on-call during outage) require urgency
  • Intense work can be fulfilling and career-accelerating (startup momentum)
  • Not everyone is overwhelmed; some thrive in high-intensity environments

Honest Take:

  • Both are true. Context matters.
  • Early-stage startup ≠ established company ≠ government contractor
  • Individual tolerance varies; design for the team, not the hero
  • Short-term intensity is fine (3–6 months); chronic overwork is corrosive

"Hustle Culture" Critique

The 2010s said: "Sleep is for the weak," "If you're not working nights, you don't care," "Real founders ship, not sleep."

Why that's wrong:

  • Sleep deprivation → worse decisions, more bugs, higher burnout risk
  • Overwork doesn't scale: you hit a wall
  • Glorifying overwork normalizes it for juniors who feel trapped

Why some people still glorify it:

  • Genuine accomplishment in intense sprints (fast-growing startup, big launch)
  • Survivor bias: "I thrived in chaos" doesn't mean everyone does
  • Competitive: "If my competitor works 60 hours, I have to too"

Moving forward:

  • Separate intensity (short-term, focused) from chronic overwork
  • Create cultural permission to say "I'm burned out"
  • Leaders model boundaries
  • Outcomes over hours: "Did it ship?" not "Did you sleep at the office?"

Return-to-Office Tension

Post-COVID, many orgs forced RTO (return to office). Data is mixed:

In-office benefits:

  • Spontaneous collaboration
  • Onboarding easier
  • Team culture harder to build remote

Remote benefits:

  • No commute (2 hours/day for some)
  • Focused work time
  • Geographic flexibility (access to more talent, better life balance)
  • Reduced cost of living (not paying SF rent)

Honest take:

  • Hybrid (3 days in, 2 days remote) common compromise
  • Async-first culture supports both in-office and remote
  • Mandate RTO for "culture" is often code for "executives miss seeing people"; metrics-driven orto reduces resentment
  • Choice > mandate (trust team to optimize)

South African Context

Mental Health Resources

South African Depression and Anxiety Group (SADAG)

  • sadag.org
  • Helpline: 011 234 4837 (24/7, free)
  • SMS/WhatsApp support available
  • Founded 1994; operates 30+ national helplines
  • Over 400 calls/day from all provinces
  • 2025: SADAG launched online support groups for educators, young adults, persons with disabilities

SA Society of Psychiatrists

  • Referrals to licensed psychiatrists (medication + talk therapy)
  • Private practice (varies by insurance)

Discovery Health Mental Health Coverage

  • Most insured South Africans have some mental health benefit
  • Psychologist, psychiatrist, counselor coverage (varies by plan)
  • Verify your policy limits and co-pay

SA Tech Industry & Burnout

  • SADAG 2025 Study: Over 50% of SA workers suffer from depression, anxiety, burnout due to workplace stress and job insecurity
  • Pay reality: SA tech salaries (especially early career) lag international; remote work (earning in USD) common escape valve
  • BEE compliance: additional reporting burden for tech orgs
  • Visa uncertainty: expats on critical skills visas face extra stress
  • Brain drain: burnout + opportunity abroad drives emigration

Practical for SA Tech Workers

  • Check your benefits: Do you have mental health coverage? How many sessions? Co-pay?
  • Therapy cost: Private ~R800–1200/hour; less common in corporate packages
  • Community: SA tech Slack groups (local, supportive)
  • Remote work: If burned out, consider contract work for international companies (better pay, often better WLB)
  • Sabbatical: Less normalized than US; negotiate if possible

Conclusion: It's a Systems Problem

Burnout is not a personal failing. It is an occupational phenomenon resulting from chronic workplace stress that has not been successfully managed.

Individual strategies matter (sleep, boundaries, therapy), but they are insufficient. Orgs must fix:

  • Alert quality (SOC fatigue)
  • On-call rotation fairness (SRE overload)
  • Succession planning (CISO turnover)
  • Career paths (helpdesk not dead-end)
  • Blameless postmortems (psychological safety)
  • Boundaries culture (Slack, async, hours respect)

Early warning signs:

  • You're working >50 hours/week and it's not temporary (3–6 month sprint)
  • You dread Slack/email
  • You've stopped doing things you enjoy
  • You can't remember when you took a real vacation
  • Cynicism about work ("nothing matters," "I'm an impostor")
  • Physical symptoms: sleep problems, headaches, stomach issues

If you see these in yourself:

  1. Tell someone (manager, therapist, trusted peer)
  2. Use your EAP (free, confidential)
  3. Take time off (real time: no work)
  4. Get professional help (therapist or counselor)
  5. If org doesn't support recovery: start looking for a new job

You are not the problem. The system is.

Source URLs (Remediation — direct citations + free resources)

Official ICD-11 & Clinical Standards

Industry Research & Surveys

Crisis & Emergency Support (24/7)

United States

United Kingdom

South Africa

  • SADAG (South African Depression and Anxiety Group): sadag.org — helpline 011 234 4837 (24/7, free); SMS/WhatsApp available

Australia

  • LifeLine Australia: lifeline.org.au — phone 13 11 14 (24/7); chat online

International

  • Befrienders Worldwide: befrienders.org — 90+ help centres across 32 countries; phone, email, SMS, chat

Mental Health Organizations & Communities

  • Mental Health America (MHA): mhanational.org — screening tools, workplace resources, referrals
  • National Alliance on Mental Illness (NAMI): nami.org — support groups, education, peer resources
  • Open Sourcing Mental Illness (OSMI): osmihelp.org — tech-focused mental health community, surveys, corporate resources

Free YouTube Channels & Educational Content

Apps with Free Tiers (Meditation & Cognitive Behavioral Tools)

  • Insight Timer (free, extensive library): insighttimer.com — 100,000+ free meditations, music, sleep stories; premium $9.99/month
  • Calm (limited free; 14-day premium trial): calm.com — free tier: rotating meditations, limited sleep stories; premium $69.99/year
  • Headspace (limited free; 7-day trial): headspace.com — free: intro courses, some meditations; premium $69.99/year; free for US teens
  • Woebot (free trial; enterprise focus): woebothealth.com — AI CBT chatbot; 10-session free trial; formerly direct-to-consumer, now enterprise partnerships

Essential Books (Burnout, Sleep, Resilience)

TitleAuthor(s)PublisherYearURL
Burnout: The Secret to Unlocking the Stress CycleEmily & Amelia NagoskiBallantine2019Amazon
The Body Keeps the Score: Brain, Mind, and Body in the Healing of TraumaBessel van der Kolk, MDPenguin2014Amazon
Why We Sleep: Unlocking the Power of Sleep and DreamsMatthew Walker, PhDScribner2017Amazon
Atomic Habits: An Easy & Proven Way to Build Good Habits and Break Bad OnesJames ClearAvery2018Amazon
It Doesn't Have to Be Crazy at WorkJason Fried & David Heinemeier HanssonHarper Business2018Basecamp

Industry-Specific Resources & Guides

SRE / DevOps / On-Call

Security / SOC / Pentesting

Remote Work & Boundaries

Four-Day Workweek Research

Per-Role Resilience Tactics (Sourced)

For SREs & On-Call Teams

Key Resource: Google SRE Book: Operational Overload

  • Alert tuning: Reduce false positives 50%+ (alleviates alert fatigue, improves signal-to-noise)
  • Incident triage <5 min: Clear escalation paths reduce cognitive overload
  • Runbook quality: Fastest time to context = fastest time to fix
  • Rotation fairness: No one on-call >1 week/month; avoid stacking with late meetings
  • Post-incident recovery: Mandatory 24–48 hours off after major incidents
  • Blameless postmortems: Learning-focused reduces PTSD-like symptoms and moral injury

For SOC / Security Operations

Key Sources: SANS 2025 Detection & Response Survey; Stamus Alert Fatigue Research

  • False-positive reduction: 50% improvement in 6 months is achievable; prioritize high-confidence alerts only
  • Shift buddy system: Peer support during slow periods; reduces isolation
  • Career paths out: SOC analyst → threat intelligence, forensics, IR (escape alert fatigue)
  • Competitive pay: $50k+ for L1 roles signals value; entry helpdesk avg $39.6k
  • Break rotation: Mandatory 15-min breaks every 90 min

For Helpdesk / Support Roles

Key Source: GHDSI Helpdesk Burnout Research

  • Script flexibility: Agents can deviate if customer/situation justifies it
  • Call limits: Cap 30–40 calls/day or 4 hours talk time; rest = documentation, training
  • No surveillance metrics: Replace keystroke loggers / AHT pressure with outcome metrics (tickets closed, CSAT)
  • Autonomy to escalate: Agent can say "let me research and callback" (reduces forced confidence, improves accuracy)
  • Career visibility: Helpdesk → sysadmin, network, cloud (not dead-end)
  • Wage competitiveness: $45k+ for skilled support (vs. $29.7k replacement cost)

For CISOs

Key Source: Heidrick & Struggles 2024 CISO Survey

  • Succession planning: Identify & mentor internal successor (explicit, ongoing; address 47% gap)
  • Balanced scope: No single CISO + VP Risk + Privacy Officer role (split explicitly)
  • Peer network: CISO roundtables, anonymized problem-sharing (isolation is major stressor)
  • Clear wins: Celebrate compliance milestones, training completion (not just breach response)
  • Sabbatical planning: 2 weeks uninterrupted every 12 months (not email-checking)
  • Board education: Realistic scope, timeline, budget (set expectations; reduce blame culture)

For Developers (All Levels)

Key Source: Cal Newport | Deep Work (context-switching burnout)

  • Define work hours & respect them: 5 PM off-limits; genuine separation
  • Sleep 7–9 hours: Non-negotiable (critical for focus, mood, creativity)
  • Exercise 30 min/day, 5x/week: Proven anxiety & depression reducer
  • Vacation truly off: No Slack, no "quick bug fixes"
  • Red flags to job-search: Chronic >50 hrs/week, on-call without rotation/stipend, blame culture, rapid team turnover

Conclusion

Burnout is systemic. Individual strategies (sleep, boundaries, therapy) are necessary but insufficient. Organizations must fix root causes:

  • Alert quality and tuning (SOC, DevOps)
  • On-call rotation fairness and automation (SRE)
  • Succession planning (CISO, bus-factor roles)
  • Career paths and skill development (helpdesk, support)
  • Blameless, learning-focused incident response
  • Boundaries culture (async-first, no always-on Slack)

Early warning signs:

  • Working >50 hrs/week without temporary cause (3–6 month sprint exception)
  • Dread of email/Slack
  • Stopped doing things you enjoy
  • Can't remember last real vacation
  • Cynicism about work ("nothing matters")
  • Physical symptoms: sleep problems, headaches, stomach issues

If you see these in yourself:

  1. Tell someone (manager, therapist, peer)
  2. Use your EAP (free, confidential)
  3. Take real time off (no work)
  4. Get professional help
  5. If org doesn't support recovery: start looking for a new job

You are not the problem. The system is.

Sources (Original)

Rate this article
…
Was this helpful?
Comments (—)
0/2000