I downshifted from senior engineer to junior at a different company — no regrets

The question I get most often when I tell people what I did is: "Weren't you embarrassed?" It's phrased more diplomatically than that — "Wasn't it hard on your ego?" or "How did you explain it to people?" — but that's the question underneath. And the honest answer is: less than I expected, and less than most people assume when they hear it.

What follows is the version I wish I'd found before I made the decision. Not a LinkedIn post. The actual account — including the financial reality, the social friction, the parts that went better than expected, and the one thing I genuinely got wrong.

What led to it

I'd been a senior engineer at a mid-sized company for five years. Not a spectacular career — a solid one. I shipped things. I mentored people. I was involved in hiring and architecture decisions and all the things that the title implies. I was also, by the time I left, thoroughly exhausted in a way that two weeks off hadn't fixed and wasn't going to fix.

I didn't want to burn out entirely. I'd watched colleagues do that — cycle through intense productivity, then collapse, then either leave the industry or return to the same conditions and repeat the whole process. I wanted to sidestep that cycle, and the more I thought about it, the more I felt that a significant part of what was depleting me wasn't the work itself but the level of responsibility and visibility that came with the level I was operating at.

Senior engineers carry a lot that isn't code. The stakeholder management. The political navigation. The expectation that you'll have opinions about everything and that your opinions will be defensible. The performance of confidence in technical decisions even when you're genuinely uncertain. The mentoring, which I'd found genuinely rewarding early on and found increasingly draining as my own reserves got lower. All of this, layered on top of actual technical work, had become more than I was managing well.

I wasn't looking to leave tech. I was looking to find a version of the work that didn't require me to operate at the level of output the senior title had come to represent. The most honest framing I had was: I want to go back to a version of this job where the primary thing I do is write code and get better at it, and where the decisions that keep me awake at night are technical problems, not organisational ones.

The financial reality

I'll be direct about this because most accounts gloss over it: the step-down cost me about $28,000 in annual compensation. Previous role: $165,000 total (base plus bonus target). New role: $137,000 base, no meaningful bonus structure. That's a real number and it had real implications for how I thought about savings, timelines, and what I could afford to not prioritise for a while.

The things that made it workable: I'd been saving at a reasonable rate for several years and had a financial cushion that meant the reduced income wasn't immediately threatening. My partner was working. Our fixed costs were lower than they would have been if we'd been optimising our lifestyle against the senior salary. None of these are facts everyone can rely on, and I want to be honest that the arithmetic worked out partly because of accumulated circumstances that not everyone has.

The things that made it easier psychologically: the new company had a clear and public compensation framework with defined progression. I knew exactly what the path back to my previous income level looked like, and the estimate was eighteen to twenty-four months if things went reasonably. It didn't feel like a permanent downgrade — it felt like a deliberate demotion with a visible route back up. That framing mattered a lot.

The social friction

This was the part I'd underestimated. Not from strangers — from people who knew my previous work and knew the industry well enough to understand what the move implied. The reaction divided roughly into three categories.

The first was concern, expressed as questions: was everything okay, had something gone wrong, was there something I wasn't saying. The assumption that a voluntary step back must be covering for an involuntary one — a performance issue, a difficult exit, something that the official story was papering over. I'd anticipated this and had a clear, honest answer ready: nothing went wrong, I chose this, here's why. Most people accepted it. A few clearly didn't, and I stopped worrying about those people relatively quickly.

The second was advice, often delivered with a gentle urgency: you should negotiate harder, you don't need to take a level cut, your skills are worth more than you're giving them credit for. This advice was well-intentioned and mostly irrelevant. I hadn't been unable to get a senior role elsewhere. I'd specifically chosen not to. That distinction took more repetition to communicate than I expected.

The third was quiet respect, usually from people who'd made unconventional choices themselves and understood what it meant to prioritise something other than the title. Those conversations were worth more than the others.

