Refolk
September 5, 2026·9 min read

IBM's Attrition Hit 2%. The Other 48% Is Your 2026 Sourcing Pool.

IBM's attrition fell under 2% while roughly half of U.S. workers quietly watch for new roles. Here is how to source the 2026 job-hugging engineer.

passive candidate sourcing 2026job hugginghow to source employed engineersquiet-open engineerssourcing senior engineers
IBM's Attrition Hit 2%. The Other 48% Is Your 2026 Sourcing Pool.

Arvind Krishna told analysts this quarter that voluntary attrition at IBM is under 2%, the lowest in 30 years, versus a historical rate closer to 7%. Gallup's March 2026 read says roughly half of U.S. employees are watching for something better. If you are sourcing engineers off WARN filings and "Open to Work" banners, you are hunting the wrong 4%.

The visible sourcing surface has collapsed

The pool of engineers who will raise their hand is now historically small, and the pool of engineers who will take a well-aimed call is historically large. That gap is the entire 2026 sourcing thesis.

Three numbers tell the story:

  • 4.1% U.S. unemployment (BLS, July 2026), roughly 6.9M people. This is the "unemployed and searching" universe, not "employed and looking."
  • 2.1% quits rate (JOLTS, June 2025), down from the 3% Great Resignation peak in 2022. Employed people who openly search have thinned out.
  • ~50% "watching" for a better opportunity (Gallup, 2025 and 2026). That is roughly 10x the actively-unemployed pool, and it is invisible to every tracker your team subscribes to.

Korn Ferry named this in August 2025: job hugging. Employees are holding on "for dear life," in Korn Ferry's phrase, because AI-driven hiring freezes have made external opportunities scarcer. They are not loyal. They are stuck. And stuck disengaged high performers are exactly who you want to reach.

SliceFigureSource
U.S. actively unemployed6.9M (4.1%)BLS, Jul 2026
U.S. quits rate2.1%JOLTS, Jun 2025
Employees "watching" for a role~50%Gallup, 2026
Employed workers planning H1-2026 search38%Robert Half, Dec 2025
Tech workers planning H1-2026 search44%Robert Half, Dec 2025
IBM voluntary attrition<2% (vs. ~7% historical)IBM CEO, late 2025

The ratio is the point. Even at Robert Half's more conservative 38%, the addressable-but-silent pool is roughly 19x the visible-resignation pool. At Gallup's 50%, it is 25x.

Job hugging favors the sourcer, not the employer

Job hugging is when employees stay in roles they would have left in a healthier market, because hiring has slowed and AI has scrambled the entry-level rungs they used to jump onto. That behavior is a supply-side symptom, not a loyalty signal, and it makes cold outreach more effective than it has been in years.

Two mechanisms matter:

  1. Suppressed intent signals. People do not flip their LinkedIn banner, post on "Who Wants to Be Hired," or reply to recruiter DMs when the market feels hostile. So the surface a sourcer used to scan (Open to Work, quits, WARN) undercounts real openness by an order of magnitude.
  2. Concentrated disengagement. For the first time in Gallup's tracking, more U.S. workers are struggling than thriving, with engagement at a 10-year low. The unhappy majority is still on payroll. They will not initiate. They will answer.
Job hugging is not loyalty. It is trapped inventory, and it is priced to move for the recruiter who calls first.

The healthy-company paradox

The best-known "healthy" employers are the richest sourcing ground in 2026, not the worst. IBM, Wells Fargo, and Shopify are publicly telegraphing flat-to-shrinking headcount and using attrition "as our friend," in Wells Fargo CEO Charlie Scharf's phrase. Shopify CFO Jeff Hoffmeister has made the same flat-headcount case on earnings calls.

Nobody at these companies is filing for unemployment. Nobody is showing up on a layoff tracker. But the mechanism is exactly the one that produces quiet-open supply:

  • Reorg without headcount growth
  • RTO mandates without compensation adjustment
  • Denied promotion cycles because the band above is frozen
  • Manager changes because the last one got quietly managed out
  • Backfill freezes that quietly double someone's scope

