Engineering Managers Are Burning Out: 65% Have Expanded Responsibilities, Only 3% Saw Scope Decrease

vp_eng_keisha · February 5, 2026, 6:59am

I need to talk about this because I’ve been living it and watching it happen to my peers for two years straight.

LeadDev’s 2025 Engineering Leadership Report surveyed 617 engineering leaders and the numbers are devastating:

22% at critical burnout levels
24% moderately burned out
Only 21% categorized as “healthy”
65% reported expanded responsibilities
40% managing more direct reports than before
Only 3% saw a decrease in scope
38% working longer hours
40% said their teams are less motivated than a year ago

That last statistic — 79% of engineering leaders experiencing some level of burnout — should be a five-alarm fire for every organization. But instead, we’re still having conversations about “resilience” and “self-care” as if the problem is that managers aren’t doing enough yoga.

How We Got Here

The burnout crisis has a clear origin story, and it’s not mysterious.

Phase 1: The Layoffs (2023-2025). Meta’s Zuckerberg criticized “bloated management hierarchies.” Amazon’s Jassy announced plans to boost the IC-to-manager ratio by 15%. Amazon cut roughly 14,000 managerial positions — about 13% of their total. The message was clear: management layers are overhead to be eliminated.

Phase 2: The Redistribution. When you cut managers but keep the work, the remaining managers absorb the load. That’s the 65% with expanded scope. Teams got bigger. Responsibilities got broader. But nobody’s calendar got shorter.

Phase 3: The “Super Hybrid” Role. Here’s what really changed: managers are now expected to be player-coaches again. During the 2010s, engineering managers were encouraged to move away from hands-on coding to focus on leadership. Now, with smaller management cohorts and pressure to demonstrate technical relevance (especially with AI looming), managers are expected to code AND lead AND hire AND do performance management AND run roadmap planning AND handle cross-functional alignment.

As one expert told LeadDev: “A lot of managers I talk to feel insanely stressed out and beyond what they’re able to keep up with. The problem is the variety and sets of responsibilities that are difficult to manage.”

The “Manager Squeeze” Is Real

Perceptyx coined the term “the manager squeeze” and the research backs it up. Managers are sandwiched between:

From above:

Pressure to deliver more with fewer resources
Expectations to drive AI adoption and transformation
Accountability for metrics they have decreasing control over
Board-level mandates to cut costs while maintaining velocity

From below:

Teams anxious about layoffs and AI displacement
Direct reports seeking career development and growth
Morale management for increasingly demotivated teams
Emotional labor of absorbing fears about job security

The data shows that managers consistently score lower than both executives and individual contributors on work-life balance. They’re the pressure point in the organizational sandwich, absorbing stress from both directions.

And here’s the multiplier effect: managers account for 70% of the variance in team engagement. When managers disengage, the cascading effect on their teams creates multiplicative productivity losses. A burned-out manager doesn’t just affect themselves — they affect every person who reports to them.

The Financial Cost Nobody’s Calculating

The numbers are staggering when you actually do the math:

Burnout costs approximately ,000/year per non-manager, ,000/year per manager, and ,000/year per executive
Burned-out workers are 3x more likely to be actively job searching (45% vs. 16% of non-burned-out workers)
DHR Global found that 52% of workers say burnout drags down engagement, up from 34% in 2025

So the same companies that cut management layers to save money are now paying for manager burnout through:

Higher turnover in remaining managers (expensive to replace)
Cascading team disengagement (productivity loss)
Declining innovation (exhausted people don’t take creative risks)
Knowledge loss when burned-out managers leave (institutional memory walks out the door)

It’s Not About Hours Anymore — It’s Cognitive Overload

This is the shift I’m seeing that the “work-life balance” conversation misses entirely. The primary driver of burnout is no longer excessive hours. It’s cognitive overload.

What’s driving it:

Context-switching: managers toggle between coding, 1:1s, roadmap meetings, incident response, hiring interviews, and performance reviews — often in a single morning
Fragmented tools: Slack, Jira, GitHub, Linear, Notion, Confluence, email — each with their own notification stream demanding attention
Emotional labor: absorbing layoff anxiety, AI displacement fears, career uncertainty — none of which appears in the job description
Decision fatigue: making dozens of technical and people decisions daily with insufficient information

The share of employees citing lack of reward or recognition as a burnout driver nearly doubled from 17% to 32%. Managers are doing more, getting recognized less, and watching their role described publicly as overhead to be eliminated.

What I’m Doing About It (And What’s Not Working)

