Cloudflare's May 7 Cut: 1,100 Alumni You Shouldn't Email Until August
Cloudflare's May 7 layoff pays full base through Dec 31 and vests equity to Aug 15, 2026. Here's how to time outreach to 1,100 alumni without burning the list.
On May 7, 2026, Cloudflare cut more than 1,100 employees, roughly 20% of its workforce, on the same earnings call where it reported Q1 revenue of $639.8M (up 34% YoY). The severance is unusually generous: full base pay through December 31, US healthcare through year-end, and equity vesting extended to August 15, 2026. If you treat this like a normal RIF and InMail every name in May, you will burn the list.
This is the rare layoff where the smartest move is to slow down.
The package rewrites the outreach calendar
Read the official Cloudflare blog post ("Building for the future", co-signed by Matthew Prince and Michelle Zatlyn) and the math becomes clear. Affected employees keep their base salary through December 31, 2026. They keep vesting equity through August 15, 2026. One-year cliffs were waived for recent hires, with pro-rated vesting. That is roughly eight months of paid runway from the announcement date.
Compare that to Snap's April 2026 layoff, which cut about 1,000 people with four months of severance. Cloudflare paid roughly double. For context on the rest of the market: U.S. tech announced 85,411 job cuts in the first four months of 2026 per Challenger, Gray & Christmas, a 33% YoY increase, with AI cited as the leading attributed cause for two consecutive months. Most of those cohorts hit the market hot. Cloudflare's does not.
The typical post-layoff sourcing playbook assumes panic mode within two to four weeks: scraped lists, cold InMails, "saw the news, would love to chat." That playbook will fail here. A Cloudflare alum reading a generic outreach in May has full salary, healthcare, vesting RSUs, and zero financial pressure to respond. They will archive you.
Two windows, not one
There are really two sourcing windows on this list:
- May through late July: relationship building. Low-pressure conversations. Coffee, advisory chats, "what are you thinking about next?" No closes. No urgency. The candidate is not motivated yet, and pretending otherwise reads as tone-deaf.
- Late July through mid-August: active conversion. Vesting ends August 15. Paychecks end December 31. Senior people start lining up start dates in this window. This is when you push for onsites and offers, and when you should be specifically offering start dates of August 18 or later so the candidate captures the full vesting extension.
A rival recruiter who pressures a Cloudflare alum to start before August 15 is asking them to forfeit roughly three months of additional vesting. That is a quantifiable opportunity cost, and naming it explicitly in your message ("we can start you August 18 so you don't leave equity on the table") is a hard-to-beat signal of competence.
Who was actually cut
Prince was unusually public about which roles went. He used Drucker's "builders / sellers / measurers" framework and aimed at measurers: finance, compliance, legal review, internal audit, revenue recognition, middle management, and operations support. He explicitly protected revenue-carrying sales reps and engineering.
That has two implications for sourcing Cloudflare engineers and operators.
The "measurer" tag is a hiring signal, not a stigma
Every Series B and Series C company in your portfolio needs its first compliance lead, its first revenue-recognition manager, its first internal audit hire, its first ops lead with enterprise scars. Banks and non-AI-pilled enterprises need the same roles, in volume. The fact that Prince publicly labeled these functions as "measurers" doesn't damage the resume; it tells you exactly where to fish.
If you're a recruiter at a fintech that just raised a Series C, the Cloudflare alumni list is the cleanest single source of senior G&A talent you'll see this year. The brand stamp matters. The package means the candidates are still emotionally intact when you talk to them, instead of nine weeks into an anxious search.
The engineering pool is small and scarce
Because engineering was largely protected, "Cloudflare engineer alumni" from this cut is a much smaller pool than the 1,100 headline suggests. The technical profiles that surfaced are dominated by Software Engineers, Engineering Managers, and PMs, with global concentrations in SF Bay Area, Austin, Seattle, London, Lisbon, and Bengaluru. Treat them as scarce, not abundant. A few hundred names globally, not thousands.
This is the part of the list where standard LinkedIn filters fall apart. Searching "Cloudflare" plus "Software Engineer" in London returns everyone who ever worked there, including 2017 alumni, current employees who didn't get cut, and contractors. You need to constrain by likely-affected tenure, function, and location, then cross-reference with public signals like recent GitHub activity drop-offs or "open to work" toggles that flipped after May 7. That kind of multi-signal query is exactly the friction Refolk was built to remove: you describe the person in plain English ("ex-Cloudflare backend engineer in London, joined 2022 to 2024, likely affected by the May cut") and get a ranked shortlist across GitHub, LinkedIn, and the open web.
Why these engineers are unusually valuable
Prince said the entire R&D org runs on Cloudflare's Workers platform, with engineers using vibe coding, and 100% of deployed code reviewed by autonomous AI agents. Whatever you think of that as a management posture, it means the engineers who came out of that org have shipped production code through agentic AI workflows, daily, at scale. That is a small population globally.
Most engineers list "used Copilot" on a resume. Cloudflare alumni shipped through agentic review on every PR. </pull>
For any company hiring around agentic AI, layoffs hiring conversations, or AI-native infra teams, the Cloudflare engineer pool is one of the few places to find candidates who have lived inside that workflow rather than read about it. Position the outreach accordingly. "We use Claude Code" is not a pitch. "Our review pipeline is closer to what you ran on Workers, and we want your opinion on where it breaks" is.
NET dropped 24% the same day. That changes the math.
NET stock fell about 24% on the announcement, despite the earnings beat. Cloudflare projected $140M to $150M in restructuring charges, mostly in Q2.
This matters for sourcing in a specific way: the equity portion of severance is worth materially less than employees expected on May 7. Senior people whose unvested RSU piles took the biggest haircut have rational reasons to move earlier than the August 15 date suggests. Do not blanket-delay outreach. Segment by seniority.
- Staff and above, heavy unvested RSUs: the August 15 extension is worth less per share than they planned. They may start serious conversations in June. Reach out earlier, with respect, framing it as exploratory.
- Mid-level ICs and managers: the package math still favors waiting. Light touch through July, push in August.
- Recent hires whose cliffs were waived: small absolute equity numbers, larger career anxiety. Often the most responsive group early.
This segmentation is the whole game on this list. A blanket "send everyone the same sequence on May 20" approach loses to a segmented approach by a wide margin, and the segmentation can't be done by title alone. You need tenure, level, and team. That is the second place a plain-English query tool earns its keep: instead of building three separate LinkedIn Recruiter projects with overlapping filters, you describe the segment and pull the slice.
The backlash is a feature, not a bug
Chamath Palihapitiya criticized Prince's framing on the All-In Podcast. There has been broader public debate about whether attributing 1,100 cuts to "a 600% jump in internal AI usage" is honest framing or PR cover for a margin decision. You don't have to take a side. But you should know that some Cloudflare alumni feel publicly labeled as obsolete, and that feeling shapes how they read inbound recruiting.
The implication for messaging: do not lead with AI. Do not reference Prince's "measurers" framing, even sympathetically. Lead with what the candidate built. Reference specific products (Workers, R2, Magic Transit, Zero Trust, the developer platform). Treat them as practitioners with a track record, not as a category Prince retired.
A realistic 90-day plan
If you are sourcing Cloudflare engineers or operators from this cut, here is the cadence that actually fits the package:
Weeks 1 to 4 (May): Build the list. Tag by function, level, location, likely-affected tenure. Quietly follow on GitHub and LinkedIn. No outreach yet, except to staff-plus engineers with large unvested positions who may move early.
Weeks 5 to 10 (June through mid-July): Soft-touch outreach. Advisory conversations, intros to founders, "tell me what you're thinking about." No pitches. The goal is to be the recruiter they trust by August, not the seventh InMail they archived in May.
Weeks 11 to 14 (late July through mid-August): Active conversion. Onsites, offers, signing bonuses calibrated against remaining vest. Start dates of August 18 or later. Specific named comp bridges for anyone losing meaningful unvested equity.
Weeks 15 onward: Boomerang watch. Prince said publicly that Cloudflare expects to hire again and may have more headcount in 2027 than in 2026. A subset of this alumni list will be on Cloudflare's own re-hire list within 12 months. If you place someone, you are placing them against an active counter-offer risk from their old employer. Price that in.
What this means for Cloudflare alumni recruiting in 2027
The pattern Cloudflare set here, generous package, public framing of cuts by function, vesting extension past a clean calendar date, will be copied. Several large tech companies are already drafting similar packages for 2026 H2 cuts. The two-window sourcing model becomes the default, not the exception.
Recruiters who learn to operate on this calendar in May will have an edge through the rest of 2026. The ones still blasting same-day InMails will keep wondering why their response rates are dropping.
FAQ
When should I actually start outreach to Cloudflare alumni?
For most of the list, light-touch conversations starting in June, intensifying in late July, and converting in August. The exception is senior engineers and managers with large unvested RSU positions, who may rationally accelerate their search given NET's 24% same-day drop. Segment by level and tenure before you decide on cadence.
Are Cloudflare engineers really "AI-native" in a useful way?
More than most. Prince stated that the entire R&D org runs on Workers, uses vibe coding, and reviews 100% of deployed code through autonomous AI agents. Whether you agree with that as a strategy, engineers from that org have daily production experience inside agentic workflows. For roles that need that lived experience, the pool is small and high-signal.
What about non-engineering roles from the cut?
This is where the volume is. Prince publicly targeted finance, compliance, legal review, internal audit, revenue recognition, middle management, and ops support. For Series B/C companies that need their first senior G&A hires, or for enterprises building these functions in new geos, the Cloudflare alumni list is the cleanest single source you will see this year. The Cloudflare brand stamp helps, not hurts.
How do I find the right slice without scraping?
The standard LinkedIn filters return everyone who ever worked at Cloudflare, which is the wrong list. You want affected tenure, specific functions, specific geos, and public signals of recent change. Tools that take a plain-English query across GitHub, LinkedIn, and the open web, like Refolk, are built for exactly this shape of search and save the work of stitching three filtered projects together.