None of these events surface on the tools most recruiting teams pay for. They surface in conversation, in commit history, in a sudden gap between a person's title and their actual scope. That is the exact gap Refolk closes: describe the engineer you want in plain English, including the employer context ("Senior backend engineer at a company running an efficiency narrative, shipped a migration in the last 18 months"), and get a ranked shortlist across GitHub, LinkedIn, and the open web.

What the Refolk index says about the addressable pool

Refolk's index contains 212,726 current Senior and Staff Software Engineers in the U.S. Apply Gallup's 50% and roughly 106,000 of them are quietly open right now. Apply Robert Half's 44% tech figure and it is still ~93,000. Neither number will show up on any layoff tracker this quarter.

Top current employers of that Senior/Staff pool in the index include Google, Datadog, Vanta, Airbyte, Starburst, and Omada Health. Every one of them is publicly running an efficiency or profitability story. Every one of them, by the job-hugging math, is exporting quietly-open engineers into any sourcer who bothers to reach in.

212,726
U.S. Senior and Staff SWEs in the Refolk index
At Gallup's 50% watching rate, roughly 106,000 are quietly open and invisible to layoff trackers.

The scarcity story sharpens as you narrow the skill. The index shows 14,434 U.S. Senior-and-above engineers with Kubernetes, concentrated in San Francisco, with Meta, Cloudflare, Crusoe, and Datadog as top employers. That is 6.8% of the broader Senior/Staff pool. When your requirement is that specific, the "actively looking" slice of that 14,434 is a handful of people, most of whom every other recruiter is also emailing. The quietly-open slice is closer to 7,000. That is where the roles get filled in 2026.

The Gen Z plus tech overlap converts fastest

The one cohort where "quietly open" reliably converts to "will take the call" is tech workers and Gen Z. Robert Half's December 2025 survey put 44% of tech and healthcare workers and 42% of Gen Z planning an H1-2026 search, versus 38% overall. Robert Half's Dawn Fay called it a "thaw."

The practical read for anyone running passive candidate sourcing in 2026:

  • Prioritize engineers with 2 to 6 years of tenure at their current employer. Long enough to be frustrated by a frozen promo cycle, short enough not to be vested into paralysis.
  • Weight Gen Z and early millennials. They were promised the mobility their older peers had and are not getting it.
  • Deprioritize the "Open to Work" green ring. It is now adverse selection: the people using it in a job-hugging market are disproportionately the ones who could not stay.

Source on engagement-triggering events, not intent signals

Because intent signals have thinned out, the working sourcing signal in 2026 is the engagement-triggering event, not a status change. You are looking for the moment an incumbent's silent tolerance flips into a willingness to answer.

The events that reliably move the needle:

  1. Reorg or manager change in the last 90 days. Watch team-page diffs, LinkedIn "changed roles internally" pings, and public re-orgs announced in earnings.
  2. RTO mandate that materially changes commute.
  3. Missed promo cycle. Someone who has been "Senior" for four years at a company where the median is two is a signal, not a status.
  4. Public efficiency narrative from the CEO. When Krishna, Scharf, or Hoffmeister say "attrition is our friend," they are announcing that internal mobility is dead. Their high performers know.
  5. Product line sunset or acquisition integration. Engineers whose work is being absorbed into a larger org are almost always quietly open within a quarter.

You cannot buy any of these as a filter on LinkedIn Recruiter. You can approximate them by triangulating across GitHub commit patterns, blog posts, conference talk history, tenure math, and employer news. That is the workflow Refolk was built for: describe the engineering signal in one sentence, and let the system triangulate the evidence across sources.

The outreach that gets a job-hugger to reply

A job-hugger replies to specificity and ignores volume. The pitch that worked in 2022 ("saw your profile, big fan, quick chat?") is now noise; the pitch that works in 2026 names their scope and offers a specific delta.

