Job Hopping: How to Read Short Tenures Without Guessing

A short tenure is a fact; job hopping is a story someone tells about it. The first is observable, the second is a guess about the person's reliability, and the guess is often wrong. Treat short stints as a question about a pattern, not a verdict. One brief role has many ordinary causes. Several brief roles in a row, with no clear reason, deserve a question. Whether it matters at all depends on how long the role takes to pay off.

This post covers how to tell a pattern from a coincidence, which roles care about tenure, and what to ask.

Ordinary reasons for short stints

Before reading anything into the dates, remember how many causes are neutral.

• Layoffs, restructuring and company closures.
• Contract, temp and fixed-term roles that were short by design.
• Agency work, where each placement is a new client.
• Acquisitions that changed the job or the team.
• A role that was misrepresented when the candidate joined.
• A manager, culture or safety problem.
• Relocation, visa timing or caring responsibilities.
• A planned career change.

An inference from the dates alone mixes all of these together. The resume rarely tells you which one it was, and a candidate may not wish to say.

What counts as a pattern

One short role in a career of otherwise stable ones is noise. A pattern shows up in the shape of the whole history.

The dates matter less than the content of each role. A candidate who left after eight months with a concrete project shipped is a different case from one who left after eight months with nothing to show.

When tenure matters

For some roles, stability is part of the job.

• Long sales cycles, where results show after 12 months or more.
• Complex internal systems that take time to learn.
• Client-facing roles built on a relationship.
• Positions with expensive training.

For these, put tenure on the scorecard with the reason, for example "has stayed through at least one full sales cycle", rather than keeping it as a gut reaction. For roles with a short ramp, such as high-turnover support or seasonal work, tenure carries much less weight, and treating it as a requirement filters out many good candidates. See the sales screening guide for an example of reading tenure through a full cycle.

Questions that work

Ask in a screening call, and ask everyone the same way. See phone screen questions.

1. "What were you hired to do at X, and what did you deliver?"
2. "What made you move on?" Listen for coherence, not a particular reason.
3. "What would make you stay in a role for several years?" This gives you something to check against the real job.
4. "Which role have you been proudest of, and why?"

Stories that name specific work and a clear reason are normal. Stories with no specifics, or ones that contradict the resume, are the part to note.

Avoid these shortcuts

• A fixed average-tenure cutoff, such as "must average two years". It penalises early-career people, contractors and anyone affected by layoffs.
• Treating loyalty as the main virtue. Staying a long time can mean growth or can mean inertia.
• Assuming gender, age or family status explains a pattern, which is both wrong and risky.

If a tool applies a tenure rule automatically, check what it does. A tool that flags a variance for a person to read is safer than one that lowers a score silently. See AI bias in hiring, and the related topic of employment gaps.

Recording your reasoning

If tenure influenced a decision, write down which requirement it related to and what you asked. "Four roles under 18 months in 5 years; asked; two were fixed-term and two were redundancies; no concern" is a clear and fair record. The same discipline helps the resume screening checklist stay consistent across reviewers.

A worked timeline

Here is a hypothetical timeline for a marketing manager over eight years: 14 months at an agency, 9 months at a startup that closed, 11 months at a software company during a restructure, then 3 years at a current employer.

Read it by shape. Two of the three short roles ended for reasons outside the candidate's control, and the long one at the end shows what they do when the conditions are stable. A fixed rule such as "average tenure under two years" would flag the candidate. A fair reading sees a market-driven run followed by a stable period and moves on to the work. The question for the call is not "why did you leave so often?" but "what did you ship at each place, and what would you want from the next one?"

Compare a second timeline: six roles in six years, each ten months, each with a different title at a similar level and no stated projects. Here the pattern is real and the content is thin. A call can find out whether this is a string of poor fits or something the person tends to repeat, and what changed.

Do the arithmetic on your own turnover first

If people leave your company quickly, short tenures in candidates may reflect the market you both share. Look at how long recent hires in the role have stayed before setting a bar for applicants. Holding candidates to a standard your own team does not meet creates a filter that fails everyone.