I’ll be honest about what I’ve tried at my org (scaling from 25 to 80+ engineers):

What hasn’t worked:

Wellness programs (meditation apps, mental health days) — these treat symptoms, not causes
“Protected focus time” on calendars — it gets overridden within weeks
Telling managers to “prioritize” — when everything is urgent, this is meaningless advice
Hiring more managers — the budget doesn’t exist, and it takes 6+ months to onboard effectively

What’s actually helping:

Ruthless scope reduction: I personally review every manager’s responsibility portfolio quarterly and actively remove things. If nobody owns it after removal, maybe it didn’t matter.
Explicit capacity planning: We treat management capacity like we treat server capacity. If a manager is at 90% utilization, they can’t absorb incidents. We maintain slack intentionally.
Separating the player-coach expectation: Some of our managers are pure people leaders. Some are tech leads who do light management. Forcing everyone into the hybrid role is what breaks people.
Measuring manager health as a leading indicator: We track manager engagement monthly, not annually. If a manager’s engagement drops, that’s a leading indicator of team problems in 60-90 days.

The Question I Keep Coming Back To

Are we witnessing the structural redefinition of engineering management — from a career path into a temporary rotation that nobody wants to stay in?

Management salaries have stagnated. The role’s been publicly labeled as overhead. The scope keeps expanding while the recognition keeps shrinking. 82% of boards expect to reduce up to 20% of their workforce due to AI within three years, and middle management is disproportionately targeted.

At some point, rational people will stop volunteering for this role. And then what happens to the teams that depend on good management to function?

I’d love to hear from other engineering leaders: how burned out are you, really? Not the answer you give in your skip-level. The honest one. And what’s your organization actually doing about it — not the wellness program brochure, but the structural changes?

eng_director_luis · February 5, 2026, 7:00am

Keisha, reading this felt like reading my own journal from the past 18 months. I manage 40+ engineers at a Fortune 500 financial services company and the “super hybrid” role description hit me hard.

The Player-Coach Trap at Scale

At my level — Director of Engineering — the player-coach expectation takes a specific form. I’m not expected to write production code daily, but I am expected to:

Make architectural decisions that require deep technical context
Review designs and ADRs with enough detail to catch critical issues
Evaluate technical talent in hiring panels (usually 3-4 interviews per week)
Maintain credibility with principal engineers who will push back if I’m out of touch
Drive AI tool adoption strategy while also being hands-on enough to know what works

All of this while managing 5 engineering managers, each with 6-8 direct reports, participating in cross-functional leadership meetings, running budget planning, and handling escalations from anywhere in the org.

The result? I tracked my own time for a month. Here’s what I found:

Activity	Hours/Week	Category
1:1s with direct reports	5	People management
Skip-level 1:1s	3	People management
Cross-functional meetings	8	Organizational
Technical reviews/decisions	6	Technical
Hiring/interviews	4	Recruiting
Incident response/escalations	3	Reactive
Strategy/planning	4	Strategic
Email/Slack/async communication	8	Administrative
Actual focused thinking	2	What I should be doing more

That’s 43 hours of committed time before I’ve done any of my own strategic work. The “2 hours of focused thinking” is what’s left — and that’s where the innovation, the team development planning, and the long-term architecture decisions are supposed to happen.

The Recognition Problem Is Real

You mentioned recognition declining while scope expands. I want to put a specific shape on this.

When Amazon publicly frames manager reduction as an efficiency gain, it sends a message through the entire industry: managers are cost, not value. My own CEO has referenced the Amazon playbook in board meetings.

I’ve watched three of my peer Directors leave in the past year. Not for more money — for roles with clearer scope. One went to a smaller company as VP where she manages fewer people but with a clear mandate. One went back to IC as a Staff Engineer (with a pay bump). One left tech entirely.

The pattern is consistent: high-performing managers are opting out of management. The ones who stay are either deeply mission-driven, haven’t found an alternative yet, or — and this is the concerning one — are too burned out to have the energy to job search.

What I’d Add to Your Framework

Your four-point framework is strong. I’ve tried something similar and want to add two things I’ve learned:

5. Delegate the emotional labor explicitly. One of the biggest hidden costs is that managers absorb their team’s anxiety about layoffs, AI, and career uncertainty. At my org, I’ve started providing managers with talking points and frameworks for these conversations, rather than expecting each manager to figure out how to address existential career anxiety on their own. I also brought in an external coach who works with our management team — not as therapy, but as skills development for navigating uncertainty conversations.

