IBM's 14-Day NDA Window Closes Aug 19. The watsonx Pool Is 534.

IBM opened a two-week "voluntary" separation offer on August 5, 2026. It closes August 19. If you wait for "Open to Work" flags to appear, you will lose this pool to referrals, because the departures are getting wrapped in NDAs and 45-day OWBPA consideration periods that push visible LinkedIn end-dates into October.

This is a calendared outflow with a known tempo and a mostly invisible signal surface. Below is what to search, where, and in what order over the next 14 days, anchored on Refolk's index of professional profiles.

Why the Aug 5 to Aug 19 window is different from a normal layoff

The exit dates are public but the exits themselves will not be. IBM's voluntary separation offer, per Techrights reporting, runs Aug 5 through Aug 19, 2026, and the target cohort is roughly the 15% of staff previously marked as "low performers" under IBM's stack-ranking system, a group large enough to touch 30,000+ people without triggering WARN notices.

Three mechanics compound to hide the outflow:

• NDAs. Separation agreements include non-disclosure (usually encapsulating non-disparagement), so leavers cannot narrate the exit publicly.
• OWBPA 45-day consideration periods for group layoffs involving employees 40 and older. Signed paperwork does not equal a same-week LinkedIn update.
• Title inertia. Senior IBMers rarely change their headline until a next role is signed, and in a wave this size, "next role signed" clusters 6 to 10 weeks after the offer closes.

Net effect: the visible pool on LinkedIn between Aug 19 and mid-October will look almost unchanged, while thousands of the people you actually want have already mentally checked out. That is the arbitrage.

40,000

What the watsonx and Z/mainframe pools actually look like

The watsonx pool is small enough that a single day of the Aug 5 to Aug 19 window can materially reshape it, while the Z/mainframe pool is deep, old, and already dispersed across a handful of banks and specialty shops. Both matter, and they demand opposite sourcing strategies.

In Refolk's index of professional profiles:

• 534 profiles globally list watsonx as an explicit skill.
• The single largest current employer of self-tagged watsonx talent is IBM India Private Limited, with 16 profiles. IBM Research is close behind.
• Top regions for watsonx skill are Bengaluru, New York, and Singapore, meaning US watsonx supply outside IBM itself is even thinner than 534 suggests.
• 6,250 US-based profiles list z/OS as a skill, concentrated at JPMorgan Chase, SoFi, Hitachi Vantara, and Unicom Systems.

At 534 profiles globally, a 40-person watsonx outflow is roughly 7.5% of the tagged pool moving in a single fortnight. There is no world where LinkedIn Recruiter surfaces that in real time.

The three-track playbook for the next 14 days

Run three sourcing tracks in parallel between now and Aug 19: identity-signal search for watsonx, employer-destination search for Z/mainframe, and Red Hat pre-outreach for the rumored October wave. Each track uses a different signal because each pool has a different visibility problem.

Track 1: identity signals for watsonx, not titles

Title search will not work here. Only ~534 people globally self-tag watsonx as a skill, and IBM itself employs the plurality of them. The people you want, IBM Research staff and watsonx contributors, mostly carry generic "Senior Research Engineer" or "AI Engineer" titles on LinkedIn.

Use these identity signals instead:

1. Commits to github.com/IBM watsonx- repos* in the last 12 months.
2. Hugging Face model card authorship on IBM Granite family models.
3. IBM Research paper co-authorship, especially arXiv drops from 2024 to 2026.
4. watsonx-tagged Medium and IBM Developer posts with named authors.
5. Kaggle profiles connected to IBM watsonx competitions.

This is the exact gap Refolk closes: you describe the person in plain English ("senior engineer with watsonx commits or IBM Granite model card authorship, based in the US or EU, currently at IBM") and get a ranked shortlist that pulls from GitHub, LinkedIn, and the open web at once, rather than a Boolean that only sees stale titles.

Track 2: employer-destination search for Z/mainframe

The mainframe Z pool is deep but geographically inconvenient, and its ex-IBM movement pattern is well-established. In Refolk's index, US z/OS talent lands overwhelmingly at four employers: JPMorgan Chase, SoFi, Hitachi Vantara, and Unicom Systems. For the Aug 5 to Aug 19 window, this pattern gives you two shots:

• Current IBM Z engineers with 15+ year tenure. These are the "marked but not yet gone" cohort. Reach them before the offer closes.
• Recent ex-IBM Z engineers already at the four destination employers. Many are one call away from a second move, especially if they landed after a prior IBM RA.

The RTO 50-mile rule is a free pre-filter. Per the memo, staff must live within 50 miles of a strategic center - Armonk, Raleigh, Austin, or Atlanta - or "separate from IBM." Any IBM engineer publicly located outside those four metros is disproportionately in the take-the-offer cohort. Geo-negative-filter accordingly.

Track 3: Red Hat pre-outreach for the October wave

