Cloudflare's Aug 15 Cliff: 1,100 Alumni With Cash Through December
Cloudflare's first mass layoff hands recruiters 1,100 alumni with eight months of pay and an Aug 15 vesting cliff. Here is how to source them before July.
On May 7, 2026, Cloudflare announced the first mass layoff in its 16-year history: 1,100 people, roughly 20% of headcount, on the same earnings call where revenue hit a record high. The severance terms are unusually generous, which means the real recruiter deadline is not the layoff date. It is August 15, when accelerated equity vesting shuts off.
If you are sourcing this cohort, the calendar matters more than the headline. Here is how to read it.
The terms create a two-window sourcing problem
Cloudflare is paying full base salary through end of 2026, covering US healthcare through December 31, and accelerating equity vesting through August 15, 2026, with one-year cliffs waived and pro-rated vesting through that date. That is roughly eight months of paychecks, eight months of insurance, and a few extra months of stock for over 1,000 people.
For context, Snap offered four months of severance for its 1,000-person layoff the prior month, and that was considered generous. Cloudflare is offering double.
That severance creates two distinct sourcing windows, and most recruiters are only going to see the second one.
The first window opens now and runs to roughly mid-July. Top candidates who want their next signing grant or refresh to overlap with the Cloudflare vesting tail will sign by then. They are not panicked. They are picky. Outreach in this window competes on narrative and equity, not on speed.
The second window opens around August 15 and lasts through the fall. This is the scramble. The vesting tap shuts off, the LinkedIn feed fills with "open to work" banners, and inbound applications start landing on the wrong jobs. The candidates who waited are still strong on paper, but the selection has thinned.
If you only show up in window two, you are sourcing leftovers from a sale that ended a month ago.
Ignore the front-line. Prince told you who got cut.
CEO Matthew Prince did something unusual on the earnings call. He told the entire market which functions were spared and which were not. Quota-carrying salespeople and code-writers were spared. Everyone supporting them was on the table.
CFO Thomas Seifert confirmed the cuts span all teams and geographies except quota-carrying salespeople. The CA EDD WARN notice for the 224 San Francisco layoffs names the departing leaders, and the list is consistent with that framing: CIO Mike Hamilton (in role since March 2024), chief cyber solutions officer Ramy Houssaini (since December 2024), and VPs of procurement, product and solutions marketing, product-led growth, Americas field marketing, corporate marketing, and demand generation.
The actual sourceable list skews toward:
- Marketing operations and demand generation
- Product marketing and solutions marketing
- Procurement and corporate functions
- Customer support and success
- Internal recruiting
- Senior IT and security leadership
If you are spamming Cloudflare AEs and Workers engineers, stop. They are still on payroll and they know it. The recruiters who win this cohort are the ones who reframe sourcing around the roles AI replaced internally, because those people have seen agentic workflows up close from the operations side.
This is the part where plain-English search beats Boolean. "Find me ex-Cloudflare product marketers in the Bay Area who shipped developer-tooling launches in the last two years" is a query you can paste into Refolk and get a ranked shortlist for. Building the same query in a traditional ATS sourcing module is a 20-minute exercise in keyword guessing.
The financial profile flips the usual outreach script
Most laid-off candidates are sourcing from a position of weakness. Eight months of base pay plus healthcare changes that math entirely. These candidates can absorb equity-heavy seed and Series A offers without immediate cash pressure.
That is the opposite of the usual post-layoff profile. It also means founders and early-stage operators should be the loudest voices in their DMs, not late-stage talent teams trying to backfill a req with a "safe" hire.
For eight months, ex-Cloudflare staff get to choose like they are still employed. After August 15, they choose like everyone else.
The pitch that works in window one is not "we have an open role." It is "you have runway, here is a bet worth taking with it." Anchor on equity terms, founding-team scope, and the specific thing about your product that benefits from someone who watched a profitable infrastructure company replace its own support layer with agents.
The "AI made my job obsolete" framing followed every laid-off Cloudflare employee onto LinkedIn the moment Prince said it. Recruiters who position the next role around AI-native rebuilding ("you have seen agents do this work, now build the company that productizes it") will outcompete generic "you'd be a great fit" pings by an order of magnitude. This is one of the cleanest examples of agentic AI layoffs hiring becoming a positioning exercise rather than a pipeline exercise.
The Prince list is a sourcing signal, not a sourcing plan
On X, investor Mikael Pawlo suggested Cloudflare publish an opt-in webpage with LinkedIn links to laid-off staff. Prince replied "That's the plan."
If it ships, it becomes one of the most efficient candidate databases of 2026. Bookmark it, scrape it, build a campaign around it.
If it does not ship, or ships partial, you need your own index. Cloudflare did not comment on how the cuts affect roughly 120 Australian staff or the company's plan to hire more than 1,100 interns in 2026. The WARN filing covers 224 San Francisco roles. That leaves a large remainder distributed across geographies, with no central public list.
This is the use case Refolk was built for. You describe the person in plain English (function, seniority, prior employer, geography, recency) and you get a list. For Cloudflare layoffs sourcing specifically, the query writes itself: ex-Cloudflare, the right function, the right geography, currently signaling availability.
As an order-of-magnitude check, Refolk's index currently returns roughly 1,197 US-based profiles matching Cloudflare-affiliated headlines, concentrated in the Bay Area, with notable seniority bands (Principal Systems Engineer, Sr. Director of Engineering Storage & Databases, Head of Solution Engineering, CRO). That is the reachable surface area before the company-published list ships, and it is bigger than most recruiters assume.
Tactful outreach beats fast outreach this month
Strauss Borrelli PLLC opened a WARN Act investigation on May 12 examining whether Cloudflare failed to provide the legally required 60 days' notice for the 224 San Francisco layoffs. That matters operationally because some portion of this cohort is talking to lawyers. Cold outreach that opens with "saw the news, congrats on the layoff" lands badly when the candidate is mid-conversation with counsel about whether the notice was lawful.
The outreach pattern that works:
- Do not lead with the layoff. Lead with a specific piece of their work.
- Acknowledge the runway explicitly. "I know you are not in a hurry" disarms the typical recruiter-vs-candidate dynamic.
- Pitch the August timeline, not the May timeline. Top candidates are pacing themselves.
- If you are early-stage, lead with equity. The cash floor is already set by Cloudflare.
This is also a moment where sourcing tooling either helps you or actively hurts you. Bulk-templated InMails to anyone with "Cloudflare" in their headline will burn the cohort fast. Targeted, role-specific, geography-specific outreach to the right 30 people will not. Tools that let you express that targeting in plain English (the Refolk pitch, "Find anyone. Just ask.") collapse the time from "I think there is a pool here" to "here are the 30 names" to about a coffee break.
The wave is bigger than Cloudflare
Cloudflare is the flagship of a single-week event, not a one-off. The same week, PayPal cut 4,760, Coinbase cut 700, Freshworks cut 500, Arctic Wolf cut 250, and Ticketmaster cut 350, mostly with AI framing. From January through April 2026, US tech employers announced 85,411 job cuts, up 33% year over year per Challenger, Gray & Christmas.
That means the Cloudflare 1100 layoff list is not the whole pool. It is the highest-quality concentrated slice of a much larger supply. Recruiters who build a Cloudflare-specific campaign should plan the same campaign against PayPal's Braintree middle, Coinbase's killed manager layer, and Freshworks' support org. The narrative ("you have runway, the next role is AI-native rebuilding") ports cleanly across all five.
The mistake is treating each layoff as its own one-week news cycle. Treat them as a unified pool of high-pedigree alumni with varying severance terms, and sequence outreach by which cliff lands first. Cloudflare's August 15 is the earliest meaningful one in the wave.
What to do this week
Three concrete moves before the end of May:
- Build the named list. Pull every Cloudflare alum in your target function and geography. Use the WARN filing as a seed, then expand. If you are using Refolk, this is one query.
- Segment by window. Tag the cohort into "wants to sign by mid-July" and "will look in September." Different outreach, different cadence.
- Write the equity-first pitch. If you are pre-Series B, your pitch is the offer letter, not the job description. Have it ready when window one opens.
The Cloudflare severance recruiting story is going to get retold every August between now and 2030 as the cautionary tale of "we waited and the good ones were gone by July." Do not be the firm that retells it.
FAQ
How many of the 1,100 Cloudflare layoffs are engineers?
Prince explicitly excluded code-writers and quota-carrying salespeople from the cut, and CFO Thomas Seifert said the cuts span all teams and geographies except quota-carrying sales. The departing leaders named in the SF WARN-derived reporting are heavy in marketing, procurement, and corporate functions, plus senior IT and security leadership (CIO Mike Hamilton and chief cyber solutions officer Ramy Houssaini). Expect the engineer share to be small and weighted toward platform, IT, and internal-tooling roles rather than product engineering on Workers or the data plane.
When is the right time to reach out to laid-off Cloudflare staff?
Now, if you want them to sign by mid-July and overlap their next equity grant with the August 15 vesting tail. The first sourcing window runs from May through early July. The second opens after the August 15 cliff and runs through fall, but the pool will be thinner and the competition louder. If you are an early-stage company offering equity, window one is dramatically better.
Will Cloudflare actually publish a list of laid-off staff?
Prince replied "That's the plan" to investor Mikael Pawlo's suggestion of an opt-in webpage with LinkedIn links. Whether it ships, and how complete it is, is unknown as of mid-May 2026. Treat it as upside, not as your sourcing plan. Build your own index of ex-Cloudflare profiles by function and geography in parallel, so you are not waiting on a company-published page that may cover only a fraction of the 1,100.
How should I word outreach given the active WARN Act investigation?
Tactfully and without leading with the layoff. Strauss Borrelli PLLC opened an investigation on May 12 covering the 224 San Francisco roles, which means some candidates are in active legal conversations. Lead with specific past work, acknowledge the runway, pitch a timeline that respects their pacing, and skip "congrats on the new chapter" framing entirely. The candidates with the strongest options are the ones who will react worst to templated outreach.