Cloudflare's 1,100 Have 30 Weeks of Runway. Your Pitch Has 30 Seconds.
Cloudflare's 1,100 layoffs come with pay through 2026. Here's the 6-month sourcing playbook for ex-Cloudflare edge and security engineers.
On May 7, 2026, Cloudflare announced it was cutting 1,100 people, roughly 20% of its workforce, and handed them one of the most generous severance packages in tech history: full base pay through December 31, healthcare through year-end, and equity vesting through August 15. The stock fell 18% the same day. If you run sourcing, you already know what this means: a thousand-plus edge, security, and systems engineers are about to hit the market with no financial pressure to take your offer.
That last part is the whole game. Every post-layoff playbook you have ever run assumes 8 to 12 weeks of runway and a candidate doing math on their savings account. This cohort has 30+ weeks. Move at your normal speed and you will look desperate. Move at theirs and you will close people other recruiters never even reach.
Why the standard post-layoff playbook breaks here
The typical layoff sourcing motion looks like this: pull the LinkedIn "Open to Work" green banners, blast a templated "saw the news, we move fast" sequence, get on calls within a week, push for a verbal in two. It works because severance is short and COBRA is expensive. The candidate's clock is your leverage.
Cloudflare just deleted that clock. Per the company's own filing, cash expenses for notice, severance, and benefits run $105M to $110M, plus another $35M to $40M in non-cash accelerated equity vesting. That is roughly $130K per departing employee in cash alone, on top of base pay continuing through December. A senior engineer making $250K base is collecting paychecks until the snow melts.
So the "we move fast" pitch lands as a red flag, not a feature. It signals that you need them more than they need you, which inverts the dynamic you actually want.
Severance this generous turns urgency into a tell. The recruiters who slow down will close the people the fast ones scared off.
The real deadline is August 15, not December 31
Read the severance terms carefully. Equity vesting stops on August 15, 2026. That is the date that actually changes the financial calculus for any tenured Cloudflare engineer with meaningful unvested RSUs. Severance pay is a floor, but the equity cliff is the ceiling on staying out of the market.
Recruiters who plant seeds in May and June, run technical deep-dives in July, and have offers ready the week of August 11 will convert. Recruiters who show up in October will be competing with everyone else who finally figured out the calendar.
What got cut, and what didn't
CEO Matthew Prince was unusually specific on the earnings call: "We have seen that there are roles at Cloudflare that are not the roles we need for the future... a lot of the support roles behind them are not going to be the roles that drive companies going forward." Internal AI usage at the company jumped more than 600% in the last three months alone, which is the framing he used to justify the cuts.
Translate that and you get a clear read: sales ops, recruiting, HR, finance ops, marketing ops, and likely a chunk of QA and program management took the heaviest hits. Customer-facing engineers and infrastructure ICs were largely spared. Which means two things for sourcing ex-Cloudflare engineers:
- The 1,100 list is engineer-light relative to the company's overall ratio. The actual engineering bleed is smaller than the headline.
- Survivor's guilt and uncertainty about the next round will quietly open up the engineers who weren't cut. They are the bigger prize, and they don't show up on any "Open to Work" filter.
The "we hire humans" counter-pitch
Cloudflare publicly told 1,100 people they weren't needed for the future. That is a brand wound, and infrastructure startups, security firms, and AI infra companies should press on it. The pitch writes itself: "The edge and security problems we work on don't compress under AI. We are hiring humans because the work is harder, not easier."
This lands especially hard with senior systems engineers who spent years building Pingora-class infrastructure and don't love being told a Claude prompt could do their job.
Where the engineers actually are
If you are running a Cloudflare layoffs 2026 sourcing project, the LinkedIn "ex-Cloudflare" filter is the obvious starting point and the worst one. Everyone has it. Within 72 hours, every senior engineer with a clean profile will be sitting on 40+ inbound messages, and the templated ones will be deleted unread.
The better surfaces are the ones tied to the actual work:
- Pingora contributors on GitHub. Pingora is the Rust HTTP proxy framework Cloudflare built to replace Nginx. Its open-source repo is a public list of the systems engineers who actually shipped it. Pull the commit graph, cross-reference against current and former Cloudflare email domains, and you have a sourcing list nobody else is working from.
- quiche contributors. Cloudflare's QUIC implementation. Same logic. Smaller list, higher signal.
- Workers ecosystem. The Cloudflare Workers Discord, r/CloudflareWorkers, and the "Built with Workers" showcase surface engineers who built on the platform, including ex-employees who kept shipping personal projects on it.
- QUIC working group mailing list and CNCF edge-computing SIG. Niche, but the people on these lists are the actual edge-protocol experts, not generalists with "edge" in their headline.
The hard part isn't knowing these surfaces exist. It is stitching them together. A GitHub handle, a LinkedIn profile, a Discord username, and a personal blog rarely share an obvious key, and doing this match by hand for 1,100 candidates is a non-starter.
This is the friction we built Refolk to remove. You describe the person in plain English, "ex-Cloudflare systems engineer who contributed to Pingora or quiche, based in SF, London, or Lisbon," and get a ranked shortlist that pulls from GitHub, LinkedIn, and the open web together. No 1,000-result LinkedIn cap, no hand-stitching identities across surfaces.
Don't sleep on Lisbon
Cloudflare's engineering footprint in Lisbon is real and underweighted in most sourcing plans. The standard SF/NYC/London lanes will be crowded within a week. Lisbon engineers cost less, face less competition from FAANG, and are well-suited to remote-first edge and security teams. If you are hiring edge computing engineers and your geo filter stops at "Europe, English-speaking," widen it.
The 6-month courtship, week by week
Here is the actual cadence for a post-layoff sourcing playbook tuned to this severance package.
May to June: introduce, don't pitch
First-touch outreach should not contain a job description. The goal is a 30-minute conversation about what they actually want to build next. Reference their work specifically (a Pingora PR, a Workers project, a conference talk on V8 isolates) and offer a low-stakes call. The single most effective opening line right now is some version of: "Not pitching a role. Curious what you'd want to work on if you took the next year to pick carefully."
This works because it is true to their situation. They have a year. Pretending otherwise insults them.
July: technical deep-dive
By mid-July the financial fog has cleared, the summer travel is winding down, and the August 15 equity cliff is suddenly close. This is when you bring the engineering team in, not the recruiter. A two-hour architecture conversation with your CTO about, say, how you handle sub-1ms cold starts without V8 isolates is worth ten recruiter calls.
This is also when sourcing Cloudflare Workers talent gets competitive. Workers expertise commands rates 10 to 20% above general serverless developers in freelance markets, which is a useful comp benchmark for full-time offers. If you are pricing a Workers-fluent engineer at the same band as a generic AWS Lambda dev, you will lose them.
Early August: offer in hand by the 11th
The equity cliff is August 15. You want a written offer, with comp, equity, and start date, in their inbox by Tuesday August 11. Not "we'd like to make you an offer, let's schedule a call." The actual document. The candidates who are going to take a role before the cliff will decide that week, and the offers that are already concrete will win against the ones that are still being drafted.
September to December: the long tail
A meaningful share of this cohort will sit out until late fall. They have the runway. Don't let them go cold. A monthly check-in, an invite to a small dinner, a thoughtful share of relevant news. The candidates who say "not yet" in June and "still not yet" in August are often the strongest hires in November, because they have had time to evaluate carefully and self-select against the panicked options.
The competitive set you are actually fighting
Coinbase cut roughly 700 the same week. PayPal is reportedly planning 20% cuts. Meta, Block, and Oracle have all announced 2026 layoffs. The talent pool is large but so is the demand, and the companies that will move on this Cloudflare cohort fastest are predictable:
- Edge platforms: Fastly, Vercel, Netlify, Deno, Fly.io, Akamai
- Security and networking: Wiz, Snyk, Censys, Tailscale
- AI infrastructure: Anthropic, OpenAI, and the long tail of inference-at-the-edge startups
If you are one of these companies, your differentiator is not comp. Everyone is going to be in the same band. Your differentiator is the technical pitch and the timing of when you show up. Refolk helps with the first half of that, getting to the right named engineers before the obvious lists get scraped, but the patience is on you.
What to do this week
If you are running this play right now, three things matter:
- Build the named list. Not "ex-Cloudflare engineers in SF." Specific people, with specific work you can reference. Pingora, quiche, Workers, Durable Objects, R2, the QUIC stack. Cross GitHub with LinkedIn with the open web. This is exactly the use case Refolk is built for, and a plain-English query gets you further than a Boolean string.
- Draft the May-to-August calendar. Block the dates. The August 11 offer deadline is not a guideline.
- Write one non-pitch first message and test it on five people. If your reply rate isn't above 35% you have the wrong message, not the wrong list.
The recruiters who treat this like a normal layoff will burn the cohort by Memorial Day. The ones who treat it like a six-month relationship project will close hires their competitors didn't even know were available.
FAQ
How is Cloudflare's severance different from past tech layoffs?
It is dramatically more generous. Stripe's 2022 layoffs offered 14 weeks of severance. Twilio and Shopify's 2023 cuts were in a similar range. Cloudflare is offering full base pay and healthcare through December 31, 2026, plus equity vesting through August 15. That is roughly 30+ weeks of runway from the May 7 announcement, which fundamentally changes the urgency math for anyone sourcing ex-Cloudflare engineers.
Should I focus on the 1,100 laid-off employees or current Cloudflare engineers?
Both, but weight current employees higher than most recruiters will. CEO Matthew Prince's framing of the cuts ("roles not needed for the future") created real survivor's-guilt and uncertainty internally. Tenured engineers who weren't cut are quietly open in a way that doesn't show up on any "Open to Work" filter, and they tend to be stronger ICs than the laid-off cohort on average.
What's the right comp benchmark for Cloudflare Workers talent?
Workers expertise commands 10 to 20% above general serverless rates in freelance markets, which translates reasonably to full-time bands. If you're pricing a Workers-fluent engineer the same as a generic Lambda developer, you will lose the offer. Pay attention specifically to Durable Objects, R2, and Workers AI experience, which are the harder-to-find subsets within the broader Workers ecosystem.
When is the actual best time to send the offer?
The week of August 11, 2026, with a written offer in their inbox by Tuesday. Equity vesting stops on August 15, which is the real cliff, not the December severance end date. Engineers who are going to move before forfeiting unvested RSUs will decide that week, and concrete offers beat draft conversations every time.