The tech worker's guide to knowing when enough is enough

Let's start with what this is not.

It's not a quiz with a score that tells you when to quit. It's not a framework that removes the discomfort from the decision. There is no version of this guide that produces certainty, because you're making a judgment call about a complex situation under uncertainty, and any guide that promises to remove that uncertainty is lying to you.

What this is: a set of distinctions that help you tell the difference between discomforts that are survivable and situational, and the ones that are telling you something more fundamental about the fit between you and the situation you're in.

The difference between "hard" and "wrong"

The single most useful distinction, and the one most people find hardest to hold clearly, is this: hard is often temporary and situational. Wrong is structural.

Hard looks like a particularly demanding quarter, a difficult project, a team going through a rough patch. It has a clear source, a plausible endpoint, and a reasonable chance of being different on the other side. When you imagine the difficult thing resolving, the rest of the situation looks tolerable — even, in better moments, genuinely good.

Wrong looks like a mismatch between what the role fundamentally requires and what you have to give. A set of values or working styles in irreconcilable tension with the organisation's. A pattern of depletion that doesn't correlate with workload — that's present in quiet periods as much as busy ones. When you imagine the difficult thing resolving, the rest of the situation still looks wrong.

This distinction matters because the productivity industry and most management advice treats everything as the first kind of problem. The recommendation is always: reframe, try differently, build resilience. This advice is sound for problems of the first kind. For problems of the second kind, it is actively misleading — it produces effort in the wrong direction and delays the recognition of something that would benefit from a different response altogether.

The signals worth taking seriously

There are a handful of signals that, in the accounts people share most honestly, tend to indicate that the problem is structural rather than situational. None of them is definitive on its own. If several are present simultaneously, and have been for more than a few months, treat them as information rather than noise.

You've stopped believing things will improve. Not in a bad-week way — everyone has bad weeks and manages the cynicism that comes with them. But in a considered, clear-eyed way: you've genuinely stopped believing the situation has the capacity to become something you'd choose to stay in. When hope has fully left the picture, that's worth treating seriously. It's not the same as pessimism. It can coexist with high performance and continued professionalism. It's a quieter thing — a settled absence of expectation rather than an active complaint.

Your body is making decisions before your mind catches up. Chest tightness before Monday standups. The particular quality of dread on Sunday evenings that has graduated from vague to specific. Getting sick more often, or taking longer to recover than you used to. These aren't coincidences to manage or symptoms to suppress. They're your nervous system processing something your conscious mind hasn't fully admitted to itself yet. The body tends to be several months ahead of the thinking in these situations.

You've stopped being who you want to be at work. Not underperforming in a technical sense — many people in their final year at a job are still delivering adequately. But performing a version of yourself that has increasingly little to do with who you actually are: performing enthusiasm you don't feel, performing certainty in a direction you've privately questioned for a year, performing commitment to a culture whose values you've stopped believing in. The performance becomes more costly the longer it continues, and the gap between the performed self and the real one is one of the more reliable signals that something fundamental has shifted.

The people who know you best are seeing something you're trying to minimise. Partners, close friends, people who knew you before the job — if more than one of them is expressing concern in different ways, that pattern of external observation is data. Not because they necessarily understand the specifics of your work situation, but because they can see the version of you that comes home. And sometimes the version that comes home tells the truth about how things are, even when the version that goes to work is still managing the presentation.

The reasons people stay — and whether they hold up

The reasons people give for staying in roles that are making them unwell are almost universally framed as financial. The mortgage. The healthcare. The savings target five years away. The bonus that vests in eight months. These concerns are real. They're also, in most cases, based on numbers that haven't been checked recently against an honest accounting of the full cost — including the cost of staying.

The less-discussed reason people stay is identity. For many tech workers, the job title, the company name, the sense of being the person who builds something technically significant — that has become part of who they are. Leaving threatens not just the income but the self-description. Untangling your sense of yourself from the role you hold is the hardest part of this, and it's the part that standard career advice almost never addresses honestly. You cannot make a genuinely clear decision about whether to stay in a role if your sense of who you are is entangled with staying in it.

There is also, particularly in smaller companies and startup environments, a form of social obligation that keeps people longer than either finances or identity alone would. The team that depends on your specific knowledge. The project that would stall without you. The colleagues who have become friends. These are real, and they matter — and they are also, frequently, the mechanisms through which organisations extract effort they couldn't justify asking for through a formal employment contract. It's worth naming that honestly.

When the timing is never quite right — and what to do with that

The timing is almost always wrong. This is not a cynical observation — it's a structural feature of tech jobs in particular. There is always a critical product cycle, a bonus that vests in eight months, a reorg that's supposedly going to simplify everything. The conditions for a clean departure rarely assemble themselves without deliberate action. Waiting for a good moment is, in practice, a way of not deciding — which is itself a decision, with its own accumulating costs.

This is not an argument for impulsiveness. Financial preparation matters — having a clear sense of your runway, your non-negotiable expenses, what you'd need to feel stable during a transition. But "the timing isn't quite right" is worth interrogating specifically: what exactly would need to be different? Is that thing actually on track to happen? Is it within your control? And if it did happen, would it genuinely change your answer — or would it just surface the next reason the timing isn't right?

A lot of people who eventually leave describe a period of serial conditions: first I need to hit this milestone, then I need this amount saved, then I need to know what I'm going to do next. Each condition is reasonable on its own. The pattern is worth noticing.

What "enough is enough" actually feels like from the inside

People who've reached it describe it consistently, and the description is quieter than you might expect. Not a crisis or a dramatic moment of clarity. More like a settling — a point at which the internal argument about whether to stay or go simply stops producing new arguments. The decision feels less like a choice being made and more like a recognition of something that was already true.

What tends to precede that point, in most accounts, is a period of having genuinely tried. Tried to make it work. Tried to ask for what they needed. Tried to believe the next quarter would be different. The point of enough is usually not a first response — it's what's left after the alternatives have been genuinely attempted rather than theoretically dismissed.

If you're still in the trying phase, that's worth knowing too. It doesn't necessarily mean the decision isn't already made — sometimes the trying is more about gathering evidence for a conclusion you've already reached than about genuinely remaining open to staying. But it's worth being honest with yourself about which phase you're actually in, and what would have to happen for that to change.

The five questions framework is worth working through if you're in this territory — it's designed to cut through the noise rather than add to it. And if the practical side of the decision feels abstract and frightening, the runway thinking is the most useful place to make it concrete.