Cloudflare's 1,100 Get Paid Through December 31. Source Them in September.
Cloudflare's May 2026 cuts come with severance through year-end. Here's the right timing window, and which "measurers" are actually worth pursuing.
On May 7, 2026, Matthew Prince and Michelle Zatlyn posted "Building for the future" and put 1,100 Cloudflare employees, about 20% of the company, out the door. Every recruiter with a finance, legal, ops, or middle-management req opened a spreadsheet within hours. Most of them are wasting their summer.
The package is the story. Full base pay through December 31, 2026. US healthcare through year-end. Equity vesting through August 15, including a waived one-year cliff for anyone short of it. That is not a layoff package. That is an eight-month sabbatical with benefits, handed out by a company that beat Q1 revenue estimates ($639.8M against $621.9M consensus). The 1,100 are not desperate. They will not act desperate until the runway gets short.
The severance is the moat
Challenger data puts the average US severance package at roughly 16 weeks, about four months. Cloudflare's package, for a May-cut employee, runs roughly eight months. Google's 2026 package is 16 weeks base plus two weeks per year of service. Meta's recent packages have been similar. Salesforce floored its last round at five months regardless of tenure. Cloudflare flat-paid every cut employee through year-end, which means a six-month tenure engineer is sitting on the same runway as a six-year tenure director.
That changes the response curve. A "we have a role open, can you start in three weeks" message landing in a Cloudflare alum's inbox on June 3 is asking them to trade six months of paid runway for an immediate commute. The open rate will be fine. The reply rate will be terrible. The accept rate will be worse.
The actual timing
Three windows matter, and they are not equal.
May through mid-August: relationship, not roles. Intro coffees. Advisory chats about your portfolio. "I'd love to learn what you saw inside Cloudflare on AI-agent rollout." No ask. You are buying a slot in their mental queue for when they start looking. Recruiters who pitch roles here get filtered into the "annoying" bucket and stay there.
Mid-August through early September: the equity unlock. This is the under-discussed window. Equity vests through August 15. Many of the 1,100 will refuse to seriously evaluate a new package with new equity until they see the final RSU tranche land and can value what they are giving up. The two weeks after August 15 are when "I'm not really looking" flips to "send me the deck." Outreach in this window converts at multiples of June outreach.
September through November: the conversion window. Pay still flows but the runway visibly shortens each week. Candidates start wanting signed offers in hand before benefits expire December 31. Sell January start dates. A January start pitched in October is a far easier yes than a June start pitched in May, because the candidate gets to keep every dollar of severance and walk into a new role with no gap.
A January start date pitched in October is the easiest yes in tech recruiting right now. </pull> If you are running a year-end hiring sprint, your December 15 close target should be backed into from a September 8 first-touch. Not earlier. ## "Measurer" is two pools, and one of them is a trap Prince borrowed the framework from Peter Drucker's *The Practice of Management* (1954): builders, sellers, measurers. In his WSJ op-ed "How I Choose Which Cloudflare Employees to Replace With AI," he was explicit that the vast majority of the 1,100 were measurers, defined as middle management, finance, legal, internal audit, revenue recognition, compliance, ops, and parts of marketing. Quota-carrying sellers were spared. Engineering builders were largely spared. Recruiters reading that list and thinking "great, 1,100 finance and ops people" are about to waste a quarter. The pool splits cleanly into two segments, and they have opposite market dynamics. ### Segment A: the IC specialists worth chasing Senior FP&A leads. Revenue-recognition specialists who have closed a public-company quarter under ASC 606. Securities and SEC-reporting counsel. Internal audit ICs who know SOX at a $1.5B+ public SaaS company. Technical accounting managers. These are precisely the people pre-IPO companies need to make their first finance and legal hires, and they almost never come on the market. Databricks, Canva, Stripe's finance org, and anyone within 18 months of an S-1 should already have a list. There is a second, sharper destination: AI back-office startups. Ramp, Brex, Pilot, Harvey, EvenUp, Rilla. Cloudflare's internal AI adoption surged over 600% in the three months before the cuts. The measurers who got cut watched that happen in real time. They have firsthand experience with agentic finance and legal tooling that most candidates lack, and they have just been told, in a published memo, that their old function got eaten. They are uniquely motivated to go build the thing that ate them. ### Segment B: the generalists to skip Director of Operations. Chief of Staff. Generalist Program Manager. Middle Manager of People Managers. Marketing Operations Director. These titles got cut because the role itself compressed under AI, and most hiring companies are flattening the same layer at the same time. You are pulling from a shrinking pool into a shrinking pool. The candidates are real, qualified, and likable. The market for them in Q4 2026 is going to be brutal, and not because of anything they did wrong. Prince said publicly he thinks this pattern will "become the norm over the next year." Meta is cutting 8,000 US jobs. Cognizant is cutting 15,000+. Oracle's restructuring touches 30,000 roles. HSBC, 20,000. Every one of those announcements adds more generalist measurers to the same pool. The IC specialist pool stays small. The generalist pool floods.
refolk prompt: Find former Cloudflare finance or legal ICs cut in May 2026 with public-company revenue recognition or SEC reporting experience, ranked by AI tooling exposure. note: You get a shortlist of the Segment A specialists, with current LinkedIn signals and any public writing or GitHub activity since May, instead of 1,100 raw alumni profiles. slug: 5vyqjh6146
This is exactly the segmentation problem [Refolk](/) was built for. The 1,100 don't share a title, a location, or a function, and the cut crossed Austin, Seattle, Singapore, and the UK. Boolean strings over LinkedIn return either too narrow ("Senior Manager, Revenue Operations" at Cloudflare, 11 results) or too noisy (former Cloudflare + "finance," 4,000+). Describing the person in plain English, "ex-Cloudflare revenue recognition lead, public company experience, posted about AI agents in finance after May 7," is what actually returns the 30 names that matter.
## Geography: this is not a Bay Area cut
The memo said all teams and geographies. Refolk's index on Cloudflare's ops, finance, and legal titles shows the obvious headcount distributed across Austin, Seattle, Singapore, and the UK in sampled profiles. Singapore and London-based measurers are particularly underbid right now because most US-focused recruiters do not have them in their default search. If you're staffing a global finance org or a UK/EU compliance hire, the Cloudflare cut just gave you a candidate pool nobody else is competing for through Q3.
This also matters for severance math. UK and Singapore notice and statutory periods stack on top of the Cloudflare package in some cases. The runway for non-US alumni can extend even longer than December 31, which pushes the conversion window for those candidates into Q1 2027. Time them accordingly.
## The "ex-Cloudflare seller" signal trap
One more pool hygiene note. Quota-carrying sales was explicitly spared. So if an "ex-Cloudflare AE" or "ex-Cloudflare CSM" surfaces on the market in mid-2026, they are almost certainly a voluntary departure or a performance-managed exit, not part of the 1,100. Treat them as you would any other seller transition. Do not lump them into the layoff cohort in your pitch to hiring managers, because they don't signal the same way and a sharp VP of Sales will catch it in 30 seconds.
## What to actually do this week
1. Pull a clean list of the 1,100 by August. Not by title string. By "cut in May 2026, currently listing Cloudflare as previous, joined before May 7 2026." This is where [Refolk](/) saves a week of Boolean iteration on LinkedIn, GitHub, and the open web.
2. Tag every profile as Segment A (IC specialist) or Segment B (generalist) before you write a single message. Discard Segment B unless you have a specific generalist req and no better candidate pipeline.
3. Build the relationship in June through mid-August. No roles. Notes, intros, advisory invitations.
4. Hit hard the week of August 18. Equity has vested. The decision is unlocked.
5. Close in September through November with a January 5 or January 12 start date. Let them keep the severance. They will remember.
```stat
number: 600%+
label: Cloudflare internal AI adoption surge in the 3 months before the cuts
note: The 1,100 are unusually AI-literate, which matters more for where you place them than where you find them.
</stat>
The recruiters who win this cohort are not the ones who send the first message. They are the ones who send the right message in the right week. The severance window is a gift, but only if you treat it like one.
## FAQ
### When is the best time to reach out to laid-off Cloudflare employees?
The week of August 18, 2026 onward is the inflection point. Equity vests through August 15, so candidates have visibility into their final RSU tranche and can rationally evaluate new equity offers. Outreach before mid-August competes with eight months of paid runway and converts poorly. Outreach in September through November, pitched against January start dates, lets candidates keep their full severance and benefits and converts at multiples of summer outreach.
### Are all 1,100 Cloudflare layoff victims worth sourcing?
No. The "measurer" pool splits into IC specialists (senior FP&A, revenue recognition, SEC counsel, technical accounting, internal audit) and generalists (director of ops, chief of staff, generalist program managers). The IC specialists are scarce, valuable, and uniquely suited to pre-IPO finance teams and AI back-office startups like Ramp, Brex, Pilot, and Harvey. The generalists were cut because the role compressed under AI, and competing employers are flattening the same layer, so the market for them in Q4 2026 will be saturated.
### Does Cloudflare's severance package really run through December 31, 2026?
Yes, per the May 7 blog post co-signed by Matthew Prince and Michelle Zatlyn. The package includes full base pay through year-end, US healthcare through year-end, and equity vesting through August 15 including a waived one-year cliff. Cloudflare disclosed $140 to $150M in restructuring charges to the SEC, with the plan substantially complete by end of Q3 2026. For a May-cut employee, the eight-month runway is roughly double the US average severance length.
### Should I treat ex-Cloudflare sales candidates the same as the 1,100?
No. Quota-carrying salespeople were explicitly spared in the cuts. Any ex-Cloudflare AE, AM, or quota-carrying CSM on the market in 2026 is almost certainly a voluntary departure or a performance-managed exit, not part of the layoff. Conflating the two pools in your pitch to hiring managers signals carelessness. Source them as you would any other seller transition, and keep them in a separate pipeline from the measurer cohort.