I had everything the job promised. So why did I feel nothing?

I want to get the setup right, because it's easy to misread this story, and the misreading is its own kind of loneliness.

I wasn't in a toxic workplace. My manager was reasonable, my team was talented. I had hit the milestones I'd aimed at. I was, by any external measure, thriving. And I felt, consistently and increasingly, almost nothing. Not unhappy exactly — something harder to name than that. A flatness where the feeling should have been. A going-through-the-motions quality to days that I knew should have felt significant and didn't.

The thing that made it hardest to talk about was the absence of a legitimate complaint. You can't exactly go to a therapist and say "I have everything the job promised and I feel nothing" and expect that to land as a crisis, because it doesn't look like one. It looks, from the outside, like a success story that needs a bit of gratitude work.

But it wasn't a gratitude problem. And I think a lot of people in tech are quietly living this same thing and not saying it out loud, for exactly the same reason.

What success was supposed to feel like

There's an implicit promise embedded in how tech careers work. It goes something like: develop your skills, demonstrate your value, progress through the levels, reach the compensation band you've been targeting — and at that point something will resolve. The effort will have paid off. You'll feel, in yourself, that it was worth it.

Nobody states this promise explicitly. It doesn't need to be stated. It's structural. It's in the logic of the performance review, in the way progression is talked about, in the whole framing of levels and bands and the next thing to be earning your way toward. The system implies a destination at which arrival feels like arrival.

I arrived. The resolution didn't come.

What happened instead, each time I hit a target, was about three days of something that might generously be called satisfaction before the horizon moved and the familiar state reasserted itself. Staff engineer: brief, clean satisfaction, then a new set of pressures and a new level I wasn't yet at. A good equity event: a weekend of relief, then back to roughly the same internal weather. The milestones were real. The feeling I'd expected them to produce either wasn't there, or was there so briefly that it barely registered as a feeling at all.

I kept assuming this meant I needed the next one. That the resolution would come when I reached the level above the current one. That I was just not quite there yet. It took longer than I'd like to admit to consider the possibility that no level was going to produce what I was looking for, because what I was looking for wasn't available at any level.

Why I didn't pay attention to this sooner

High-performing people are, in my experience, unusually skilled at overriding inconvenient internal signals. Not because they're incapable of introspection — often the opposite — but because the same cognitive habits that make them effective professionally make them effective at explaining away things they don't want to examine.

Feeling like something is wrong but unable to name what? That's probably imposter syndrome, which has a name and a known treatment, which is to keep going until you feel like you belong. A low-grade sense that the work doesn't matter as much as it's supposed to? Reframe that as perspective — everyone feels this sometimes, it doesn't mean anything. A suspicion that the life you're building doesn't quite feel like yours? That's the adjustment period. Give it time. You'll grow into it.

The rationalisation machine is fast and sophisticated and it had been running, in my case, for years. I was good enough at reframing that I didn't notice how much I was doing it, or what I was doing it to.

There was something else, too. The absence of a legitimate complaint made the feeling harder to sit with honestly. I wasn't suffering in any way I could point to. Which meant that taking the feeling seriously required giving it weight that the external situation seemed to argue against. It felt like ingratitude. It felt like a problem I should be able to think my way out of. The possibility that it was neither of those things — that it was accurate information about something real — took a long time to consider.

The moment I couldn't keep explaining it away

For me it was a conversation at a company offsite — the kind of structured discussion about five-year goals that produces the right-sounding answers almost automatically. I gave mine. Forward-looking, technically accurate, entirely hollow. Not hollow to the room. Hollow to me.

On the drive back I sat with the fact that I had just described a future I felt genuinely indifferent to. Not opposed to. Not excited about. Indifferent. And I realised, with a clarity that was uncomfortable in its precision, that I had been giving some version of that answer for years — describing a trajectory I was on without ever quite asking whether I wanted to be on it.

Then came the harder thing: if I was indifferent to where I was going, what direction would I not be indifferent to? And I didn't have a good answer. Not a vague one. Not any answer at all. I had spent so long optimising for a particular set of outcomes that I had lost, somewhere in the process, the capacity to register what I actually wanted as something distinct from what I had been aiming at.

What the emptiness was actually telling me

The way I eventually came to understand it was this: the flatness wasn't malfunction. It was the system registering, in the only way available to it, that the thing I was chasing and the thing I actually wanted were not the same thing — and had possibly never been the same thing.

Tech careers select for a specific kind of ambition early. They reward people who want progression, who want recognition, who find meaning in building technical things at scale. And there are people for whom that ambition is genuinely theirs — for whom the work itself is the thing, not just the path to something else. But there are also people who learned to want what the environment rewarded, who performed the ambition convincingly enough that eventually they couldn't tell the performance from the real thing.

I think I was the second kind. The flatness was the gap between the performed version of what I wanted and whatever was underneath it — muted by years of not being attended to, not dead, just very quiet.

What I don't want to do with this

I don't want to wrap this up. I don't want to tell you what I did next and how it resolved, because for most people in this situation nothing resolves quickly or cleanly — and the story of someone who figured it out and is now doing the meaningful thing can be its own kind of alienating. Another destination to fail to arrive at. Another version of yourself you're not yet.

What I want to say instead is simpler: if you are in this, the feeling is not ingratitude. It's not a sign that you're broken or that you need to recalibrate your attitude or that you should be more present and appreciative of what you have. It is accurate information. Something is off — not catastrophically, not irreparably, but genuinely. And that information, taken seriously rather than managed, is the beginning of something real.

You don't need to know yet what it's the beginning of. That's the part that takes time. What you can do right now is stop explaining the feeling away, stop treating it as a symptom to be treated, and start treating it as something worth listening to.

That's it. That's enough for now.

If you're sitting with this and trying to figure out what it means, the identity track on the Start Here page has more writing on it — not answers, but honest company for the question.