6. Make scope visible to leadership. I created a “management scope dashboard” that shows each manager’s: direct reports, number of active projects, cross-functional commitments, hiring involvement, and incident response load. When my VP asks why something isn’t moving faster, I can point to the dashboard instead of having an abstract conversation about “capacity.” Making the load visible is the first step toward getting permission to reduce it.

The cognitive overload point you raised is the key insight. The problem isn’t that any single responsibility is too much. It’s that the variety and context-switching cost of managing 8 different types of work simultaneously drains cognitive resources faster than any amount of “time management” can solve.

alex_dev · February 5, 2026, 7:01am

I want to add the IC perspective here because burned-out managers are not just a leadership problem — it’s a problem for everyone who reports to them.

What a Burned-Out Manager Looks Like From Below

I’ve had three engineering managers in the past two years. Two of them showed clear signs of what I’d now recognize as burnout, and the impact on my day-to-day was significant:

The cancelled 1:1s. When a manager hits overload, the first thing that gets sacrificed is the recurring 1:1. My last manager cancelled or rescheduled about 60% of our 1:1s over a six-month period. Each time it was a legitimate conflict — an escalation, a cross-functional meeting, a hiring debrief. But the cumulative effect was that I had no regular channel for career conversations, technical guidance, or raising concerns. I just stopped bringing things up because there was never a good time.

The slow feedback loop. PRs that used to get reviewed within a day started sitting for 3-4 days because my manager was both a reviewer AND in back-to-back meetings. Design docs that needed a decision would languish in “I need to think about this” limbo for weeks. Not because the manager didn’t care, but because the mental bandwidth for thoughtful technical decisions was already consumed by everything else.

The emotional flatness. This is the subtle one. A healthy manager brings energy to team conversations — excitement about wins, concern about risks, curiosity about technical problems. A burned-out manager goes through the motions. Standup becomes status reporting. Retros become checkbox exercises. The team starts to mirror the energy, and suddenly everyone’s just clocking through the sprint.

Why ICs Should Care About This Data

The 70% variance stat Keisha mentioned is not abstract. Here’s what it means concretely for ICs:

Your career development depends on your manager having time to advocate for you. If your manager is at 43 hours of committed time (per Luis’s breakdown), when are they preparing for your promotion case? When are they identifying stretch opportunities? The answer is: they’re not, or they’re doing it at 10pm on a Sunday.
Your technical growth depends on quality feedback. A manager who has 2 hours of focused thinking per week is not going to give you the kind of deep design review feedback that makes you better. You’ll get “LGTM” instead of “have you considered X” — not because they’re a bad manager, but because they’re drowning.
Your team’s ability to shield you from organizational chaos depends on manager health. One of the most valuable things a good manager does is filter organizational noise. They attend the cross-functional meetings so you don’t have to. They translate executive priorities into clear team goals. When the manager is overwhelmed, that filtering breaks down and suddenly ICs are getting pulled into meetings and Slack threads that have nothing to do with their work.

The Uncomfortable IC Responsibility

I’ll say something that might not be popular: ICs have a role to play in reducing manager load.

I’ve started thinking about what I can do to help my current manager (who I can tell is stressed but trying hard):

Being low-maintenance where I can. If I can answer my own question with 15 minutes of research, I don’t escalate it. I write decisions down so my manager can async review rather than needing a synchronous discussion.
Running my own career development. Instead of waiting for my manager to identify opportunities, I propose specific projects and ask for a yes/no rather than an open-ended “what should I work on next.”
Being explicit about what I need. Instead of a vague “I’d like more growth opportunities,” I say “I’d like to lead the design review for the auth migration. Can you sponsor that?” Concrete asks are easier for an overloaded manager to action.
Providing upward feedback when something’s slipping. If a manager’s burnout is affecting the team and they don’t know it, someone needs to say something. I’ve learned to frame it as “I’ve noticed our 1:1s have been tough to schedule — is there anything I can take off your plate to free up time?”

None of this solves the structural problem. But while we wait for organizations to fix the system, ICs who understand what their managers are dealing with can make the relationship work better for everyone.

The question I keep coming back to: if management keeps becoming less attractive, who’s going to mentor the next generation of engineers? I’m 7 years in, approaching the point where I should be thinking about whether to go into management. Threads like this make me think twice.

cto_michelle · February 5, 2026, 7:01am

This thread is one of the most important conversations happening in engineering leadership right now, and I want to address the systemic question Keisha raised: is engineering management becoming a temporary rotation rather than a career path?

