Cloudflare Fired 1,100 Measurers. The 586 Engineers Aren't the Prize.
Cloudflare's May 2026 restructuring added ~586 engineers and displaced 1,100 measurers with paid runway through year-end. Here's the real sourcing list.
On May 7, 2026, Matthew Prince did something most CEOs would never do: he published the org chart in reverse. He told the world exactly which 1,100 Cloudflare employees had just been declared obsolete, called them "measurers," and then, in the weeks that followed, quietly added about 586 engineers on top of the 1,308 already in the building. If you source technical talent for a living, this is not a news story. It is a target list with names on it.
The BNP Paribas LinkedIn read, first surfaced by Business Insider and reviewed by Prince himself, puts Cloudflare engineering at 1,894 people as of late June 2026, up 45% in a matter of weeks. That number matters. What matters more is the 1,100-person shadow list of finance analysts, internal auditors, compliance leads, RevOps managers, and middle managers now sitting at home with full base pay through December 31.
What Prince actually said, and why it changes your sourcing
Prince's framework, laid out in the WSJ op-ed and echoed in the Q1 call, sorts every Cloudflare employee into three buckets. Builders make the product: engineers, designers, PMs, security researchers. Sellers carry quota. Measurers, in his own words, work in middle management, finance, legal, internal auditing, and revenue recognition, plus a "significantly reduced" marketing team. CFO Thomas Seifert confirmed on the earnings call that the cuts hit every team and geography except quota-carrying salespeople.
That is unusually specific language from a public-company CEO. It is also, functionally, a public sourcing memo. Prince has told competitors: here is the list of functions I no longer value. Anyone building a finance, compliance, or marketing ops team over the next 90 days should have Cloudflare alumni at the top of a spreadsheet by end of week.
Why the 586 engineers are the harder target
The engineers are the loud number, so let's start there. Cloudflare didn't just add 586 headcount. It absorbed nearly a million applications for 1,111 paid summer internships in 2026, and every intern hired was tagged Builder or Seller. This is a company that is currently the most oversubscribed engineering destination on the internet, running Q1 revenue of $639.8M (up 34% YoY) and posting record numbers while cutting 20% of staff.
Poaching from Cloudflare engineering right now is expensive. The stock is behaving, the internal AI usage grew "more than 600% in the last three months" per Prince, and the people who just got hired chose Cloudflare over roughly 900 other options. If you go after them, go after them narrowly.
Segment the 1,894, don't scrape it
The mistake most sourcers will make this quarter is running a single LinkedIn search for "Cloudflare engineer" and blasting a template. The 586-person surge is not one market. It is at least four.
Workers Runtime and Edge. C++, Rust, and WebAssembly on the platform that runs V8 isolates at the edge. The active job posts in Austin explicitly name this stack. These are systems engineers with a very specific taste for low-level performance work. They are hardest to source and hardest to close. Look for GitHub contributions to workerd, V8, or WASM tooling before you touch InMail.
Developer Platform. TypeScript and Go, building the surface area customers actually see. Broader labor pool, faster to close, more responsive to product mission pitches.
AI infrastructure. The vector DB team hiring in Austin is a distinct sub-org with a distinct candidate pool. These are people who could equally sit at Pinecone, Turbopuffer, or Chroma. Cross-reference contributor lists.
Security research. Prince lumps this into Builders, but the hiring pipeline is completely different. Con talks, CVEs, and bug bounty leaderboards, not GitHub stars.
Running four searches instead of one is the difference between a shortlist and a spam campaign. This is one of the friction points that pushed us to build Refolk: you describe the person in plain English ("Rust engineer in Lisbon with Workers Runtime or V8 experience, contributing to WASM projects in the last 12 months") and get a ranked shortlist across GitHub, LinkedIn, and the open web, without stitching together five Boolean strings.
The real prize: 1,100 measurers with a paid runway
Here is the part most technical recruiters will skip because it isn't engineering. Do not skip it.
Prince's severance design is unusually generous: full base pay through the end of 2026, plus healthcare and equity vesting. Someone laid off on May 7 has almost eight months of paid runway before they need to sign anything. That changes the shape of the candidate pool entirely.
Most layoff cohorts source badly because the strong candidates get scooped in week one and the rest turn desperate by week six. Cloudflare's cohort is different. The strong candidates are taking their time. They will interview in July, take August off, and start closing offers in September and October. Any competitor who runs a normal "hit them in week one" cadence will miss the top half of this list.
Cloudflare's severance design is a sourcing weapon against them, and the window closes in October.
If you run RevOps, FP&A, internal audit, compliance, or marketing operations hiring for anyone in the Cloudflare talent radius (Austin, SF, NYC, Lisbon, London, Bengaluru), this is the cleanest non-desperate candidate pool of 2026. These people passed the Cloudflare bar in 2022 and 2023 when the bar was high. They were not fired for performance. They were reclassified.
Read the geography, not the headline
The Refolk index of profiles with Cloudflare in current or recent history skews to Lisbon (largest non-US engineering density), Greater Seattle, London, Austin, and outposts like Aachen, Germany, matching Cloudflare's stated hub map of SF, Austin, NYC, Lisbon, London, and Bengaluru. Lisbon is the interesting one. Cost of living is a fraction of the Bay, English proficiency is uniform, and the engineering talent density there is under-indexed by US-based sourcers. If you are a European AI infra startup with an EU-time-zone requirement, Lisbon is a two-week sprint, not a quarter-long project.
This is not just a Cloudflare story
GitLab did the same thing in May 2026. CEO Bill Staples cut ~7% of staff, stripped up to three layers of management, and reorganized engineering into 60 autonomous teams. Different vocabulary ("agentic era"), same restructure: concentrate builders, thin measurers, flatten management.
The Cloudflare vocabulary and the GitLab vocabulary are both leading indicators. When a public-company CEO's letter uses the words "flatter," "fewer layers," "consolidated operations," or "agentic," you have roughly a 90-day window before headcount changes hit LinkedIn. TrueUp's wider labor read backs this up: open technology roles are up 14% YoY in 2026, hardware engineering openings are up 52%, and ops, HR, and general management postings are declining.
Anyone sourcing seriously in the AI-era layoffs technical recruiting environment should be doing two things right now. First, maintaining a running list of CEO letters and 10-Qs that use the builders-sellers-measurers vocabulary or its equivalents. Second, having a sourcing plan ready to fire the day the layoff hits, because the good candidates are gone in three weeks.
The contrarian read
Marc Andreessen, on 20VC, argued that most large companies are structurally overstaffed and AI is now the convenient "silver bullet excuse" to cut what should have been cut anyway. Chamath Palihapitiya criticized Prince's memo for its class-warfare framing. Both critiques matter for sourcing.
If Andreessen is right, then the 586 engineering adds aren't a real reallocation. They are a story Prince is telling investors while the actual restructuring is a straight cost cut disguised as an AI reorg. In that case, the 586 number will drift back down in Q3 and Q4 as the internal AI-productivity narrative meets reality. Sourcers should track this. If Cloudflare engineering headcount is still climbing in October, the builders-vs-measurers framework is real and every other CEO will copy it by year-end. If it plateaus at 1,894 or drops back, the whole thing was AI-washing and the "builders concentrate" language will quietly disappear from earnings calls.
Either way, the 1,100 measurers are already gone, they have paid runway through December, and they are the cleanest quality-adjusted candidate pool on the market this summer.
What to do this week
If you're a founder or engineering leader trying to hire before Q3:
- Run four separate searches on Cloudflare engineering, not one. Workers Runtime (C++/Rust), Developer Platform (TS/Go), AI infra, security research. Different pitches, different close cycles.
- Prioritize Lisbon and Austin before you touch SF. Density is higher, competition is lower, close rates are better.
- Build a parallel list for the 1,100 measurers. RevOps, FP&A, internal audit, compliance, marketing ops. Reach them in July, expect closes in September.
- Set a Google Alert on "flatter," "fewer layers," and "agentic era" in earnings transcripts. GitLab is not the last one.
If you want to compress steps 1 through 3 into an afternoon, this is exactly the workflow Refolk was built for. You describe who you're looking for in plain English (including negative constraints like "not currently interviewing with Vercel or Fly"), and Refolk pulls the shortlist across GitHub, LinkedIn, and the open web. The measurer pool in particular is one where speed matters, because the top of the list will close between August and October and won't be visible after that.
Prince did the segmentation for you. The only question is which half of his framework you're going to move on first.
FAQ
Is the 586 engineering number from Cloudflare or from LinkedIn?
Neither, technically. The 1,308 to 1,894 figure comes from BNP Paribas analysts using LinkedIn profile data, first reported by Business Insider. Prince reviewed and confirmed it, but Cloudflare has not filed it in a 10-Q. Treat it as a directional sourcing signal, not a payroll fact. Title changes on LinkedIn can lag and over-count, especially when a company publicly redefines its own job categories the way Cloudflare just did.
Are the laid-off Cloudflare measurers actually good hires, or just cost cuts?
Prince and Seifert were explicit that the cuts were not performance-based. They were function-based: entire categories of work that Cloudflare now believes AI can absorb. That means the individual quality bar is closer to Cloudflare's 2022-2023 hiring bar than to a typical layoff cohort. For finance, compliance, and RevOps roles at similar-stage companies, this is arguably the cleanest candidate pool of the year, and the paid-through-December severance means the strong ones aren't panic-signing.
How do I read the "builders sellers measurers layoffs" signal at other companies?
Watch CEO letters, earnings transcripts, and internal all-hands leaks for vocabulary like "flatter," "fewer layers," "consolidated operations," "agentic," or explicit builder/seller framing. GitLab in May 2026 ran the same play with different words. TrueUp's data shows ops, HR, and general management postings declining broadly across tech in 2026, while hardware engineering openings are up 52%. The pattern is now industry-wide, not Cloudflare-specific.
What's the best way to poach Cloudflare engineers on LinkedIn right now?
Don't lead on LinkedIn. Cloudflare engineers are the most InMailed group on the platform this quarter. Lead on GitHub, conference talks, or mutual connections in Lisbon and Austin, then move to a warm channel. Segment by team (Workers Runtime, Developer Platform, AI infra, security research), pitch to the specific technical problem they've been solving, and skip the "we're a fast-growing startup" opener entirely. If you can name their last three PRs, you're already ahead of 95% of the inbound they're getting.