The Boomerang Rehire Score: Pursue Now, Nurture, or Pass

This guide gives you a rubric for deciding which of your former employees to chase for an open role, and whether now is the moment. It is for in-house recruiters, sourcers, talent leaders, and founders who have an alumni roster and a live req, and who need to rank named people today rather than build a newsletter. By the end you can score any alumnus on two axes, fit and return-readiness, and sort them into pursue-now, nurture, or pass with a reason you can defend to a hiring manager.

Most public writing on boomerang hiring stops at the plumbing of alumni networks and the general upside of rehires. That is a pep talk, not a decision. The judgement you actually make is per-person: is this named former employee worth an outreach this quarter for this role. That is what the score below is built to answer.

Why a per-person score beats the boomerang averages

The boomerang averages are real but they describe a population, not the person in front of you. The retention and cost numbers are strong enough to justify looking at alumni first, but weak enough that applying them to the wrong name will burn a hiring manager's trust.

Here is the population case, drawn straight from the reported benchmarks.

Those figures come mostly from vendor and HR-press compilations rather than primary datasets, so hold them loosely. The more careful peer-reviewed work is cooler: Arnold and colleagues, in the Journal of Management, studied 1,318 boomerang managers and found post-rehire performance was not statistically different from before they left, and Purdue's summary of that work notes that internal and external hires tend to improve more over time than rehires do.

The practical reading: the averages tell you alumni are worth scoring, not that any given alumnus is worth pursuing. The score isolates the two things the averages hide, whether the original exit trigger is resolved and whether the person is gettable right now.

The two axes: rehire fit and return-readiness

Score every alumnus on two independent axes. Rehire fit asks whether you should want them back for this role. Return-readiness asks whether they are reachable and movable now. A person can be high on one and low on the other, and the two mistakes those crossings produce are different, so keep them separate.

Rehire fit is built from three inputs:

• Eligibility. A hard gate, not a score. Terminated for cause or job abandonment means barred, full stop.
• Exit-reason resolvability. Is there a concrete, verifiable difference now against the thing that drove them out.
• Skill and scope delta. Does their public history since departure make them a raise, a neutral, or a step down against the open req.

Return-readiness is built from two:

• Current tenure and role-change recency. Short tenure at a new employer plus a recent move is the gettable tell; long, settled tenure is the pass-for-now tell.
• Stated return reason clarity. A specific, forward-looking reason beats a vague one that is really escape from a job they just took.

The top-right quadrant is the only one that earns outreach this week. The top-left is the one people mishandle: a genuinely strong alumnus who is currently settled. The tax on waiting there is comp, which the next sections make concrete.

Set your baseline by sector before you score anyone

Your industry sets the odds before any individual signal does. Because boomerang share of hiring varies so widely by sector, the same personal score means different real-world probabilities for a tech recruiter than for a manufacturing one.

ADP's data puts boomerangs at 35% of new hires across all sectors as of March 2025, up from 31% the year before, with the information sector running near two-thirds. If you recruit in tech, your roster is structurally warmer than the headline suggests and a "nurture" verdict decays faster because competitors are just as likely to be re-poaching your alumni. If you recruit in manufacturing, be more selective about which names you spend outreach on, because the base rate is lower.

Market depth matters too, and it cuts both ways.

In Refolk's index of professional profiles, the US "Software Engineer" pool returns 330,907 people against 41,159 in the UK, roughly 8x. American alumni sit in a deeper, more liquid market: they are easier to locate, and they are easier for a competitor to re-poach quickly. That raises the cost of nurturing slowly and pushes borderline US names toward pursue-now.

Score each dimension: what it proves and how it lies

Each dimension below has a scoring rule, what a clean signal proves, and what it looks like when it misleads you. Read the "how it lies" column as carefully as the score.

Eligibility (gate, not points)

Eligibility is a pass/fail gate applied first. In standard policy templates, people terminated for cause or who abandoned their job are not eligible for rehire. This proves nothing about talent; it removes legal and cultural risk before you spend a minute sourcing. It lies when a recruiter reads an old boomerang statistic onto a barred name: the 44% retention lift and the productivity numbers are built almost entirely on voluntary leavers, so they do not transfer to involuntary exits at all.

There are compliance gates here too. On Form I-9, a Supplement B applies when you rehire within three years of the date the original I-9 was completed, and anyone rehired more than three years after the original I-9 must complete a new one. If you plan to credit prior service for seniority or benefits, set consistent rules, for example requiring at least a year of prior service and that prior service exceed the gap.

Exit-reason resolvability

This is the most load-bearing document you hold. Score it resolved or unresolved, based on a specific, verifiable difference against the trigger. A resolved trigger proves the return will not simply recreate the exit; Randstad's global data attributes 32% of departures to a bad relationship with a manager or colleague, so "the manager left" is often the whole story. It lies when regret masquerades as fit. Boomerangs who leave a second time tend to leave for the same reasons as the first, which makes the original exit-interview note effectively a re-attrition forecast.

Positive-reason exits fare best. People who left to continue education, change careers, relocate, or stay home with family are more likely to return and perform at their previous level. Note, though, that Purdue's summary found initial turnover reason was not a strong predictor of rehire performance once you control for initial performance, so weigh the last performance rating alongside the reason.

Skill and scope delta