The Honest Answer: Maybe. And That Might Not Be Entirely Bad.

I know that’s a provocative take in a thread about manager burnout. But after 25 years in this industry, I think we need to separate two problems that are getting conflated:

Problem 1: The current state of engineering management is unsustainable. This is unambiguously true. The data is clear. 65% expanded scope, 3% decreased scope, 79% experiencing burnout. This is a crisis and organizations need to fix it. Full stop.

Problem 2: The traditional model of “management as permanent career destination” may have been flawed from the start. This is more nuanced and worth discussing separately.

The 2010s model assumed managers should fully leave hands-on work, build their identity around people leadership, and climb the management ladder. But that model created its own problems: managers who lost technical credibility, career paths that felt one-directional, and a stigma around returning to IC work.

What I think we’re actually moving toward — once we get past the current crisis — is something more fluid. Not the current “super hybrid” nightmare where one person does everything badly, but a system where people move between IC and management roles more naturally throughout their careers.

Charity Majors wrote about the “engineer-manager pendulum” years ago. I think the pendulum model was ahead of its time. The execution is the problem — we’re forcing the pendulum to swing too fast while cutting resources, rather than building organizational structures that support intentional transitions.

What I’ve Changed at My Organization

I’m CTO of a mid-stage SaaS company scaling from 50 to 120 engineers. Here’s what I’ve implemented after seeing the burnout data hit my own leadership team:

1. The Management “Tour of Duty” Model

We explicitly frame engineering management as a 2-3 year rotation, not a permanent career move. When someone takes a management role, we discuss:

What they want to learn from the experience
What success looks like after 2-3 years
What their path back to IC or into a different leadership role could look like
How we’ll maintain their technical skills during the rotation

This changes the psychology fundamentally. Managers don’t feel trapped. They feel like they’re on a defined mission with an exit plan.

2. Splitting the Atom: People Lead vs. Tech Lead vs. Delivery Lead

The “super hybrid” role fails because it combines three fundamentally different jobs:

People Lead: 1:1s, career development, performance reviews, hiring, team culture
Tech Lead: Architecture decisions, design reviews, technical direction, code quality
Delivery Lead: Sprint planning, cross-functional coordination, roadmap execution, stakeholder management

We don’t ask anyone to do all three. Every team has these roles distributed across 2-3 people. The engineering manager focuses on people. The tech lead (senior IC) owns technical direction. The product manager or a TPM handles delivery coordination.

This reduced manager burnout measurably — our internal pulse survey showed a 31-point improvement in manager satisfaction after 6 months.

3. The “No New Meetings” Policy for Managers

For any new recurring meeting that would include a manager, we require:

A written justification for why this meeting needs to exist
Identification of what meeting or responsibility it replaces (net zero)
A 90-day sunset review

We discovered that 40% of our managers’ meeting load was accumulated ritual — meetings that were created for a specific purpose, achieved it, and then continued indefinitely because no one cancelled them. Just enforcing the sunset review freed 3-5 hours per week for most managers.

4. Manager Sabbaticals

Every 18 months, managers get a 2-week period where their reports are temporarily distributed to other managers, and the manager either works on a technical project, takes time off, or does a learning sprint. This prevents the identity erosion that comes from never touching the craft.

The Recognition Problem Requires Organizational Honesty

Luis and Keisha both flagged the recognition issue. When the industry narrative says “management is overhead,” the psychological impact on managers is profound.

I’ve started being explicit with my leadership team about this in all-hands and board presentations. I frame management impact using language the business understands:

“Our engineering managers saved us an estimated in reduced attrition this quarter” (using the 70% engagement variance data)
“Manager-led development programs produced N promotions and M internal transfers, representing in avoided external hiring costs”
“Teams with healthy managers shipped X% more features with Y% fewer escaped defects”

If we don’t quantify management value in business terms, the narrative will default to “management is cost.”

Alex’s Question Deserves a Direct Answer

Alex asked: if management keeps becoming less attractive, who mentors the next generation?

My answer: we need to stop assuming management is the only path to mentorship. Staff and Principal Engineers should be mentoring. Senior ICs should be running design reviews. Technical leadership doesn’t require people management authority.

The mistake was ever equating “leadership” with “management.” They’re related but distinct capabilities. The organizations that thrive in 2026 and beyond will be the ones that build leadership structures where both paths — IC and management — carry equal weight, equal recognition, and equal capacity for organizational impact.

But that only works if we fix the current crisis first. Burned-out managers can’t build the bridge to a better model while they’re drowning.