The Burnout You Can’t See

I’ve sat across from enough startup founders and senior engineers to know the look. Not the obvious one- red eyes, missed deadlines, the person who finally breaks down in a sprint retrospective. I mean the other look. The one that took me years to recognize.

Bright eyes. Clean Git commits. On time for every standup. They’ll tell you they’re “crushing it” and mean it, in the moment. They’re the ones you promote. The ones you give the hardest problems to. The ones who stay late not because anyone asks, but because their brain won’t let them leave until the thread resolves.

And they’re burning out in ways that don’t register on your dashboards.

What I missed for years

Early in my practice, I treated the visible cases. The founder who stopped sleeping. The CTO who cried in our first session- his first cry in fifteen years. These were easy to spot, relatively speaking. They had symptoms. They had crashed.

But the quiet ones kept showing up in my office through side doors. Referred by a partner who noticed they stopped arguing. A CEO who couldn’t explain why their best hire felt “off” in one-on-ones. Or they came themselves, confused, saying some version of: “I think I need to work harder. Something’s wrong with my focus.”

They’d describe weeks of flow state followed by sudden, inexplicable dread. The loss of taste for problems they used to love. A creeping sense that their accomplishments were fraudulent or, worse, meaningless- but only in flashes, late at night, gone by morning standup.

I didn’t have language for this. The burnout literature talked about exhaustion, cynicism, inefficacy. These people weren’t exhausted. They were precise. They weren’t cynical. They were committed, sometimes desperately so.

What they were was disconnected from themselves while performing connection to their work perfectly.

The system that rewards the wrong signals

Here’s what I see in tech specifically. Your performance metrics- ship velocity, bug resolution, hours of focus- are terrible proxies for sustainable capacity. Worse, they’re inversely correlated with the self-awareness that would protect your best people.

The founder who notices her anxiety rising at 2pm and takes a walk? The engineer who recognizes he’s solving problems mechanically, without real engagement, and asks to rotate projects? That’s a “motivation problem” in many cultures.

Meanwhile, the person who ignores the signal, pushes through, ships at 3am? Hero. Promotion track. More equity.

I’ve watched companies install meditation apps, hire “wellness coaches,” roll out resilience training- and keep rewarding the exact behavior that makes those tools necessary. It’s not hypocrisy, exactly. It’s a failure to see that individual coping strategies don’t fix collective extraction.

Your high-performer doesn’t look burned out because they’ve learned to metabolize unsustainable demands into identity. I’m the person who figures it out. I’m the one who doesn’t quit. The work needs me. This isn’t vanity. It’s often genuine care, misdirected until it becomes self-erasure.

What actually shows up in session

I can’t give you case studies, but I can tell you patterns. The 10x engineer who hasn’t felt curiosity about a problem in six months but can’t admit it because what else would he be? The founder who wakes up at 4am with solutions- not because she’s inspired, but because her nervous system won’t let her rest until the threat is neutralized. The “culture carrier” everyone leans on, who has stopped leaning back because there’s no one there, and anyway, they’re supposed to be the strong one.

They don’t say “I’m burned out.” They say:

• “I think I need a different challenge” (meaning: this one has consumed me)
• “I’m having trouble prioritizing” (meaning: everything feels equally urgent because my threat detection is broken)
• “I should probably exercise more” (meaning: I know something is wrong but I’m trying to solve it with the same optimization mindset that caused it)

The tragedy is they often leave before anyone understands what happened. They join another startup, or start one, carrying the same pattern. Or they stay, performing brilliantly, while something essential quietly leaves first.

What leadership actually owes them

Not more resilience training. Not “permission” to take vacation they won’t actually take because the backlog terrifies them. Not check-ins that ask “how are you” when the real message is “please keep performing.”

What I’ve seen work, in the rare companies that try:

Real load reduction, not permission to rest. The engineer who’s been carrying critical infrastructure needs someone else to actually own pieces of it- not just “support”- before she can recover. This costs. It takes longer than installing an app. It requires believing her work is valuable enough to protect her capacity for.

Naming the pattern without shame. When a leader can say, publicly, “I pushed through illness to ship that feature and that was a failure of judgment, not a success of will”- it gives language to what high-performers privately suspect. That their model is broken.

Separating identity from output- structurally. Not as a wellness slogan. As practice. When someone’s value to the team is explicitly discussed in terms beyond their recent commits, it loosens the knot that ties self-worth to productivity.

Protecting the people who protect others. Your “culture carriers” need their own support system, and they need it without becoming the organization’s unofficial therapist. I’ve seen companies lose their best people because they were too good at making everyone else feel okay.

What I still don’t know

I can’t tell you with certainty who recovers and who doesn’t. Some high-performers leave, build slower lives, and find they don’t recognize themselves without the intensity. Others stay, change companies or roles, and slowly rebuild a relationship with work that includes them in it.

What I do know: the ones who heal fastest had someone notice before they crashed. Not a diagnosis. Just a real conversation that acknowledged the gap between how they seemed and how they felt. The relief in those sessions is palpable. You see it, they say. No one sees it.

They’re wrong, usually. Someone almost always sees it. What they mean is: no one named it. No one made it safe enough to be seen in.

That’s the work. Not preventing burnout- though that would be nice- but recognizing the forms it takes when your best people are too skilled to show it.