What separates a reply from a delete:

  • Named artifact. Reference the actual repo, RFC, or talk. Generic praise reads as automation.
  • Named scope delta. "You are the third engineer on a team of nine; this role is technical lead on a team of five" beats "great opportunity."
  • Named comp band or equity structure. In a job-hugging market, ambiguity is a cost. Anchor the conversation with a range.
  • Named next step, small. "20 minutes with the founding engineer next Thursday" outperforms "hop on a call."

The person on the other end has already decided they will not initiate. Your message has to do the initiation work for them, and it has to feel like it was written for one human, not one hundred.

What to stop doing in 2026

Stop treating layoff trackers as your top-of-funnel. They miss the 19x-to-25x quietly-open pool that never got laid off in the first place, and Indeed's economists project unemployment will only tick up to around 4.6% in 2026, with software development among the weakest industries for new openings. The visible surface is not coming back.

The specific reallocations to make now:

  • Cut time spent scraping WARN and layoff RSS. Reinvest in employer-signal monitoring (earnings language, RTO announcements, product sunsets).
  • Cut InMail volume. In a job-hugging market, volume outreach underperforms specific outreach by a wider margin than at any point in the last five years.
  • Cut "Open to Work" as a positive filter. Treat it as neutral at best.
  • Invest in cross-source sourcing. The answer to how to source employed engineers is no longer on any single platform. It is in the join between GitHub activity, LinkedIn tenure, personal blogs, conference talks, and employer news.

The teams that will hire the best Senior and Staff engineers over the next 18 months are not the ones with the biggest WARN alerts. They are the ones who accepted that sourcing passive engineers is now the entire job, and built a workflow around describing the person in plain English and letting the tooling do the join.

FAQ

What is "job hugging" and how is it different from quiet quitting?

Job hugging, a term Korn Ferry coined in August 2025, describes employees staying in roles they would have left in a healthier market because external opportunities have thinned. Quiet quitting is a behavior inside a job (doing the minimum). Job hugging is a decision about the job (staying against preference). For recruiters, job hugging matters more, because it means the majority of the workforce is quietly open to a call even though they will not signal it publicly.

If only 4.1% are unemployed, why does Gallup say 50% are "watching"?

Because those are two different populations. The 4.1% BLS figure is unemployed and actively searching. Gallup's ~50% is employed workers open to a better opportunity if one appears. The employed-and-openly-searching group sits between them and is captured by the JOLTS quits rate (2.1%) and Robert Half's H1-2026 planned-search figure (38%). Layoff trackers only see the 4.1%. Sourcing wins now come from the 46 points in between.

Which companies should I source from first in early 2026?

Start with employers running a public efficiency or flat-headcount narrative and dense with Senior/Staff engineers. In Refolk's index, that includes Google, Datadog, Vanta, Airbyte, Starburst, Meta, Cloudflare, and Crusoe. Layer in an engagement-triggering event (reorg, RTO mandate, product sunset, missed promo cycle) and you will out-convert any recruiter still working the WARN feed.

How do I actually reach engineers who are not marked Open to Work?

Describe them by signal, not by status. In Refolk, that looks like a plain-English query naming the employer type, tenure, and technical artifact ("Senior Kubernetes engineers at healthy West Coast infra companies, 3+ years tenure, shipped a public migration in the last year"). Then reach out with a message that names a specific artifact of their work, a specific scope delta, and a small next step. In a job-hugging market, specificity is the entire unlock.

Try it on the search you came here for

Stop building boolean strings. Just describe the person.

Type one sentence. I plan the search, read GitHub, public LinkedIn and Crunchbase records, and the open web as it is right now, and hand back a ranked list with the reason next to every name.

  1. 01Describe them

    One plain sentence. Role, city, stack, stage, whatever matters to you.

  2. 02I read the web live

    GitHub, public LinkedIn and Crunchbase records, the open web. Not a database that went stale last quarter.

  3. 03You read the shortlist

    Ranked, with the reasoning under every name. Open a profile, ask a follow-up, narrow it down.

  • No boolean, no filters, no seat to buy. One box.
  • Read at search time, so a profile updated yesterday counts today.
  • Every step visible as it runs, every name with its reason.

500 free credits on sign-up. No card, no demo call. See real searches.

Read next