When Staying Becomes the Betrayal
On the unwritten contract between leaders and the engineers who trust them.
The Quiet Part
There’s a moment, and it’s never the one you expect, where you realise you’re going to leave. It doesn’t come during a heated argument or a bad quarter. It comes on a Tuesday afternoon, mid-sentence in a meeting, when someone says something and you feel nothing. No pushback. No frustration. Not even the energy to disagree. Just a flat recognition that the gap between what you believe and what you’re being asked to do has gotten too wide to bridge.
I’ve led engineering organisations for over fifteen years. I’ve weathered bad quarters and difficult reorgs, strategies I didn’t love, people decisions that kept me up at night. That’s part of the job. You don’t leave because things are hard, you stay because the hard things are worth doing. Because you believe the direction is right even when the path is rough.
But what do you do when you stop believing?
What Alignment Actually Means
I want to be precise about this, because alignment gets thrown around a lot in leadership circles and it’s worth defining what I mean.
Alignment is not agreement. I’ve disagreed with my manager and my peers. That’s healthy. If you’re surrounded by people who agree with you on everything, you have a different problem. Disagreement on strategy, on timelines and/or on sequencing is the normal friction of building something complex. You argue, you commit, you move forward.
Alignment breaks somewhere deeper. It breaks when the values shift. When the way a company thinks about its product and its people changes in a way you can’t reconcile with your own principles. It’s not about a single decision. It’s about a pattern. The company you joined, the one whose mission made you show up early and stay late, starts making choices that feel wrong. The company stops caring about building a great product. Engineering judgment, the kind that says “we can build this, but we shouldn’t build it like that,” starts getting treated as an obstacle rather than a contribution. Requirements become mandates. Timelines become deadlines with no negotiation. And the question “is this the right thing to do?” is replaced by “when will it be done?”. And then, people stop raising their voice. No one challenges or questions anymore.
That’s not misalignment on tactics. That’s a fundamental divergence in what the company values are.
The Invisible Cost of Ignoring Engineering Judgment
Here’s something that’s always bothered me. If a civil engineer tells you a bridge can’t support a certain load, nobody asks them to prove their calculus. The conversation is over. The load gets reduced or the design changes. There’s a respect for professional judgment that’s built into how we treat physical engineering.
Software engineering doesn’t get that. And I think I understand why: the consequences are invisible. A bridge built wrong collapses. A system built wrong degrades slowly. It accumulates operational burden, creates on-call nightmares, becomes the thing every new hire is warned about. The organisational scar tissue builds up over months and years, and by the time anyone outside engineering notices, the cost is already enormous.
So when a senior engineer or an EM says “yes, it’s technically possible, but the cost of building and maintaining it this way would be irresponsible,” that gets heard as “they’re being difficult.” Because the thing can be done. “Technically possible” is all some stakeholders need to hear. Feasibility isn’t binary, the real cost isn’t just in the initial build but in the years of maintenance, the operational overhead, the cognitive load spread across the entire organisation gets lost. Or worse, it gets dismissed.
The Contract
This is the part that made leaving inevitable.
When you lead engineers, they trust you and you have a contract with them. It’s unwritten, but it’s real, and if you’ve ever been on either side of it you know exactly what I’m talking about. You represent their craft upstream. When a business decision will compromise the quality of what they build, you push back. When timelines are unrealistic, you say so. You make sure the cost of shortcuts is understood before anyone commits to them. You protect their ability to do work they can be proud of. That’s what professional leadership looks like in any discipline.
And in return, they trust you. They follow your judgment. They take on hard problems because you’ve told them it matters, and they stretch beyond what’s comfortable because they believe you wouldn’t ask if it wasn’t worth it.
The moment you can no longer honor that contract, when you’re asked to push decisions downstream that you know are wrong, when the requirements you’re told to deliver make you uncomfortable, that’s when staying becomes the betrayal.
I thought about this a lot before I made my decision. Could I compartmentalise? Just execute, disagree privately, let the results speak for themselves? Maybe some leaders can. I couldn’t. Maybe I was wrong. You always have to ask yourself that question honestly. But then I’d talk to my engineers, hear the frustration in their voices when describing what they were being asked to build, and I’d know. This wasn’t me being inflexible. This was the organisation losing something it shouldn’t have lost.
I wasn’t willing to spend my credibility pretending otherwise.
Leaving
People assume leaving is the hard part. It’s not. By the time you actually resign, the decision has been made for weeks, sometimes months. The hard part is everything before it. The part where you’re still trying. Where you show up to meetings hoping something has changed, that someone will say the thing that makes it make sense again. The part where you wonder if you’re overreacting, or if your standards are too high, or if this is just what companies do when they scale.
I didn’t leave angry, and I didn’t leave with a desire to burn anything down. I left disappointed because the job was not done, because I still believe that products should be built with care, that engineering judgment is an asset, that you owe the people you lead honesty about what you’re asking them to do and why.
Those beliefs aren’t going to bend. And the company’s direction isn’t going to change because I want it to. At some point, you have to accept that the paths have diverged and no amount of influence will bring them back together.
So you go.
Author Notes
This is my first piece on this Substack, and it felt right to start here, with the thing that set this in motion.
I’m writing this Substack because, after fifteen years of leading engineering organisations, I’ve accumulated a set of convictions about how to build products and lead teams that I want to put somewhere permanent. Somewhere that doesn’t depend on an employer’s direction or a company’s appetite for honesty. I’ve spent my career thinking about engineering leadership, org design, the craft of software, and the messy human problems that sit underneath all of it. That’s what you’ll find here.
I’m still in the arena. Still building. Still leading. Just from a place where the principles aren’t negotiable.