Bending Spoons' 75% Rule: Airtable's ~200 Engineers Have 5 Days

On October 12, 2026, Airtable's new product lead posted that affected employees would exit by end of week with substantial separation packages. Five weeks after Bending Spoons closed the $1.285B deal, that cadence matches WeTransfer, not Vimeo. If you want ex-Airtable engineers before they sign somewhere else, you have days, and the window closes in a specific order.

The number nobody is publishing: ~200 engineers out by Friday

Airtable has not disclosed a headcount, but Bending Spoons' own history makes the math defensible. Against Airtable's roughly 270 engineers and 900 total staff, the WeTransfer precedent of 75% implies around 200 engineers and 675 total employees separated by end of week.

Bending Spoons has done this four times publicly. Each deal has a headcount, a cut rate, and a cadence you can read off the record:

The WeTransfer cut landed within weeks of close. Vimeo's deeper cuts arrived at month four. Airtable's five-week timeline sits inside the WeTransfer envelope, which is why treating this week's cohort as the main wave, rather than waiting for a bigger second wave, is the correct bet.

~200

Why this exit pool is unusually clean to source

The Bending Spoons Airtable acquisition is not a routine RIF, which is why the exit pool is unusually clean to source. Separation packages mean the people leaving are not scrambling, and the acquirer's own product leader has publicly invited recruiters in.

Federico Simionato, Bending Spoons' product leader, wrote: "To everyone leaving: thank you. If you're hiring, these are excellent people and worth a call." That is, functionally, a permission slip. Outbound to this cohort does not need to be delicate about the layoff frame. You can reference it directly.

Three mechanics make this pool unusually liquid:

1. Severance decompression. Candidates with packages typically take two to four weeks before accepting calls, then move fast. Reach out during the exit window, close after. The dead zone is weeks two through six.
2. Public invitation to recruit. Simionato's post removes the usual delicacy around outbound to a laid-off cohort.
3. Finite inventory. Airtable's eng org has been visible on GitHub, conference talks, and the engineering blog for years. The identifiable surface area is small enough to touch exhaustively.

What "exhaustively" actually means here

In Refolk's index, a focused search on current and recent Airtable technical and PM staff surfaces 177 identifiable profiles, with 10 currently tagged at Airtable in the top sample. The dominant geographies are the San Francisco Bay Area, Brooklyn, and NYC. A single sourcer, working a normal day, can touch every one of them inside 72 hours.

That is the entire game this week. Not "build a long list." Touch the finite list before Anthropic does.

177

The highest-value profiles inside the 200

The engineers worth prioritizing are the ones who built pre-AI Airtable: real-time collaboration, database internals, and infra. Bending Spoons uses AI for more than 90% of its code writing, product design, and hiring, which means the cuts fall disproportionately on senior ICs whose leverage sat in human-written systems.

Rank the pool by what Bending Spoons' operating model makes redundant:

• Real-time collaboration engineers. Airtable's live-cursor and shared-view machinery is a known hard problem, and Figma treats this profile as a direct signal.
• Database internals and query engine ICs. Airtable's cell-level permissions and formula engine are closer to a database than a spreadsheet.
• Platform and API engineers. Airtable's extension and automations surface is one of the larger public no-code APIs.
• Senior PMs on the data-platform side. Bending Spoons collapses PM-to-engineer ratios first; Refolk's sample shows PMs as the #2 title cluster in the Airtable pool. Founders hiring their first PM should prioritize this list before the ICs.
• Ex-Airtable founders in motion. The Refolk sample surfaces "Co-Founder & CTO" entries at small shops like Amutable and Mitable. Ex-Airtable people start no-code and database-adjacent companies; expect to lose a non-trivial share of the top-tier IC crowd to self-employment inside 60 days.

Waiting for a bigger second wave at Airtable is a losing bet. Act on this week's cohort as if it is the main event.

The adjacent destinations already showing up in the index for ex-Airtable talent are Google, Meta, Anthropic, and Figma. Those are the four companies you need to out-move this week. If your pitch cannot beat an Anthropic phone screen, start with the PM and real-time collab clusters where Anthropic is less active.

The 72-hour sourcing playbook

The playbook for sourcing Airtable engineers this week is three passes, in order, on the same 177-profile list. Depth beats breadth because the list is finite.

Pass 1: the ten still tagged at Airtable (Monday)

Ten profiles in Refolk's sample still carry Airtable as their current employer. These are the people who have not yet updated LinkedIn, which means either they are among the retained minority or they are fresh exits who have not posted anything yet. Reach out before they post. First-touch messages that land before the "Open to Work" banner get materially higher reply rates because the inbox is not yet saturated.