Techrights reports a second wave for IBM in early September and a Red Hat wave in October. Red Hat engineers read Techrights. Reach out now, before the October wave, and you buy 60 days of relationship head start on every recruiter who waits for a press release.

Red Hat still dominates the senior OpenShift and Kubernetes segment: in a sampled Red Hat/OpenShift senior slice in Refolk's index, 9 of 18 were current Red Hat. If you want senior Kubernetes talent this fall, the calendar is telling you exactly when to start.

The NDA problem, and what to actually watch instead

NDAs kill the two signals most sourcers rely on ("I'm open to new opportunities" posts and clean end-dates), so you need to replace them with earlier, weaker, more numerous signals.

Watch these instead of Open to Work:

• github.com/IBM commit frequency dropping to zero for a previously active contributor.
• Personal GitHub activity spiking on non-IBM projects (side-project polish is a leading indicator of exit).
• Conference talk submissions to KubeCon, QCon, or Strata under a personal email rather than @ibm.com.
• TheLayoff.com IBM board thread velocity, a real-time NDA-adjacent proxy for sentiment.
• Personal-domain resume PDFs re-uploaded in the last 30 days (crawlable, timestamped).
• Hugging Face profile bio edits removing "at IBM" language.

Sourcers waiting for Open to Work will lose the Aug 5 pool to referrals. The alpha is Aug 5 to Oct 15.

None of these individually is a departure. Together, weighted, they identify the receptive-inbound cohort with far more precision than a title search. Refolk pulls these into a single query surface, which is why "find me people currently at IBM whose personal GitHub activity spiked in the last 60 days" is a query you can actually run rather than a research project.

The contrarian read: real net attrition is 2 to 6%, not 15%

The most important number in this story is not 15%. Insiders on TheLayoff estimate actual net attrition at 2 to 3%, or 5 to 6% once you account for band 6 backfills (roughly 5,000 out, 2,500 hired back in at lower band). The gap between the 15% "marked" figure and the 2 to 6% net attrition is exactly where sourcers should focus.

Why this matters operationally:

• The "marked but not yet gone" are a much larger cohort than the "actually leaving." They know they are marked. They are the receptive-inbound cohort even if they do not take the Aug 19 offer.
• Backfills at band 6 mean many teams will be understaffed at the senior level from September onward. If you are recruiting for staff-plus IC roles, IBM's own internal reorg is generating referrals for you.
• Techrights also flags that HashiCorp and Confluent, both acquired by IBM, have quietly seen mass layoffs in 2026. Alumni of those companies now tagged "IBM" are in the pool and most sourcers will not think to filter for them.

For ex-IBM engineers hiring campaigns, add HashiCorp and Confluent alumni to your target list. They will not appear in a naive "current company: IBM" search, but they are subject to the same cut.

534

A concrete 14-day sourcing calendar

Treat the Aug 5 to Aug 19 window as a sprint with three checkpoints. The point is to have first contact made before Aug 19, not after.

If you run this playbook and land three watsonx hires, you have moved roughly 0.5% of the entire global tagged pool. That is the leverage a calendared, NDA-muted outflow event creates, and it is why speed matters more than volume here.

FAQ

How many people will actually leave IBM in the Aug 5 to Aug 19 window?

The headline "15%" figure refers to the stack-ranked "low performer" cohort, roughly 40,000 globally at IBM's ~270k headcount, per TheLayoff.com community math. Actual net attrition is more likely 2 to 6% once you account for band 6 backfill hires. The larger group still matters for sourcing, because "marked but not yet gone" is the most receptive-inbound cohort IBM has produced in years.

Why can't I just wait for LinkedIn to update after Aug 19?

Because OWBPA gives employees 40 and older 45 days to consider group layoff separation agreements, and NDAs suppress the usual "here's what happened" posts. Expect a 6 to 10 week gap between the Aug 19 close and visible end-date changes on LinkedIn. If you wait for that update, referrals and faster recruiters will have already placed the pool. The Aug 5 to Oct 15 window is the arbitrage.

Where are ex-IBM Z/mainframe engineers actually landing?

In Refolk's US index of z/OS-tagged profiles (6,250 total), the top destination employers are JPMorgan Chase, SoFi, Hitachi Vantara, and Unicom Systems. These are the shops that pay for and maintain deep IBM Z expertise, and they are the natural first-hop destinations after an IBM exit. If you are competing for Z talent, assume you are competing with those four.

Should I be sourcing Red Hat engineers right now or waiting for October?

Now. Techrights reports a rumored Red Hat wave in October 2026, and Red Hat engineers are already watching the same signals you are. Refolk's sampled Red Hat/OpenShift senior slice shows 9 of 18 still at Red Hat, so the pipeline value is real. Sixty days of relationship head start before the wave hits is worth more than a cold outreach in October when every recruiter has read the same press release.