Airtable's WARN Says 190. Bending Spoons' Track Record Says 600

In October, Bending Spoons told a "large portion" of Airtable's roughly 800 pre-acquisition staff that they would be gone by the end of the week, and Airtable still won't give a number. If you're a recruiter or an engineering leader, you don't know if you're looking at 50 people or 600, or if they're worth chasing.

My short answer: the real number is probably far above the one public filing, and the cut tells you almost nothing about how good any single person is. Below is how to size it, who to call first, and when they can actually start.

What happened at Airtable in October 2026?

Bending Spoons let go of most of Airtable's pre-acquisition team and moved its own people into newly created Core, Performance and Infra teams. Bending Spoons said the reason was team size, not performance.

The timeline:

1. The announcement. Alessandro Savarese, who now leads Airtable product development, says: "We're parting ways with a large portion of the pre-acquisition team, who will be leaving by the end of the week with substantial separation packages."
2. Oct 12. Federico Simionato, a Bending Spoons product lead, posts on X that the cut "is not a reflection of their work but a reflection of our deep belief that small teams ship more and better." The same post announces "new Performance and Infra teams focusing on speeding up bases and increasing limits on records, fields, and syncs." Fast Company covered the backlash.
3. Oct 14. A California state spokesperson confirms no WARN advisories have been filed.
4. Oct 15. A California WARN notice appears, covering 190 jobs in San Francisco County with a last day of work of Jan 15, 2027.
5. Oct 22. Strauss Borrelli PLLC says it is investigating whether Airtable failed to give at least 60 days' notice before laying off those 190 employees.

A WARN notice is filed for a specific site. That detail is why the 190 figure undercounts.

How big were the Airtable layoffs, really?

The 190 jobs on the WARN notice are a floor, not the total. If Bending Spoons followed its own track record, the real cut was more like 600 to 680 of the roughly 800 pre-acquisition staff.

The WARN filing only covers the San Francisco County facility. Remote employees who don't report to that office can fall outside it. In Refolk's index sample of Airtable engineers, 16 of the top 25 (about 64%) are based outside the Bay Area, mostly in New York and Austin. The filing can't see a big chunk of the company.

Two things move my estimate toward the high end. First, Savarese said "large portion," and nobody calls a quarter of the company that. Second, Bending Spoons doesn't do half-measures, as the next section shows. I'd plan sourcing capacity for several hundred leavers, not 190.

What is the Bending Spoons acquisition layoffs pattern?

Bending Spoons usually removes about three-quarters of an acquired company's staff soon after closing, then rebuilds the product with its own people. Airtable is the latest example, not an unusual one.

The record:

• Komoot: lost about 75% of its original staff after the acquisition.
• WeTransfer: also lost about 75%.
• Brightcove: reportedly over 85% of staff gone shortly after closing, including around 200 redundancies (that figure comes from a weaker source, so treat it as directional).
• Vimeo: layoffs in January came soon after the company had shown an ambitious roadmap.

The reason is economic, not personal. Bending Spoons runs acquired products with a fraction of the people the previous owners employed, and its own numbers show why.

$2.57M

When that's the target, the per-employee economics of an 800-person Airtable don't fit. The cut follows from the model. It isn't a judgment on the people.

Does being cut say anything about an Airtable engineer's quality?

Mostly no. The verified dividing line was the org boundary: pre-acquisition Airtable staff on one side, incoming Bending Spoons staff on the other. The stated reason was team size.

To be precise about the claim: I'm not saying Bending Spoons picked people by tenure inside Airtable. There's no evidence of that. What the evidence does support is that the cut followed which company you belonged to, not how well you performed. Simionato said as much in writing.

One more fact makes the leaver pool stronger than a usual layoff list: they already survived two rounds. Airtable laid off 254 people in December 2022 and another 237 in September 2023. Anyone still there in 2026 made it through both.

A layoff that follows the org chart tells you about the buyer's model, not the employee's work.

So treat the Airtable leaver list like any strong-company alumni list, not like a performance-managed exit list. Your normal screen still applies. The layoff just isn't evidence against anyone.

Who should you hire first from the Airtable layoffs?

Start with infra and performance engineers. Bending Spoons built brand-new Performance and Infra teams to raise limits on records, fields and syncs, which tells you the scaling work mattered. The people who held that context were the pre-acquisition engineers.

The logic: a buyer that thought Airtable's scaling problems were minor wouldn't announce two new teams for them in the same breath as the layoff. Bending Spoons decided the work was important enough to staff with its own people. That makes the outgoing engineers who knew where bases slowed down, and why the limits sat where they did, the scarcest part of the leaver pool.

Priority order I'd use:

