The Invisible Overtime: When Empathy in Engineering Leadership Becomes Unsustainable

General
1

I need to talk about something that’s been weighing on me—something I think a lot of us in engineering leadership are experiencing but rarely name out loud.

The Hidden Third Shift

Last Tuesday, I wrapped up my “official” workday around 6 PM. Technical roadmap reviews during the day, stakeholder alignment meetings in the afternoon. Standard VP stuff. Then came what I’m starting to call the “hidden third shift.”

7 PM: Slack message from a junior engineer anxious about tomorrow’s architecture review. Spent 30 minutes reassuring them their design is solid.

8 PM: Text from a senior engineer worried about the reorganization rumors. Another 45 minutes being the calm, steady voice while my own anxiety about those same rumors sits in my chest.

9:30 PM: Email from a team lead overwhelmed by the new AI tool expectations from leadership. Our execs saw a Copilot demo and immediately added 30% more features to the sprint. I draft a careful response about sustainable pace while figuring out how to manage up tomorrow.

This is emotional labor—and it’s invisible, exhausting, and increasingly unsustainable.

The Data Behind What We’re Feeling

I thought I was just bad at boundaries until I saw the research. Turns out, 22% of engineering leaders are at critical burnout levels (LeadDev 2025 report). Another 24% are moderately burned out.

Even more telling: 65% of us report expanded responsibilities, with 40% managing more people—yet only 3% saw their scope decrease. We’re pressure valves for our teams, absorbing anxiety about layoffs, translating executive decisions, calming demo nerves, mentoring through imposter syndrome.

And here’s what really got me: manager behavior explains retention better than remote/hybrid policies. We’re literally the difference between people staying or leaving—but who’s supporting us?

When “Soft Skills” Becomes a Mask for Real Labor

I’m tired of emotional intelligence being called a “soft skill” when it’s some of the hardest work I do. These aren’t nice-to-haves—they’re the invisible scaffolding holding our teams together during constant uncertainty.

The research shows 78% of workers now rate mental health support as a top factor when evaluating employers (up from 52% in 2019). Guess who delivers that support on the ground? Middle managers and engineering leaders, working what’s become normalized 12-15 hour days since AI tools launched.

We’re told AI increases productivity, but I’m living the reality: leadership inflated sprint expectations, team utilization dropped after the initial excitement, and I’m the one managing the gap between promise and reality—at 9:30 PM on a Tuesday.

The Question I Can’t Stop Asking

Where do we draw the line?

I believe in empathetic leadership. I’ve seen firsthand how it builds trust, enables psychological safety, and creates the conditions for great engineering work. But empathy without boundaries doesn’t just burn me out—it ultimately fails my team too. You can’t pour from an empty cup.

So I’m genuinely asking this community:

  • How do you advocate for your own boundaries while still being the leader your team needs?
  • What does sustainable empathy actually look like in practice, not just in theory?
  • When executive expectations and team reality diverge, how do you manage that gap without absorbing all the stress yourself?

I know some of you have figured out ways to do this work sustainably. I need to hear what’s actually working, because the current path isn’t sustainable—and I know I’m not alone in feeling this.

Looking forward to hearing your experiences and strategies. Even if you’re still figuring it out like me, knowing we’re in this together helps.

2

Keisha, thank you for naming this so clearly. This isn’t individual weakness—it’s a systemic issue that we’ve been treating as a personal problem.

The View from the C-Suite

From where I sit as CTO, I see how emotional labor gets delegated down the org chart without corresponding resource allocation. We ask VPs and Directors to “manage team morale” and “ensure psychological safety” as if these are cost-free add-ons rather than real work requiring real energy.

Here’s what opened my eyes: I started tracking my own hours and realized I was spending nearly 15 hours a week on what I call “people hours”—distinct from technical strategy, architecture reviews, or stakeholder management. Coaching managers through difficult conversations. Being the sounding board for career anxiety. Translating board concerns into messages that won’t trigger panic.

When I shared this data with our board, they were genuinely surprised. They thought “people management” was built into my technical leadership role, not understanding it’s become a parallel full-time job.

Making the Invisible Visible

