Five signals it is time to look for a new engineering role

Most engineers we talk to wait too long to leave their job. Not because they love it. Because leaving is hard, and the brain is excellent at framing every uncomfortable signal as something temporary, something fixable, something to revisit in another six months.

Then another six months pass.

After fifteen years of recruiting, we have had this conversation enough times to recognize the shape of it. There is a real difference between a rough quarter at work and a structural sign that you have outgrown your current role. This is a guide to telling the two apart, written for senior engineers who suspect it might be time but are not sure.

The data backs up the gut feel. Stack Overflow’s 2024 Developer Survey found that fewer than one in five professional developers describe themselves as happy in their current role, with about half characterizing themselves as complacent. Bureau of Labor Statistics tenure data shows median US tenure across all workers sits around 3.9 to 4.2 years, and analysis published on the Stack Overflow blog puts engineer tenure at roughly half of that at large tech companies. Translation: a senior engineer asking themselves whether it is time to look is having a normal, common thought. The question is whether the signals justify acting on it.

If you read all five signals and recognize one or two of yourself, that is normal. Every job has friction. If you recognize three or more, the conversation is no longer about whether to look. It is about how to do it well.

Signal one: you are no longer learning

The strongest engineers we know describe their best years as ones where they ended the year noticeably better at the craft than they started. That can mean different things at different stages. Earlier in the career, it usually means new technical depth. Later, it usually means new leverage: leading larger initiatives, mentoring more people, owning ambiguous problems, or shipping things you previously could not have shipped.

What it does not mean is repetition. If you can describe last year and the year before with the same words, the role is no longer producing growth. That is not a moral failing of the job. It just means you have extracted what was there to extract, and continuing to stay puts the next phase of your career on hold.

A useful test is to ask yourself: if I were interviewing for a senior role at another company today, what would I have to talk about that I could not have talked about eighteen months ago. If the honest answer is “not much,” the signal is real. Korn Ferry’s research on voluntary turnover places boredom and the lack of new challenges among the most common reasons employees leave, second only to compensation. Engineers in particular are sensitive to it.

Signal two: your scope is shrinking

This one tends to creep up gradually, which is why it is dangerous.

When you started, you owned a meaningful surface area. Maybe a service, a feature, a technical direction. Over time, things have happened. A reorg, a new hire, a leadership change. The scope you used to own got split, or absorbed, or quietly handed to someone else. You are still senior on paper, but the actual work you do today is narrower than it was two years ago.

Sometimes this is fine. There are good reasons scope shifts. But more often, scope shrinkage is a leading indicator that the company has stopped investing in you the way it used to, even if nobody has said so out loud.

The way to verify is to look at the work coming up over the next two quarters. Do you see new ownership in your future, or do you see a slow tightening of what you can credibly say is yours. The roadmap usually tells the truth before the org chart does.

Signal three: the company stopped investing in the function

Sometimes the issue is not you. The whole engineering function is being deprioritized.

This shows up in specific ways. Headcount freezes that hit engineering disproportionately. Senior leaders leaving and not being replaced. Strategic projects that get repeatedly deferred. Decisions about technical direction being made by people who are not in engineering. A pattern of pushing back on infrastructure investment in favor of feature velocity that is itself slipping.

If you see two or three of those patterns in your company over a six-to-nine-month window, the signal is structural. It is not about your performance. It is about the company’s relationship with the engineering function. Strong engineers can absorb a lot of organizational dysfunction, but they tend to leave when the company stops believing in the work itself. The 2024 Stack Overflow survey reinforces this: developers consistently rank technical debt and frustrating tooling as their top sources of dissatisfaction, both of which compound when leadership stops investing in the function.

The harder version of this signal is when the company is doing well overall, but engineering is being treated as a cost center rather than the engine that builds the product. That dynamic, once entrenched, almost never reverses without a leadership change.

Signal four: you cannot point to a recent win

Strong engineers tend to have a running list, often informal, of things they shipped that they are proud of. The list updates over time. Old wins get crowded out by new ones. The recency of the most recent entry is itself a useful diagnostic.

