The identity trap: why tech workers find it so hard to just stop and rest

There's a version of this story you've probably heard: someone burns out, the doctor signs them off, and they spend most of the leave on their laptop anyway. Not because their employer demanded it. Not because anything was urgent. Because stopping felt, in some way they couldn't quite explain, like not being there at all.

The obvious reading is that they're a workaholic who can't switch off. But there's a more precise reading, and it matters: they weren't working because they loved the work. They were working because without it, they didn't know who they were.

That's not a work problem. That's an identity problem that work has been quietly managing — and the leave just made it visible.

How the identity gets built

It starts early, usually. You were the kid who was good at the technical stuff — maths, logic, problem-solving — early enough that it became a story about you rather than just something you happened to be good at. That story followed you. It shaped what you pursued, who you spent time with, what you were proud of.

Tech rewards that story in every direction. Titles, compensation, the specific social currency of being the person who can do the hard thing. Over years, the feedback loop tightens. Your value — not just professionally, but personally — becomes synonymous with your output. With being capable. With being useful. The capability stops being something you have and starts being something you are.

Tech culture runs a particular version of this further than most. The mythology of total commitment — the engineer who sleeps at the office, the PM who replies at midnight, the founder whose entire self is the company — presents maximum investment not as an extreme but as an aspiration. You don't have to consciously choose it. It gets absorbed through the environment, through which behaviours get praised, through which stories get told with admiration.

What you end up with, often without quite intending it, is a self built almost entirely on doing. On forward motion. On the ongoing performance of competence — not performed for others, exactly, but performed for yourself. A continuous confirmation that you are still the person you think you are.

Why rest doesn't feel like rest

Here's the part that's hard to explain to someone who hasn't experienced it: when your identity is built on doing, rest is not neutral. It doesn't feel like a pause from the performance. It feels like an absence of self.

A product manager told me about the first extended break she'd taken in years. By day three she was anxious in a way she couldn't account for — not about anything specific, not about work falling apart, just at the fact of not doing anything. She kept picking up her phone to check things. Not because there was anything to check. Because the checking felt like existing.

That detail has stayed with me. The checking felt like existing. Because in the absence of productive activity, there was no other way she knew how to confirm she was still there. Still relevant. Still the person the story said she was.

This is why telling people in this situation to just disconnect doesn't work. Turning off notifications doesn't address the problem. The problem is not the notifications. The problem is that the identity has no off switch, because it was never built to need one.

What it actually feels like from inside it

There's a particular texture to being caught in this that's worth naming honestly, because it tends not to be recognised for what it is.

Rest feels like falling behind — even when there's nothing to fall behind on. Time not spent producing feels like time lost, though you couldn't name what it's being lost to. The absence of forward motion generates an unease that isn't proportionate to any actual external threat, because it isn't coming from outside.

Doing nothing feels morally wrong. Not just uncomfortable in a way you could tolerate — actually wrong, like you are failing at something, like idleness is a character defect that reflects badly on who you are. The word "unproductive" carries moral weight it has no business carrying, and you know that, and it carries the weight anyway.

Your mood tracks your output more closely than seems reasonable. A good work day and something close to fine. A low-output day and a gloom that arrives before you've consciously registered what kind of day it's been. The connection between what you produce and how you feel about yourself has become so tight that it functions as the primary axis of your emotional life.

And underneath all of it: the sense that you should be able to just relax, that other people seem to manage it, that there's something wrong with you for finding it this difficult. Which is its own particular cruelty, because there isn't something wrong with you. There's something wrong with the structure you've built — a structure that has no room in it for you when you're not performing.

The thing about this being different from ordinary overwork

Most people who are overworked want to stop but can't, because of external demands. The situation described here is different: the external demands have reduced, or disappeared entirely, and you still can't stop — because the compulsion to be productive isn't coming from the workload. It's coming from inside, from a self that has no stable ground outside its own performance.

I've heard this described in different ways by different people, but the same feeling runs through all the descriptions. A software engineer who'd been on sick leave for six weeks said: "At least when I was working I knew who I was and what I was for. Off work, I had no idea. I felt like I'd been unplugged." An engineering manager put it more bluntly: "I thought burnout leave was supposed to feel like relief. It felt like losing my personality."

These experiences don't fit the standard narrative about burnout, which is mostly a story about doing too much for too long. This is something more fundamental: the doing was also the being, and without it, neither is available.

I'm not going to tell you how to fix this

I want to resist the move that most articles like this make at this point — the pivot to solutions, the list of things to try, the reassurance that with the right practices you can rebuild a more resilient identity and emerge from this with a healthier relationship to work. I don't trust that narrative, and I don't think it serves you.

What I'll say instead is this: the disorientation you feel when you stop is not a symptom of something going wrong. It's the beginning of something going right — the first honest look at a structure that wasn't working, in the silence that becomes available when the thing that was filling it is finally gone.

That silence is uncomfortable. It's supposed to be uncomfortable. It's the sound of a question you've been too busy to ask, finally getting loud enough to hear.

You don't have to answer it immediately. You probably can't. What you can do is stop treating the discomfort as evidence that you should go back to what you were doing before. The discomfort is not the problem. The discomfort is the signal. What you do with that signal — slowly, imperfectly, without a clear endpoint — is the work that actually matters here.

The identity track on the Start Here page has more writing on this, from people who've been somewhere in the middle of it — not people with the answer, but people who sat with the question long enough to know something real about it.