One thing that’s actually working: I’ve made emotional labor explicit in our role definitions and performance frameworks. For example:

  • Engineering Manager role now includes: “Dedicated people development time (minimum 5 hours/week)” as a protected calendar commitment
  • Director+ roles include: Quarterly peer support budgets for coaching and mental health resources
  • We’re experimenting with EI metrics: Teams with leaders who score high on emotional intelligence show 15% better internal mobility for underrepresented groups—so we’re making this part of promotion criteria

The challenge I’m wrestling with: How do we measure and value this work without turning empathy into just another KPI? I don’t want “emotionally available” to become a checkbox that people game rather than a genuine leadership quality.

The Structural Changes We Need

Individual coping strategies only go so far. We need:

  1. Peer support structures: Regular forums where managers can be vulnerable with each other, not just “manage up” to executives
  2. Protected boundaries: Real consequences when executives expect 24/7 availability
  3. Resource allocation: If we’re asking leaders to do this work, we need to reduce other expectations or increase headcount accordingly

Keisha, your question about managing the gap between executive expectations and team reality hit hard. I’ve been that executive setting unrealistic expectations based on AI tool demos. Now I’m trying to model sustainable pace at the top—leaving meetings to attend my daughter’s school events, being explicit about my own boundaries—hoping it cascades down.

Still figuring this out, but conversations like this help us move from individual survival tactics to systemic solutions.

3

This resonates so deeply. I feel like I’m constantly translating between two worlds—shielding my team from executive anxiety while managing up to keep leadership grounded in reality.

The Weekend That Nobody Saw

Two weeks ago, layoff rumors started circulating. Nothing official, just whispers from finance about “restructuring discussions.” By Friday afternoon, three engineers had messaged me privately, worried about their jobs.

Saturday and Sunday, I spent 6 hours total on video calls and Slack—not because anyone asked me to, but because I knew if I didn’t address the anxiety immediately, we’d lose a week of productivity to panic and resume updates.

Monday morning, the team showed up focused and steady. My boss commented on how “resilient” my team was. Nobody saw the invisible 6 hours that created that resilience. That was my weekend.

The Dual Burden of Mid-Level Leadership

Michelle, your point about emotional labor being delegated down without resources is exactly what I experience. As Director of Engineering, I’m:

  • Absorbing anxiety from above: Translating executive strategy shifts into messages that won’t demoralize the team
  • Supporting pressure from below: Being the steady presence when engineers are overwhelmed, uncertain, or frustrated
  • Carrying additional mentorship load: As one of the few Latino leaders at this level, I mentor engineers from underrepresented backgrounds—rewarding but exhausting work that doesn’t show up in my job description

Keisha mentioned the AI expectation inflation—that’s my daily reality. Leadership saw Copilot demos and immediately inflated sprint commitments by 30%. When I pushed back with data showing sustainable velocity, I was told I’m “not thinking ambitiously enough.”

Making It Visible (My Experiment)

I started documenting emotional labor hours in my weekly reports. Not complaining—just factual:

“Team support: 8 hours (2 career development conversations, 3 anxiety check-ins related to restructuring, 1 conflict mediation)”

At first, my manager didn’t know what to do with this data. But over time, it’s creating visibility. Last month he asked, “Is there a way to distribute some of this?” That question felt like progress.

The Question That Keeps Me Up

How do other mid-level leaders prevent burnout while maintaining the empathy that makes them effective?

I don’t want to become the leader who stops caring—that’s not who I am. But the current pace isn’t sustainable. I’m looking for that middle path between “always available emotional support” and “detached manager who just delegates tasks.”

If you’ve found that balance, please share. Because right now, I’m running on fumes and wondering how long I can keep being the person my team needs while also being present for my own family.

4

Coming from the product side, I need to acknowledge something uncomfortable: I’ve probably been part of this problem without realizing it.

What I See (and Value) from the Outside

The best engineering leaders I’ve worked with—people like Keisha and Luis—are what make product-engineering partnerships actually work. They absorb complexity, translate technical constraints into opportunities, and keep their teams steady during pivots and pressure.

I’ve always appreciated this, but I never thought about the sustainability of it. Reading Luis’s story about the 6-hour weekend maintaining team morale—that’s invisible labor that I’ve benefited from without acknowledging the cost.

My Guilty Admission

I’ve absolutely contributed to emotional burden without meaning to:

“Hey, just wanted to check in on team morale before we announce the roadmap change…”

“Can you gauge whether the team is nervous about the Q2 targets?”