1. Infra, SRE and performance engineers. Database scaling, sync, and the limits work Bending Spoons just took over.
2. Core product engineers on the base, field and record model, the area now covered by the new Core team.
3. Product managers and designers, a much smaller group (more below).
4. Sales and support. 274 people before the deal, but a different hiring market from this article's focus.

The Hyperagent and DeepSky caveat

Don't assume Airtable's AI-agent engineers were cut. Before signing, a reorganization moved the assets and liabilities of the Hyperagent business line into a separate entity, and Bending Spoons' $480M ARR figure came after that move. Engineers on Hyperagent, including people from the DeepSky acquisition (12 staff plus founders Chris Chang, Forrest Moret and Mark Kim-Huang), may never have been inside the company that ran the layoff.

Whether they're still at Airtable or in the Hyperagent entity hasn't been confirmed. If you contact them, ask. Don't open with "sorry about the layoff" to someone who might not have been laid off.

This is where keyword search falls apart. "Airtable infra engineer, not on the Hyperagent team, ideally in New York" isn't a Boolean string any tool handles cleanly. It is the kind of request Refolk is built for: you describe the person in plain English and get a ranked list.

What does Refolk's index show about Airtable talent?

In Refolk's index of professional profiles, 115 US profiles with software, infra or SRE titles mention Airtable in their headline, and 19 of the top 25 still list Airtable as their current employer after the cut. That lag is the opening for sourcers.

A few things worth noting:

• Location. Of the top 25 engineers, 9 are in the Bay Area, 6 in New York or Brooklyn, and 3 in Austin. A San Francisco-only search misses most of them, which is the same reason the WARN filing does.
• Ratio. There are roughly 6.4 engineers for every PM or designer in the index. Before the deal, Airtable had about 270 engineers against 83 in marketing and product combined. The PM and design pool is small. If you need one, move early.
• Noise. The 5,678 broad matches are mostly founders, CEOs and consultants who build on Airtable, not people who worked there. A plain "Airtable" keyword search sinks under them. Some headline matches are also near-misses like "Vitable" and "Actable," so read these counts as directional, not a census.

76%

This is why "open to work" filters are the wrong tool this month. Most leavers haven't flipped a badge or changed their headline. Filtering on "current employer = Airtable" catches leavers and stayers together, and that's fine. You find out which is which in the first reply. Competitors waiting for an "open to work" signal will miss most of them.

When can laid-off Airtable engineers actually start?

Probably not until mid-January. The WARN notice lists a last day of work of Jan 15, 2027, 92 days after the Oct 15 filing. "Out by the end of the week" most likely means out of the building and on paid notice, not off the payroll.

That changes how you pitch:

• Ask about start-date flexibility in the first call. Some leavers may want to start right away. Others may sit out the notice period to collect full pay.
• Ask how their separation package interacts with a new start date. Don't guess. If starting early costs a candidate part of their severance, an offer that looks great on paper can still lose.
• Plan offers for a January start. If your req has to be filled in November, these may not be your candidates.
• Skip the WARN dispute. The Strauss Borrelli investigation is theirs to handle. Mentioning it in outreach comes across as ambulance-chasing.

Timing is also where the competition gets real. Every infra-heavy company in San Francisco and New York saw the same headlines, and the strongest performance engineers will have several conversations going by Thanksgiving. If your team needs a senior infra hire and your sourcing pipeline already runs at six weeks per role, a three-month notice period plus a crowded market can push the hire into spring.

For the outreach itself, keep it short and specific. Mention the Performance and Infra work by name, since that's the context you're hiring for. Say you know the cut followed the org chart. Don't make it the headline. And name the January timeline yourself, so the candidate doesn't have to bring it up.

FAQ

How many people did Airtable lay off in October 2026?

Airtable hasn't said. The only public count is a California WARN notice dated Oct 15, 2026, covering 190 jobs in San Francisco County. That leaves out remote and non-SF staff. Based on Bending Spoons' usual cut of 75 to 85% at Komoot, WeTransfer and Brightcove, the total is plausibly 600 to 680 of the roughly 800 pre-acquisition employees.

Were Airtable's Hyperagent and DeepSky engineers laid off?

Not confirmed, and quite possibly not. Before signing, the Hyperagent business line was moved into a separate entity, so its engineers may never have been part of the company that ran the layoff. Ask candidates where they sit before assuming they were cut.

Is it worth trying to hire laid off Airtable engineers?

Yes. Bending Spoons said in writing that the cut wasn't about performance, and the line it drew separated pre-acquisition staff from its own incoming people. Many of these engineers also survived Airtable's 2022 and 2023 layoffs. Screen them as you would any strong alumni pool, starting with infra and performance engineers.

When will Airtable leavers be free to start a new job?

The WARN notice lists Jan 15, 2027 as the last day of work, so many leavers are likely on paid notice until then. Ask about start-date flexibility and how severance terms interact with an earlier start before you build an offer timeline.