What leaving tech actually did to my sense of self — two years later

One year out, I wrote nothing about this. There were things I could have said but they were still in flux — still too close, still potentially just the story of a hard year rather than anything that would hold up to examination at a distance. Two years out, things have settled enough that I can say something more honest: including the parts that are genuinely better, the parts that turned out differently from what I expected, and the parts I'm still working out.

The short version is that leaving tech did something to my sense of self that I hadn't fully anticipated and that took longer to process than almost anything else in the transition. Not the practical parts — those were difficult but navigable. The identity part was different. It was slower, stranger, and in some ways the most significant thing that has happened to me professionally in the past decade.

What the identity had been built on

I'd been in tech for eleven years. By the end, I was a senior engineer at a company with enough name recognition that saying the name at a dinner party changed the texture of the conversation. I worked on systems with genuine scale. I had a team I respected, compensation that represented years of compounded negotiation, and a professional context that had become the primary frame through which I understood myself. From outside, that looked like success. From inside, it also looked like success — which was most of the problem.

What I hadn't fully understood until I left was how much of my sense of self had been constructed from the scaffolding that came with the job. Not just the title, though the title mattered more than I wanted to admit. The organisation's name, which opened conversations and doors. The team, which gave me a peer group and a daily social structure. The problems, which gave me something to direct my thinking toward and which produced the specific satisfaction of solving difficult things in public, with people watching. The competence — the daily experience of being someone who was good at something specific, in an environment that confirmed it continuously.

None of this requires loving the job to function. I hadn't loved it in years. But the scaffolding provides the frame for a sense of self even when the content has become hollow. And removing the frame, it turns out, is a different kind of experience from simply leaving a job you didn't love.

Year one: what the disorientation actually felt like

The first year was mostly about adjusting to the absence. The absence of structure arrived first — the removal of the external scaffolding that had organised my time and told me, through meetings and deliverables and performance cycles, what I was supposed to be doing and whether I was doing it well. Without it, the question of what to do with any given day was suddenly and unexpectedly mine to answer, and I found I had less of an answer than I expected.

The second thing that happened, which I'd read about and still wasn't prepared for, was the identity question in social situations. In tech, the identity questions had been answered by the environment. You were an engineer, or a PM, or a manager. You worked at a company with a certain status. You were working on a product of a certain kind. These were not deep truths about who you were — but they were functional answers that let you move through social situations without having to excavate what was underneath them.

Without them, the situations became unexpectedly difficult. "What do you do?" — a question I'd answered automatically for a decade — became a question I genuinely didn't know how to answer. I wasn't unemployed. I wasn't between jobs exactly. I was figuring something out, which is an accurate description and a terrible conversation-starter, and which the people asking the question visibly didn't know what to do with any more than I did.

The disorientation of year one had a quality I can now describe but couldn't at the time: it was the feeling of having been a character in someone else's story for long enough that stopping the story didn't clarify who you were — it just left a space where the story had been. Filling that space with something genuine rather than something merely adjacent to the old structure took longer than I thought it would.

What shifted between year one and year two

The clearest way I can describe the difference is this: in year one, I was still defined primarily by what I had left. The internal conversation was mostly about the gap between who I had been and who I was now. The metric I kept applying was loss — what the identity used to contain that it didn't contain anymore. Year two stopped feeling like that. Not overnight, and not all at once, but gradually the internal conversation shifted from what was gone to what was actually here.

Part of what drove this shift was the emergence of new reference points. Some were professional — the work I was doing that was different from engineering, the skills that turned out to transfer in directions I hadn't expected, the early signs of competence in new domains that eventually started producing their own quiet confirmation that I was still someone who could do things. These came more slowly than I wanted and could not be hurried. The patience required for the period when the new competence was genuinely absent — when I was actually a beginner at things I'd never done before, with no performance review to tell me I was progressing — was the most uncomfortable sustained experience of the two years.

