How to interview candidates with short tenures without filtering out good hires

A short tenure — a role held less than a year or two — is worth asking about directly, but it is a data point to investigate, not a reason to reject a candidate before you understand the context behind it. What predicts risk is not the length of any single stint; it is whether a pattern across several roles has a specific, verifiable, and varied set of reasons behind it, or the same vague complaint repeated every time. Below is how to separate a one-off from a pattern, neutral wording for asking about it, and a question bank with what a strong answer sounds like next to the red flags.

A short tenure is a data point, not a verdict

Treat one short stint on an otherwise stable resume the way you would treat any other single data point: worth a question, not worth a conclusion. People leave roles quickly for reasons that say nothing about their reliability — a manager who left within weeks of the candidate's start, a reorg that eliminated the role, a return-to-office mandate that broke a relocation agreement, a company that ran out of funding. None of these predict how the candidate will perform in your role. What deserves closer attention is a pattern: several short stints in a row, especially with vague or inconsistent explanations.

This also cuts the other way. A single long tenure does not automatically clear a candidate of risk either; someone who stayed five years in a role they had checked out of after year two is a different kind of concern the resume alone will never show. Tenure length, long or short, is a starting question, not a finished assessment.

Separate "one short stint" from "a pattern"

Look at the most recent three to four roles as a set before drawing any conclusion. A candidate with one eight-month role sandwiched between two three-year roles has a story, not a pattern. A candidate with four consecutive roles at eight, eleven, six and nine months has a pattern worth understanding in detail — which still might have a perfectly good explanation, but is worth more time at the screen than a single outlier would be.

When you do see a pattern, listen for whether the reasons vary or repeat. Varied, specific reasons across different stints (a layoff, then a relocation, then a role that was misrepresented at hiring) are more credible than the same generic complaint every time ("the culture wasn't a fit," "it wasn't what I expected," said about four different companies in four different industries).

Context that changes the read: layoffs, contracts, acquisitions

• Layoffs and reorgs. Verifiable through public news, LinkedIn activity from former coworkers at the same time, or a straightforward mention on the resume itself. Common enough in some periods and industries that it should not be treated as a candidate's failing.
• Contract or fixed-term roles. If the role was explicitly a 6-month contract, a "short tenure" completing it on schedule is not short at all, it is the role working as designed. Check whether the resume states the contract length.
• Acquisitions and mergers. A role that ended because the company was acquired and the position was eliminated or changed dramatically is a company event, not a candidate choice.
• Early-stage startups. Shorter average tenures are common in this segment for reasons ranging from funding failure to pivots that eliminate roles, independent of the individual's performance.
• Agency recruiting, consulting and similar fields. Some professions have shorter typical tenures built into how the work itself is structured, which is worth knowing before treating a candidate's history as unusual for their field.

Neutral wording for asking about it

Ask about the specific role and timeframe, not about the pattern as an accusation. The goal is information, and accusatory framing gets you a defensive, rehearsed answer instead of an honest one.

"Walk me through what led to the move after about [X months] at
[Company]."

"What was the role like when you joined versus when you left —
did anything change?"

"Looking at the last few roles together, is there a common thread
in what made you ready to move on each time?"

"What would need to be true here for this not to be another
eight-month stop?"

Avoid questions that frame the pattern as a character flaw ("why do you keep quitting," "can you actually commit to something") — these produce a defensive answer and tell you less than a neutral, specific question would.

Timing matters too. Raising the pattern for the first time at a final round, after the candidate has invested hours in your process, reads as an ambush. Ask about it at the screen, early and plainly, so the candidate has the same chance to explain it that they would have had if you had simply called instead of reading a resume in silence and drawing a conclusion.

A short-tenure question bank

What to verify afterward

Dates and titles are the easiest facts to check and the ones worth checking first; see how to verify employment history for the method. Beyond dates, a reference check aimed specifically at the short stints — not just the most recent or longest role — is where a pattern gets its clearest read. Ask the reference the same neutral question you asked the candidate about why the role ended, and compare the two answers.

Keep the comparison specific rather than impressionistic. If the candidate told you they left a role because the team was restructured and the reference independently describes the same restructuring without being led toward it, that is a strong match. If the candidate's account and the reference's account diverge on basic facts, such as who left first or whether it was voluntary, that divergence is worth more than either account alone, and worth asking the candidate about directly rather than quietly holding it against them.

Where the real risk is, and where it isn't

The risk worth caring about is not "this person has moved jobs several times." It is "this person has a pattern of disengaging quickly regardless of the role, for reasons they cannot articulate specifically." Those are different things, and conflating them costs you candidates who left for entirely defensible reasons — layoffs, a bad manager they can describe specifically, a company that misrepresented the role at hiring — while letting through candidates who give a smooth, well-rehearsed but ultimately empty answer every time. Evidence quotes checked against what a reference independently says are a better signal than tenure length on its own.

Interview Signal's scorecards attach the candidate's own words to each rating, which is useful here specifically because a claim about why a role ended is exactly the kind of statement worth checking later against a reference's independent account rather than trusting from memory, weeks after the screen, when the details have inevitably blurred.

Mistakes that filter out good candidates