What the first three months actually felt like

The first week was disorienting in a way I hadn't anticipated. I was in meetings where I was clearly one of the less experienced people in the room. I was asking questions that I would previously have been expected to answer. I was navigating a codebase I didn't understand and working at a pace that felt slower than I was used to. All of this was, objectively, the point — and all of it felt strange.

By month two, something had shifted. I was learning again in the way I'd learned at the beginning of my career — the specific texture of encountering a system you don't understand and having to figure it out. I'd forgotten that this feeling was enjoyable. I'd spent years in a role where being expected to already know things had, gradually and without my noticing, made me anxious about the things I didn't know. At the new level, not knowing things was simply the expected state. The permission to be learning rather than already knowing turned out to be something I'd needed more urgently than I'd understood.

Month three: I was starting to feel the shape of the team, understand the architecture, have opinions about things. The pace had picked up. I was contributing more meaningfully. And I was, measurably, less depleted than I'd been in the last two years of the previous role. Not completely rested — the burnout wasn't fully resolved yet — but heading in the right direction with less friction than before.

The unexpected gifts

I want to be honest about the things I gained that I hadn't anticipated, because these were the parts that surprised me most.

The first was access to mentorship. I'd been in positions where I was expected to be the one doing the mentoring for long enough that I'd stopped thinking of myself as someone who was being shaped by more experienced people. At the new level, I had senior engineers who were genuinely good at explaining their thinking, and I was in a position to actually absorb it. I learned more in the first six months of this role than I had in the preceding three years. That's a strong statement and I mean it.

The second was permission to be wrong. At the senior level, being wrong — about an architectural decision, about a technical approach, about a timeline estimate — carried a weight that accumulated over time. You were the person who was supposed to know. At the mid-level, being wrong was simply part of learning. That shift was more relieving than I'd expected.

The third was getting the work back. The actual writing of code, the debugging, the problem-solving. These had been squeezed to the margins of the senior role by everything else the title required. Getting them back to the centre of my day was, after some adjustment, genuinely restorative in a way that nothing else had been.

The thing I got wrong

I assumed the step-down would be more clearly temporary in my own head than it turned out to be. Six months in, I found myself occasionally anxious about the title — not every day, not in a way that affected my work, but in a background way that suggested the decision hadn't been as fully internalised as I'd thought. I was more aware of my level in conversations, more conscious of what I wasn't being asked for, more prone to the slightly corrosive thought: people who were more junior than me five years ago are now senior to me here.

This is the emotional residue that nobody warned me about, and it's worth naming. The intellectual case for the decision is sound. The lived experience of having voluntarily reduced your status in an industry that cares a lot about status is something you have to process, and it takes longer than the intellectual acceptance does. Therapy helped. Being honest with myself about when I was comparing rather than assessing helped. And eventually — probably around month eight — the background noise mostly stopped.

Whether it's the right move for you

The decision to step back in level is appropriate in a narrower set of circumstances than the burnout discourse sometimes implies. It's most likely to help if the load you're carrying is significantly driven by the responsibilities that come with your current level — the visibility, the expectation to have answers, the organisational overhead. If what's burning you out is the work itself, the culture, the management, or something more structural, a level change alone won't fix it.

It also requires a certain honesty about your own resilience. The social friction is real. The financial cost is real. The ego cost, even if smaller than you expect, is real. Going in with a clear sense of what you're trading and what you expect to get for it makes the period of adjustment considerably more manageable than going in hoping it will feel clean and finding that it's more complicated than that.

For me, it was the right call. The path back up is clearer than I expected, the learning has been genuinely valuable, and the person who went into that new role has come out of it considerably more functional than the one who left the previous one. That's not nothing. In fact, it's most of what I needed.

If you're trying to figure out what the right shape of a career change looks like for you, the 10 careers tech professionals actually transition into article is a broader look at what's available — including options that don't involve staying in engineering at all.