But some of the new reference points were more personal and less obviously achievement-related. Relationships that had been backgrounded by the demands of the job came forward. Time that had previously been colonised by work became available for things that turned out to matter in ways I hadn't had the bandwidth to notice. The physical recovery from burnout — which was still underway through most of year one — eventually produced a version of myself that had access to a wider range of experience than I'd had at the end of the tech career. I'd been narrowed. The narrowing was so gradual I hadn't noticed it happening. Year two was the first time I noticed how much wider my own life had become.

What tech had done to my sense of self that I only noticed when it stopped

This is the part that surprised me most, and that I think is underexplored in most accounts of leaving. I expected to miss the competence, the structure, the financial certainty. I expected the identity dislocation. What I didn't expect was to notice, slowly across year two, all the things that tech had been doing to my sense of self that I'd never consciously registered as costs.

The comparison culture that runs through tech work — the performance review frameworks, the levelling systems, the always-visible hierarchies of technical credibility, the LinkedIn feeds showing what everyone you've ever worked with is doing and where they are now — produces a specific kind of internal noise that I only noticed when it stopped. In tech environments, there's always a clearer version of you visible somewhere nearby: a colleague who moves faster, a team that ships more, a company that has solved the problem you're struggling with in ways that make your struggle look avoidable. Living in that environment long enough normalises the comparison, and you stop noticing the hum of it running underneath everything else.

Outside tech, the hum stopped. The silence was disorienting at first — I'd lost a reference point, even a painful one. But what replaced the noise, eventually, was something that felt more like a genuine relationship with my own work. The things I was doing were interesting or not on their own terms, not relative to what someone else was doing faster and better. That shift — from comparative to intrinsic as the basis for evaluating my own output — was one of the most significant changes of year two, and I had not known to expect it or to want it.

What's still not back, and may not come back

Two years in, I want to be honest about what hasn't returned. The financial ease of a senior tech salary — the casual relationship with expense that you don't notice until it's gone — has not returned. I've made different financial choices and built a different relationship with the numbers, but the easiness isn't there. Some things required that income level and I either manage them differently now or don't manage them at all. This is a real cost and it's worth naming, because accounts of leaving tech that leave it out are doing the reader a disservice.

The professional certainty is also not fully back. In tech, I knew what good looked like in my domain. I knew how to evaluate my own work relative to others doing similar things. I knew, with reasonable confidence, where I sat in the relevant field. Two years into something different, those calibrations are still forming. I have views about my own output. I don't have the confidence in those views that comes from a decade of doing one thing in one industry. This is appropriate — you don't earn that confidence in two years — but it is sometimes uncomfortable in ways that the clarity of technical expertise wasn't.

What the self actually looks like now

Smaller, in some respects. Less professionally armoured. Without the scaffolding of an organisation's name and a senior title, the social performance I used to give automatically — the version of myself that the job produced on cue — doesn't show up in the same way. Whether this is loss or relief depends considerably on the day.

Quieter. The constant stimulation of the tech environment — the meetings, the decisions, the urgency, even the friction — had been providing a kind of activation that I didn't know I'd miss. Its absence felt, in year one, like a kind of poverty. By year two, the quiet had become something more like spaciousness. There's more room to be more things, which takes some getting used to when you've been one thing specifically for a decade.

More genuinely curious than I was at the end of the tech career. This is the thing I return to most when I'm asked about the two years. I had assumed that the loss of intellectual engagement with technical problems would be a permanent subtraction — that the curiosity that had driven the early career would be somehow tied to the domain that had housed it. What I find instead, two years out, is a quality of engagement with the things that actually interest me that I hadn't had access to for the final years of the job. The burnout had narrowed not just my capacity but my range. What's come back — slowly, on its own schedule, in directions I didn't predict — is a version of curiosity that feels more genuinely mine than the version I was performing at the end.

The piece on figuring out what you actually want is the one I'd have found most useful in year one, when the question felt enormous and the tools for answering it felt entirely absent. The account of having everything the job promised and feeling nothing captures something about why leaving felt necessary that I still find myself returning to. And the loneliness of being the only one in your circle who wants out is about the social cost of this kind of decision — a cost that two years of perspective has softened but not entirely resolved.