On Oct 12, 2026, five weeks after Bending Spoons closed its $1.285 billion Airtable deal, Airtable told a large portion of its roughly 800-person pre-acquisition team they would be gone by the end of the week. The stated reason wasn't performance or revenue. It was a belief that "small teams ship more and better." If you were on that team, or you work anywhere that just got bought, your resume is now read against that line, and most resumes leave out the one number it asks for.
What did Bending Spoons say, and why does it matter for your resume?
Bending Spoons explained the Airtable cuts in terms of output per person, not performance. That makes team size the hidden variable behind every bullet you write.
Here is what's on the record:
- The announcement. Alessandro Savarese, who now leads Airtable product development, wrote: "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." Airtable did not say how many jobs went.
- The philosophy. Federico Simionato, Bending Spoons' product leader, posted on X: "This is not a reflection of their work but a reflection of our deep belief that small teams ship more and better."
- The business. Airtable had roughly $480 million in annual recurring revenue, growing more than 20% year over year. These weren't cuts to save a struggling company.
- The replacements. Savarese said Bending Spoons brought in experienced engineers, product managers and designers from elsewhere in the company.
Why this matters past Airtable: when a high-profile layoff gets explained with a ratio, hiring managers start using that ratio themselves. A bullet that says "Led the v2 launch" and leaves out how many people built it makes the reader guess whether you drove the work or rode along. Under a small-teams lens, that guess goes against you.
How hard does Bending Spoons usually cut after an acquisition?
Its public record shows cuts that remove most of an acquired company's staff, often within months of closing. Airtable's number hasn't been disclosed, but the history tells recruiters how to read your exit.
| Company | Staff before | After the cuts | Detail |
|---|---|---|---|
| Evernote | 341 | ~20 | Down to ~60 first, then ~20, over 18 months (~94%) |
| AOL + Eventbrite + Vimeo | ~1,830 absorbed | "A few hundred" expected to remain | Per IPO filings |
| WeTransfer | 350 | ~260 cut | Planned ~75% reduction |
| Filmic | 22 | 0 of original team | Founder and CEO included |
| Airtable | ~800 | "A large portion" | Count not disclosed |
Don't put a number on the Airtable cut on your resume, in a cover letter, or in an interview. Nobody has published one, and a guess makes you look less credible. You don't need one anyway. The pattern is public, and that changes how your employer line reads.
Why is team size the most persuasive number on the page?
You can't compare output without knowing how many people produced it. "Shipped 12 features" means one thing from a 40-person org and something very different from three engineers, and a reader who has absorbed "small teams ship more" will discount the version that leaves out headcount.
A team-size denominator is the number of people who did the work, written into the bullet so the reader can work out output per person. "1 of 3 engineers" is a denominator. "Worked cross-functionally" is not.
The best template comes from the acquirer. Simionato's post promoted a "new Core team shipping your top requests monthly (already 30+ shipped in 3 weeks)." That one line has output (30+), a time window (3 weeks) and a named team. Bending Spoons writes its own wins in exactly the format it now judges other people by. Use the same format.
Bending Spoons wrote its own win as output, window and team. Write yours the same way.
The three-part bullet
Every bullet you want weighed under the small-teams lens needs three parts, plus a result when you have one:
- Output. What shipped, as a count or a named deliverable.
- Window. How long it took, in weeks or a quarter.
- Denominator. Your share of the team: "1 of 3 engineers," "sole designer," "2-person growth team."
- Result (optional). Adoption, revenue, tickets closed, latency cut.
The pattern: Shipped X in Y weeks as 1 of N [role], resulting in Z.
Small team impact resume examples
These are illustrative. Swap in your own numbers, and only ones you can defend in an interview.
| Role | Before | After |
|---|---|---|
| Engineer | Built new sync engine for enterprise customers | Rebuilt enterprise sync engine in 10 weeks as 1 of 3 engineers; cut sync errors by 40% |
| Product manager | Led roadmap for the workflow product | Shipped 14 workflow releases in 2 quarters as sole PM for a 6-person squad |
| Designer | Owned design for new launch surfaces | Designed 3 launch flows in 6 weeks as the only designer on a 5-person team |
| Operations | Improved sales ops processes | Rebuilt quote-to-cash in 8 weeks as 1 of 2 ops leads supporting 60 reps |
| Marketer | Drove lifecycle campaigns | Launched 22 lifecycle emails in a quarter as a 2-person team; lifted trial conversion 9% |
The "before" column describes a responsibility. The "after" column lets a hiring manager do the division in their head, and a small denominator next to a real output is the strongest signal a lean-team employer can get.
Where to find your real denominator
Most people don't remember their team size precisely, and rounding it up loses the whole point. Check these:
- Team pages and org charts in your internal wiki or HR system.
- Launch announcements in Slack or email, which usually name the contributors.
- Pull request reviewers and commit authors on the repo for a given feature.
- Sprint boards, filtered by assignee and quarter.
- Performance review self-assessments, which often already list scope.
How do you list an acquired company on your resume?
Lead with the brand people recognize, put the acquirer and year in a parenthetical, and keep your own employment dates on a separate line. For Airtable alumni, that means "Airtable (acquired by Bending Spoons, 2026)," not the other way around.
The reason is name recognition, and Refolk's index of professional profiles shows how lopsided it is. Worldwide, 687 professionals mention "Bending Spoons" in their headline. Only 33 of them are in the US. In a global sample of 25, twelve were in Milan.
Out of 687 worldwide in Refolk's index, so about 4.8% of the acquirer's footprint sits in the US.
Bending Spoons' own portfolio staff already do this. In sampled headlines from Refolk's index, they put the acquired brand into the job title: a sales operations lead who tags "Vimeo" after the title, a "Head of Technology, AOL." Brightcove, another Bending Spoons acquisition, shows up among the top US employers in that set. The people closest to the acquirer lead with the product brand because that's the name readers know.
For scale, Airtable's roughly 800 pre-deal staff outnumbered the US headlines mentioning Bending Spoons about 24 to 1. Meanwhile 5,678 US headlines match "Airtable," but that count is noisy: it pulls in Airtable consultants and similarly named startups (Vitable, Actable, Mintable), so it isn't a headcount. What it does show is that "Airtable" is everywhere as a skill keyword, which is one more reason your employer line has to show you built the product, not just used it.
Indeed suggests wording like "acquired by [new company] in [year]" next to the employer name. A clean version:
Airtable (acquired by Bending Spoons, 2026) Senior Software Engineer, Platform | Mar 2022 to Oct 2026
Should you leave the acquisition off entirely?
Some people say yes. One Glassdoor commenter put it plainly: "you don't need to have a mini M&A history in your resume." They also warned that an acquisition date can be mistaken for your own employment dates.
That's a real risk, and the fix is formatting, not leaving it out. Put the deal year only in the parenthetical beside the company name, and keep your month/year range on the title line. One parenthetical isn't an M&A history. It's four words that answer the question a recruiter would otherwise ask on the screening call.
Why the acquirer line helps you
The employer line already explains your exit, so spend your words on the denominator. "Not a reflection of their work" ran in nearly every write-up of the cuts, and Bending Spoons' habit of cutting between 60% and 94% of staff is public. A recruiter who reads "Airtable (acquired by Bending Spoons, 2026)" will assume a structural cut, not a performance one. Simionato even ended his post with "If you're hiring, these are excellent people and worth a call."
So don't add a "position eliminated" line or a summary paragraph defending your exit. That space belongs to the one thing the employer line can't show: your own output per person.
Why update your resume the day the deal closes?
Cuts at Bending Spoons companies have landed within weeks of closing, and the facts you need for your denominator disappear when your Slack login does. If you're at a company that just got acquired, the close date is the day to start your rewrite.
The deal completed Sept 4, 2026, and Savarese announced the cuts Oct 12.
Airtable isn't an outlier:
- WeTransfer planned to cut about 75% of staff within roughly two months of closing.
- Vimeo cut 10% before its deal closed, then made a second round in January 2026. Dave Brown, its former VP of Global Brand & Creative, posted publicly that he'd been laid off.
- Filmic lost all 22 members of its original team, founder included.
The bigger problem is evidence. Your denominator lives in tools you lose access to the day you're cut: the org chart, the launch thread, the PR history. Reconstructing "1 of 3 engineers" from memory three weeks later turns into "part of the platform team," and that's the vague bullet you were trying to replace.
Before your access goes, capture:
- Every launch you contributed to, with the date and who else was on it.
- Team size by quarter, since squads change shape.
- Metrics you're allowed to keep: adoption, latency, revenue, tickets, cycle time.
- Your title history, including any change after the acquisition.
- Names of two or three teammates willing to vouch for your share of the work.
That raw list is all Refolk needs. Paste in your history, unpolished and denominators included, and Refolk writes the resume from it, so you're editing a draft instead of facing a blank page while you also deal with severance paperwork.
FAQ
Should I write "laid off" anywhere on my resume?
No. "Airtable (acquired by Bending Spoons, 2026)" plus an October 2026 end date already tells the story, and the Bending Spoons pattern is public. If you want to address it directly, use one sentence in the cover letter or on the recruiter call, then move on to what you shipped and with how many people.
What if I don't know my exact team size?
Use the number you can verify and say what it counts. "1 of 4 engineers on the payments squad" is better than a bigger, fuzzier "15-person org." If the team changed shape mid-project, use the count during the window your bullet covers. Never round your denominator to make the team look smaller; a reference check or an interview question will expose it.
I stayed on after the acquisition. How do I list that?
Keep one employer heading, "Airtable (acquired by Bending Spoons, 2026)," and stack your titles under it with separate date ranges. If your team shrank after the deal, that's a strong denominator story: same or more output from fewer people is exactly the result Bending Spoons says it wants, and other employers will read it the same way.
Does this apply if my company wasn't bought by Bending Spoons?
Yes. Any acquisition or restructuring that gets explained in efficiency terms invites the same output-per-person reading. The format holds everywhere: brand first, acquirer and year in a parenthetical, your dates on their own line, and every bullet built from output, window and team size.