Pass 2: the ex-Airtable alumni by cluster (Tuesday to Wednesday)

Work the 167 ex-Airtable profiles by title cluster, not alphabetically. Real-time collab first, database internals second, platform third, PM fourth. The cluster matters because your pitch changes per cluster, and the candidate's next-best alternative changes per cluster.

This is the exact workflow Refolk is built for: you describe the person in plain English and get back a ranked shortlist across GitHub, LinkedIn, and the open web. No Boolean, no scraping, no manual deduplication across sources.

Pass 3: the founders and the quiet exits (Thursday to Friday)

The last pass is the hardest and the most valuable: ex-Airtable people who already left during the uncertainty window between the August 4 announcement and the September close. These profiles are not tagged "ex-Airtable (October 2026)." They are tagged with a current startup, a stealth entry, or a sabbatical. GitHub archaeology on Airtable's open source repos, conference talk dates, and early-stage investor announcements surfaces them. This is where ex-Airtable candidates become hires rather than conversations.

Where this cohort is likely to land

The most probable landing spots are Anthropic, Figma, Google, and Meta, plus seed-stage no-code startups. That ordering is driven by what the Bending Spoons AI-code mechanic has already filtered out, not by prestige.

• Anthropic absorbs infra and real-time ICs faster than anyone, and already shows up in the ex-Airtable destination data from Refolk's index.
• Figma treats Airtable tenure on multiplayer systems as a direct signal.
• Google and Meta will backfill through recruiters' existing pipelines; they move slowest but offer the biggest TC packages.
• Seed and Series A no-code and database startups absorb the founder-track exits. Nalden, WeTransfer's co-founder, publicly criticized Bending Spoons in December 2025 and announced a competing file-transfer service. Expect at least one or two ex-Airtable co-founders to do the same by end of Q1 2027.

If you are a founder hiring your first senior IC or your first PM, the arbitrage is here, this week, before Anthropic's recruiting coordinator can get a loop scheduled. Post-acquisition layoff sourcing almost never produces a cleaner pool: liquid candidates, public permission to recruit, finite inventory, and a named list of competing destinations.

What to do if you miss Friday

If you miss the end-of-week window, the next useful date is roughly end of November, after severance decompression ends. The dead zone between is real, but it is also the window where quiet pipelining pays off.

Three things to do in the dead zone:

1. Build the full 177-name list now. Even if you cannot send, having the deduplicated list ready for week six beats rebuilding it then.
2. Track GitHub activity. Ex-Airtable engineers who start committing to personal repos or small OSS projects in weeks two through four are the ones not pursuing stealth founder paths. They are reachable.
3. Watch conference CFPs. Database and real-time systems venues are where this cohort surfaces publicly before updating LinkedIn.

The deeper point of the Bending Spoons Airtable acquisition for recruiters is not that Airtable happened. It is that Bending Spoons has publicly committed to roughly 1,000 more acquisitions. The 75% rule is a repeatable sourcing event. Learn to read it fast, because the next one is already being negotiated.

FAQ

How many Airtable engineers are actually being laid off in October 2026?

Airtable has not disclosed a number, but Bending Spoons' precedent at WeTransfer was 75% of staff cut within weeks of close. Against Airtable's roughly 270 engineers and 900 total staff, that implies around 200 engineers and 675 total employees out by end of week. The upper bound, if the deal follows the Vimeo pattern instead, is closer to 240 engineers, though the five-week cadence matches WeTransfer more closely than Vimeo.

Will severance packages make these candidates harder to reach?

Severance makes candidates less desperate, not less reachable. The practical effect is a two-to-four-week decompression window during which they will take warm intros but delay accepting offers. Reach out during the exit week itself, when inboxes are not yet saturated and the news is fresh, then plan to close in week six. The dead zone is weeks two through six, so pipeline-build without aggressive follow-up during that gap.

What's the single highest-value profile in the ex-Airtable pool?

Senior ICs who worked on Airtable's real-time collaboration layer or the formula and query engine. Both are hard engineering problems with few public training grounds, and both map to active hiring at Figma and Anthropic. Bending Spoons' AI-code operating model specifically removes human leverage from these systems, which is why these ICs are disproportionately in the cut pile.

How do I source ex-Airtable candidates without a dedicated sourcing team?

Work from a finite, deduplicated list rather than running Boolean searches across three platforms. The identifiable technical and PM surface is roughly 177 profiles, small enough for one person to touch exhaustively in 72 hours. A plain-English query ("ex-Airtable backend engineers, real-time or database internals, SF or NYC, left in the last 90 days") returns a ranked shortlist across GitHub, LinkedIn, and the open web in one pass, which is the only workflow that fits inside a five-day window.