Job-Hopping Pattern

A simple explanation

A job-hopping pattern is what happens when the act of moving becomes the substitute for the slower work that staying would require. Each new role arrives with the same promise: this one is the right fit. Each role then runs the same predictable arc — ramp, fit, novelty peak, first friction, growing restlessness, exit. The deposit window — the point at which the work you put in starts paying back something durable — opens around the eighteen-to-twenty-four-month mark. The loop exits, reliably, just before.

This is not the same as changing jobs. People change jobs for good reasons all the time. The pattern is what shows up when changing jobs becomes the thing being done, on a cycle the body has learned to expect.

An everyday example

You are six months into the new role. The novelty has cleaned itself. The work is real. A couple of friction points have shown up — a colleague whose style grates, a stretch project that exposes a weakness, a manager whose feedback feels harder than the previous one's praise. By month nine, you are scrolling job listings on the train. By month twelve, you have had two informal coffees. By month fifteen, you have accepted the next thing. You tell the story as growth — the new role is more aligned, better comp, better team.

In your honest moments, you can already see the shape of how this next one will end. The arc has run six times. It has the same beats every time. And the part that was supposed to land — the depth, the mastery, the relational thickness — keeps not landing because you keep leaving at the point where landing would begin to be required.

Am I a job-hopper?

The question is not really about the resume. The CV is just a downstream artifact. The honest question is whether your exits are responses to specific, named problems with the current role, or whether they are responses to the predictable arrival of friction that follows the closing of novelty. The first is changing jobs. The second is the pattern.

A useful diagnostic: across your last three exits, name the precipitating issue for each. If the issues are genuinely different and genuinely external, you are changing jobs. If the issues cluster — the team became political, the work got repetitive, I outgrew the role — and they cluster around the same tenure window, the pattern is running.

The behavioral loop

A loop that runs cleanly because its exit point arrives before its cost becomes visible:

1. Arrival — the new role lands. The Reward System fires on novelty: new team, new stack, new problem domain. The first six weeks are the freshest window.
2. Ramp — you build context, learn the system, install relationships. The work is productive and the energy is high.
3. Fit signals — by month four to six, the role's shape becomes visible. You can do the work. You belong.
4. Novelty fade — somewhere between month six and ten, the novelty deposit closes. The Reward System's hits get smaller.
5. First friction — a difficulty appears. A colleague conflict, a project that exposes a real weakness, a manager whose evaluation feels harder than expected.
6. Threat verdict — the Threat System reads the friction as this role is not the one and begins running exit scenarios.
7. Justification — a story is assembled — comp, culture, growth, alignment — that makes the exit legible to others and to yourself.
8. Exit — the loop closes around month fifteen to twenty-four, just before the deposit window for depth and mastery would have opened.

Emotional drivers

Four feelings, often layered:

• A genuine love of beginnings, which the loop quietly recruits and over-uses.
• A sharp, often unnamed discomfort with the specific friction that arrives once novelty fades — the friction of being seen, evaluated, and asked to grow into something durable.
• A faint, accumulating self-distrust — I keep leaving — that is metabolised by the next arrival rather than examined.
• A diffuse grief, usually unseen, about the depth and craft that the pattern keeps starting and never finishes.

What your nervous system does

The Reward System's response to each new role is a clean dopamine cycle — high in the first weeks, tapering by month six. The Threat System, sensitised by prior exits, begins scanning for the friction it knows comes next. When the friction arrives — and it always does, in any role — the Threat System reads it as the signal to exit rather than the signal to grow.

Sleep through the early months of a new role is often unusually good — the body reads the change as progress. Sleep through the friction months is often poor — the body reads the friction as stuck-ness. The exit-and-arrive cycle becomes its own physiological rhythm, with the arrival lifting baseline and the friction lowering it. Over years, the system becomes increasingly intolerant of the friction months and increasingly hungry for the arrival lift, until the cycle is running on its own physiology rather than on the actual quality of the roles.

The DojoWell interpretation

The job-hopping pattern is a substituted density signature with unusual clarity. The Reward System was asked for meaningful progress; the substitute it supplied was novelty, which produces a real felt sense of moving forward while leaving the underlying deposit windows unopened. The Threat System was asked for safety; the substitute it supplied was exit, which produces a real felt sense of resolution while leaving the actual difficulty unmetabolised.

Both systems are doing what they were trained to do. The loop runs because the substitutes are convincing — I'm growing, this isn't a fit — and because the cost of the pattern is invisible at the level of any single move. Each individual job change can be defended. The pattern can only be seen across three or four cycles, when the deposit windows that were never opened start to add up to a career that is wide and not deep.

This is not an argument against changing jobs. Some jobs should be left. Some patterns are responses to genuinely bad environments. The pattern is the specific case where the changing has become the thing — where the loop exits at the point where the deposit would have begun, and where the substitution of movement for integration is being mistaken for growth.

The clean read is the deposit windows. Mastery, deep relational thickness, a body of work that compounds — these are deposits that open around the second and third year of any role. A pattern that exits before then is, almost by definition, asking movement to do work that staying would have done.

How do I stop job-hopping?

You do not stop by forcing yourself to stay. You stop by changing what you do when the friction months arrive.

Three moves, in order of difficulty:

1. Name the arc as you enter the next role. Write down, on day one, the dates at which you expect novelty to fade and friction to arrive. The naming is a small marker that, when the friction lands, reframes it as the expected beat of the loop rather than as new information about the role.
2. Stay one cycle past the exit point you would normally take. Not as endurance. As experiment. The deposit windows you have never seen will not become visible until you stay past them once.
3. Treat the first friction as the work. The thing that arrives at month nine — the colleague, the weakness, the harder feedback — is usually the actual training the role was offering. The loop exits to avoid it. Staying integrates it.

Practical steps

1. Map your last four exits on a single page. Date in, date out, the named reason, the actual underlying friction. Read across the rows. The pattern, if it exists, declares itself.
2. Distinguish a bad role from a friction month. Bad roles have specific, nameable structural problems. Friction months have generic patterns — boredom, a colleague, a harder feedback cycle. The first is a reason to leave. The second is the loop running.
3. Install one relational depth marker. A weekly conversation with a colleague that is not transactional. Depth at the relational layer is the most reliable way to stay past the loop's exit window.
4. Audit what you have never finished. A project, a craft progression, a relationship arc. The pattern shows up across domains. Naming the never-finished list outside work makes the pattern at work easier to see.
5. If you exit, exit cleanly. Write the actual reason — not the story for LinkedIn — in a private note. Re-read it during the first friction month of the next role. The note is data the next loop will try to ignore.

Reflection questions

• Across your last three exits, what was the actual friction underneath the named reason, and did the friction cluster around the same tenure window each time?
• Am I a job-hopper, given the texture of the last three roles rather than the resume?
• What deposit have you never collected because you have not stayed long enough to open the window?
• Where is movement substituting for integration in domains other than work?

Frequently Asked Questions