If you sit down and try to write your top three wins from the last twelve months and the list is harder to fill than it should be, something has changed. Either the work is no longer producing wins of the size you used to ship, or wins are happening but you are no longer being credited with them, or the work is happening but it is not the kind of work that produces clean wins.

Each of those three has different implications. The first usually points to scope shrinkage. The second usually points to organizational politics. The third sometimes points to a healthy phase of work that is genuinely investment-heavy and harvest-light, but more often points to a role that has drifted from its original shape.

The point of this signal is not that every twelve months should produce a list of wins. The point is that the absence of recent wins is information. It is worth understanding why.

Signal five: you dread Mondays for more than a month

Every job has bad weeks. The signal here is the duration.

A bad week is a project gone sideways, a tough one-on-one, a deadline that slipped. Those resolve. A bad month, where Sunday afternoon starts to carry a small weight you did not used to feel, is a different category. A bad three months, where the weight is consistent and not tied to any specific issue, is a structural signal. Your nervous system is processing something your conscious mind has not finished articulating yet.

This is the most reliable of the five signals, in our experience, because it is the hardest to rationalize. The other signals can be argued away. This one cannot, because it is a feeling that persists across context.

The mistake people make with this signal is to wait for it to fix itself. It almost never does. The reasons it shows up tend to be cumulative, and the longer you stay with it unaddressed, the more it leaks into the rest of your life. If Monday morning has felt heavy for more than a month, treat that as data.

A simple way to place yourself

If you map your current role on two axes, growth (is the work expanding what you can do) and engagement (do you feel pulled to it on Monday morning), you usually land in one of four spots. The action depends on which one.

quadrantChart
  title Where is your current role?
  x-axis "Stagnant" --> "Growing"
  y-axis "Disengaged" --> "Engaged"
  quadrant-1 Stay, you are in flow
  quadrant-2 Diagnose disengagement
  quadrant-3 Time to leave
  quadrant-4 Raise scope internally
  Strong fit, ship mode: [0.82, 0.86]
  Engaged but stuck: [0.22, 0.78]
  Growing but checked out: [0.78, 0.22]
  Stagnant and dragging: [0.18, 0.18]

The most common failure mode we see is engineers parking themselves in the bottom-left quadrant for too long, hoping it will resolve. It rarely does. Sitting in that quadrant for more than a quarter or two is the structural signal that something has to change, even if you cannot yet articulate what.

How to validate the signals before you decide

Two or three of these signals showing up at once is enough to start a real conversation with yourself. It is not enough to make the decision unilaterally.

Before you do anything irreversible, run a few honest checks. Talk to two or three engineers you respect, ideally people who do not work at your current company, and describe what you are seeing without spinning it. Ask them what they hear. Their reaction will be informative independent of what they say.

Look at your last two performance cycles. Not the ratings, the substance. What was the manager investing in. What were the goals. What changed between cycles. The trajectory tells you whether the company sees you the way you want to be seen.

Consider the counterfactual. If a role at another company landed in your inbox tomorrow, materially better in two of the four dimensions you most care about (scope, team, comp, learning), how quickly would you take a call. If the answer is “immediately,” the signal is real, even before you do the search.

How to start looking without burning the current role

If you decide to look, the next set of mistakes are tactical. Two are common.

The first is talking yourself into burning the current role on the way out. The strongest move when you decide to look is to keep doing your current job well, ideally better than usual, while quietly running a search in parallel. Your reputation in the market is built on the trajectory of your most recent role, including the way you exit it.

The second is starting the search without preparation. Senior engineers who reach out to recruiters cold, without a clear story about what they want next, get filtered into roles that match their resume rather than their actual goals. Spend a weekend writing down, honestly, what you want the next role to give you that this one does not. The clarity translates directly into better conversations.

When you are ready, the right first step is usually two to three direct conversations with recruiters or trusted operators who know your space. Not a flood of applications. Not a public job-search announcement. A small number of high-context conversations that help you calibrate what is out there and what you actually want.

If you do that well, the next role finds you faster than you expect. And the version of you that lands in that next role is better off than the version that stayed too long.