Compare their public work since departure to the open req and rate it raise, neutral, or lower. A raise proves the time away added value beyond a lateral external hire: workers who spent 12 to 18 months at a competitor or in another industry often return with process improvements, technology awareness, or networks. Evidence looks like title progression, scope words in a new title, and new stacks on a public GitHub profile.

It lies in two ways. Comp is one: boomerangs return at 15 to 25% higher compensation, so a bigger title may just mean a bigger price, not a better fit. GitHub is the other. Stars measure project popularity, not an individual's level, and only 18% of GitHub activity is public per the 2025 Octoverse report, so treat an absence of activity as missing evidence, not as weakness.

Return-readiness: tenure and stated reason

Short current tenure plus a recent role change is the strongest gettable tell. Regret peaks early - one in five who quit have already returned - and practitioners cite a 6 to 16 month reconnect window, after the regret sets in but before your relevance fades. Long, settled tenure is the settled read. The stated return reason must be specific and forward-looking; ask whether the person is running toward your role or away from the one they just took.

The original exit-interview note is a re-attrition forecast, not a memory of why someone left.

The procedure: from roster to ranked verdicts

Run this end to end on a roster against one open req. Rough time is about an hour to ninety minutes per person across roles, front-loaded on record-pulling and sourcing.

The order matters at one point: pull records and gate on eligibility before you source current status, so you never spend sourcing time on a barred name. Sources split on whether re-onboarding is trivial or full; treat it as full, because the company has changed even if the person feels familiar.

Locating current status is the slow part, because it means cross-checking two independent public sources per person: a public profile against a conference bio, an alumni update, or a GitHub account. This is exactly the friction Refolk removes, because you can ask for the roster shape you want in plain English instead of running Boolean X-ray queries name by name.

How this goes wrong: failure modes and false positives

This is the part that saves a search. Every failure mode below is a specific way a scored roster produces the wrong verdict, with the check that catches it.

• Treating survey interest as your roster's intent. The Muse's 48% who would try to get their old job back is a generic figure; a stricter Joblist read found only 17% would return and 24% were maybe. False positive: assuming half your alumni are gettable. Check: score per-person tenure and role-change signals, not population averages.
• Ignoring the exit type. Voluntary-leaver evidence does not transfer to involuntary exits. False positive: applying "44% higher retention" to someone terminated for cause. Check: verify the rehire-eligibility flag before anything else.
• Rehiring into the unresolved trigger. If the manager, comp band, or workload that drove the exit is unchanged, you recreate the conditions, which is the most common cause of a second exit. Check: require a specific, verifiable "what is different now."
• Confusing regret with fit. A hot re-engagement can really be escape from a job the person just took. Check: read the clarity and specificity of the stated return reason; vague reasons are a flag.
• Over-crediting GitHub as skill proof. Stars measure project popularity, not engineer level, and most activity is private. Check: treat absent activity as missing evidence, not weakness, and confirm skill through work history.
• Single-source current-employer reads. A public profile can be stale or restricted. Check: confirm current role from two independent public sources.
• Skipping re-onboarding. The "they already know us" assumption is the most common mistake, because the company changed. Check: run a short structured reentry regardless of how recent the departure.
• Assuming long-term outperformance. Internal and external hires tend to improve more over time than rehires. Check: score for ramp speed and retention, not indefinite trajectory.

What each verdict commits you to

The three verdicts are commitments, not labels. Pursue-now means a hiring manager sends outreach against the open req this cycle. Nurture means the person is genuinely strong but currently settled, so you stay in view and re-check tenure. Pass means no active work.

Nurture is the verdict people treat as free, and it is not. Because boomerangs return at 15 to 25% higher compensation and come back with higher titles and pay, every quarter a strong alumnus spends gaining external scope raises their return price. In a deep market like the US Software Engineer pool, competitors can convert your nurture target before you do. So attach a re-check cadence to every nurture verdict and a specific tenure threshold that flips it to pursue-now.

Name | Verdict | Fit (elig/trigger/delta) | Return-readiness (tenure/reason) | One-line reason
Jordan Lee | PURSUE NOW | eligible / trigger resolved (old mgr gone) / raise | 11 mo tenure, recent move, wants IC growth | Left over manager; that manager is gone; now a senior IC 11 months into a role that is not delivering growth.
Sam Ortiz | NURTURE | eligible / trigger resolved / neutral | 3 yr tenure, settled, no stated intent | Strong and eligible but settled; re-check at 18-24 mo or on any public role change.
Priya Nair | PASS | barred (terminated for cause) / n/a / n/a | n/a | Ineligible per policy; do not contact.

Cost context helps set the outreach effort. Rehires can cost up to 50% less to source, with no agency fee and most first-round screening already done, and one program lifted its rehire rate from 2.4% to 8%, with a customer finding a 1% rise in rehire rate worth $1.25m in savings. Onboarding a fresh hire runs around $4,000, much of which a rehire eliminates. Those savings justify the outreach effort on pursue-now names; they do not justify chasing a settled name into a bidding war.

Keep the roster current

Run this check before you send any outreach, and re-run the status portion each cycle because tenure and role changes are the fastest-moving signals on the roster.

The score is only as fresh as its tenure reads. Re-run steps three through six each hiring cycle, and treat any public role change on a nurture name as a trigger to re-score immediately, because that is the moment a settled alumnus becomes gettable and the moment a competitor is most likely to move first.