“I’m hearing some tension between frontend and backend—can you smooth that out?”

These felt like reasonable asks from a cross-functional partner. I didn’t realize I was essentially outsourcing stakeholder anxiety management to engineering leaders who are already maxed out.

Cross-Functional Perspective: This Isn’t Just Engineering

Here’s what I’m realizing: PMs have similar invisible labor. I calm anxious stakeholders, translate executive vision into roadmaps that won’t break engineering, and absorb the emotional weight of scope negotiations. Maybe this is the leadership tax across all functions?

The difference: PMs are often evaluated on stakeholder management as an explicit skill. Engineering leaders do this work but it’s labeled “soft skills” and treated as secondary to technical leadership.

A Proposal: Shared Support Structures

Michelle mentioned peer support structures for managers. What if we created cross-functional leadership support?

Product and engineering leaders facing similar emotional labor challenges, but we’re each building coping mechanisms in silos. Could we:

  • Share strategies for sustainable empathy across functions?
  • Create joint boundaries around executive expectations?
  • Support each other instead of inadvertently adding to each other’s load?

My Commitment

I’m committing to being more mindful about when I’m genuinely collaborating vs when I’m adding to EM emotional load. Before I send that “can you check on team morale” message, I need to ask:

  • Is this my anxiety I’m offloading, or actionable partnership?
  • Can I address this directly with the team instead of asking the EM to do emotional translation?
  • Am I contributing to sustainable leadership or adding to the burnout cycle?

Thank you for opening this conversation. It’s making me rethink how I show up as a partner.

5

I need to share something I don’t talk about much: my startup failed in part because I destroyed myself trying to emotionally carry the entire team.

The Story I Don’t Usually Tell

During our final six months, funding dried up, customers churned, and the team could feel the ship sinking. I absorbed ALL of it—every anxiety, every fear, every “should I start looking for jobs?” conversation.

I thought that’s what leaders do. Be the steady presence. Protect the team. Keep morale high even when you’re terrified.

Three weeks before we shut down, I ended up in the ER with stress-related chest pain. The doctor said my cortisol levels were “consistent with someone in chronic crisis.” That’s when I realized: empathy without boundaries doesn’t just burn you out—it destroys you AND fails the team.

When I was hospitalized, the team had no leader. The very thing I was trying to prevent (team instability) happened anyway, because I’d made myself the single point of failure for emotional support.

What If We Designed Emotional Labor Like a Product?

I keep thinking about this through my design lens. When we design products, we think about:

Scope and boundaries: What’s in v1 vs future releases?
Distributed load: How do we prevent single points of failure?
Rest and recovery: Systems need downtime to stay reliable.

What if we applied this to emotional labor?

  • Office hours for support: Instead of 24/7 availability, I now have scheduled “check-in hours” twice a week. Urgent issues still get immediate attention, but routine anxiety has a container.
  • Peer support systems: One leader can’t carry everything. Creating spaces where team members support each other distributes the load.
  • Built-in recovery: Protecting actual time off, not just “technically on vacation but still on Slack.”

The Reality Check I’m Still Wrestling With

Here’s my struggle: In high-growth or crisis modes, boundaries feel impossible.

When the startup was failing, there was no “good time” to set boundaries. When you’re scaling fast, there’s always another fire. Luis’s layoff weekend—if he’d set boundaries and waited until Monday, the team would have spiraled all weekend.

So I don’t have this figured out. I can share what hospitalization taught me about unsustainable empathy, but I’m still learning how to actually maintain boundaries under pressure.

What I’m Trying Now

  • Naming the trade-offs explicitly: “I can be available tonight for this crisis, but I’ll need to take Friday afternoon off to recover.” Making the cost visible.
  • Asking for help earlier: Instead of being the hero who handles everything, inviting others into problem-solving before I’m at capacity.
  • Tracking my own energy: Just like Keisha tracks burnout data, I’m tracking when I feel depleted vs energized. Patterns are emerging.

David, I love your commitment to cross-functional support. Product and engineering leaders facing similar challenges—why are we solving this in isolation?

To everyone in this thread: What’s actually working for you? Not the theory, not the aspirational “self-care” advice, but the real tactics you’ve used to maintain boundaries while still being the empathetic leader your team needs. Because I need that wisdom, and I think we all do.