Bending Spoons Just Bought Eventbrite. Brightcove Lost 85% in Two Months.
Bending Spoons' $500M Eventbrite deal triggers the same playbook that gutted Vimeo and Brightcove. How to pre-source the bench before WARN.
Bending Spoons signed a definitive agreement to take Eventbrite private at $500 million in December 2025. Stockholders sued in Delaware in January to block it. None of that matters for how you should be sourcing right now. If the deal closes, the cuts have a release date, and the release date is roughly eight weeks after close.
Recruiters who wait for the WARN filing will be six months late. The leading indicator is the press release you already read.
The pattern is not a pattern. It is a schedule.
Bending Spoons buys aging consumer-software brands, runs them as permanent holds, and finances the model by cutting headcount and raising prices. The cadence is now consistent enough to plan against.
- Filmic (2023): all 22 employees fired shortly after close, including the founder/CEO.
- WeTransfer (July 2024): 75% of staff let go within two months of acquisition.
- Brightcove ($233M, November 2024): 85% staff reduction in 2025.
- Vimeo ($1.38B, 2025): layoffs began two months after close. By month four, over 1,000 employees globally were cut, the largest in company history. Ex-employees described "almost everyone" gone, including the entire video engineering team.
- AOL: acquisition pending, closing in parallel with Eventbrite.
- Eventbrite ($500M, December 2025): closing pending, lawsuit in progress.
Vimeo's CEO Philip Moyer also laid off 10% of staff one week before the Bending Spoons deal was announced. That is the cleanest pre-close signal there is. Watch Julia Hartz's communications and any unannounced Eventbrite trims between now and close. If it happens, the clock is shorter than you think.
What gets cut, specifically
The Vimeo and Brightcove cuts were not even. The deepest reductions hit the core domain engineers, the people who actually understood the platform. At Vimeo that meant the entire video engineering team. At Brightcove, the same.
For Eventbrite, the analog is ticketing infrastructure, payments, and fraud engineers. These are the people who built the queue, the seat map, the dispute pipeline, the Stripe and Adyen integrations, and the bot mitigation that lets a Beyoncé presale not collapse. They are also the people Ticketmaster, SeatGeek, DICE, Posh, Luma, Partiful, and Fever will pay a premium for. The Eventbrite bench skews heavily senior. Senior Software Engineer is by far the dominant title across the public index, with the largest concentrations in Bengaluru, Madrid, and Vancouver.
If you run sourcing at any ticketing platform and you do not have a working shortlist of Eventbrite payments and fraud engineers by Friday, you are letting your competitors hire them in March.
The non-obvious geography
Most recruiters will focus on Eventbrite's San Francisco HQ. That is the wrong map. Eventbrite's deliberate engineering hubs are in Madrid, Alicante (from the Ticketea acquisition), Cork, Dublin, Berlin, and Mendoza, Argentina. The Madrid engineering center opened in May 2019 at 24,000 square feet, with staff between Madrid and Alicante exceeding 80 and a stated plan to triple the team in engineering and product.
Bending Spoons consistently moves operations from expensive Silicon Valley locations to cheaper European bases. That paradoxically means the European and LATAM offices may survive longer than HQ, which gives you two different sourcing windows: a fast one for US engineers (March through May) and a slower one for Madrid, Cork, and Mendoza (likely summer through fall). Plan two campaigns, not one.
Why Boolean search will lose this race
Sourcing engineers from acquisitions used to mean a LinkedIn filter for "Company: Eventbrite" plus a Boolean stack of skills. That worked when titles were clean and people updated their profiles within a week of being cut.
It does not work now. The Eventbrite engineering org has years of accumulated title drift. "Senior Software Engineer" covers payments, fraud, search, ML ranking, mobile, and platform reliability. The people you want for a fraud role at SeatGeek are not findable by title. They are findable by the shape of their work: commit history on rules engines, conference talks on adversarial ML, prior time at Stripe Radar or Sift.
This is the gap Refolk was built to close. You describe the person you want in plain English ("senior backend engineer at Eventbrite who has worked on payments fraud or chargeback systems, ideally Madrid or remote EU") and get a ranked shortlist pulled across GitHub, LinkedIn, and the open web. No Boolean. No 47-field filter stack. The point is to compress the work between "the deal closed" and "we have a 40-person bench" from two weeks to one afternoon.
The communities that go live the day of the cut
The minute the layoffs start, three things happen in this order, and none of them surface on LinkedIn for at least a week.
- A private Slack or Signal group spins up for the affected cohort. The Vimeo equivalent appeared in late January 2026. Eventbrite will get one within 24 hours of the first cut email.
- A handful of public LinkedIn posts go up from named voices. At Vimeo it was Dave Brown (former VP, Global Brand & Creative) and Steve Dixon (a software engineer who posted publicly about being laid off). These posts are sourcing gold because they pull commenters out of the woodwork and let you see the whole affected team in one thread.
- A founder voice goes critical of Bending Spoons. WeTransfer cofounder Nalden did this publicly in December 2025 and announced he was building another file transfer service. Expect the Eventbrite equivalent. That founder is going to hire 30 of their old colleagues. Be the recruiter who already knows who they are.
The WARN filing is where bad recruiters start. Good recruiters started in December. </pull> ### The communities to actually monitor - The #brite-alumni LinkedIn cluster (exists already, will activate). - r/Eventbrite and the Eventbrite organizer forums, which catch internal sentiment before staff do. - The Madrid Python and Django meetup ecosystem. Eventbrite's stack has historically been Python-heavy and the Madrid hub is deep in that community. - Argentine engineering communities around Mendoza. Mercado Libre is the obvious landing spot for that office. - Ex-Vimeo Slack groups. Some of those engineers worked at Eventbrite earlier in their careers and know who to call. ## AOL is the parallel deal nobody is staffing for The Eventbrite story is loud because it is consumer, public-market, and contested in Delaware. The AOL deal is closing in parallel and will follow the same arc. AOL still employs a non-trivial advertising, mail infrastructure, and identity engineering team, the kind of bench that Yahoo Mail competitors, ad-tech firms, and identity providers (Okta, Auth0 alumni networks, Clerk) would absorb in a heartbeat. Recruiters who only react to the Eventbrite news will miss a second, larger talent dump within the same six-month window. If you run an ad-tech or consumer-email engineering org, AOL is your trade, not Eventbrite. The same pre-sourcing logic applies. The same Refolk query, with different inputs, gets you the bench.
stat number: $1.38B label: Vimeo acquisition price, before the company lost over 1,000 employees in four months note: Eventbrite is a $500M deal. The proportional cut math is not encouraging for the people there now.
## Why this bench does not come back
Traditional private equity holds for four to seven years, then exits. That exit forces a rebuild: revenue has to grow, headcount comes back, the company hires aggressively in years three through five to prepare for sale. Recruiters can play both sides.
Bending Spoons does not do this. The company's stated model is to hold forever and extract value through cost cuts and price increases. There is no exit. There is no rehiring cycle. The roles that get cut at Eventbrite in 2026 are not paused, they are gone permanently.
That changes the calculus for the engineers, and it should change the calculus for you. These are not people waiting six months for their old company to call them back. They are people who need a landing spot now and who will say yes to a serious conversation in the first two weeks. Speed matters more than polish. A 40-person shortlist on the day of the cut beats a 400-person shortlist three weeks later.
## A concrete pre-source checklist for the next 30 days
If you run sourcing at a ticketing platform, an events startup, a payments fraud team, or an ad-tech firm with a possible AOL angle, this is the week to do the work.
1. **Build the named-target list now.** Eventbrite engineering, by function (payments, fraud, search, ML, mobile, infra) and by office (SF, Nashville, Madrid, Alicante, Cork, Dublin, Berlin, Mendoza, Vancouver, Bengaluru). Refolk handles this in a single prompt; if you are doing it in LinkedIn Recruiter, budget a full week.
2. **Tag the senior cluster separately.** The bench is heavy on Senior Software Engineer. Split it by years of tenure: 5+ years at Eventbrite are the institutional knowledge holders and the most valuable hires.
3. **Pre-write the outreach.** Generic "saw the news" notes will lose. The winning first message names the specific system the engineer worked on and the specific reason your company needs that system understood.
4. **Identify the founder-voice candidates.** Who at Eventbrite has a public following, has posted critically about acquirers before, or has founder pattern in their history? Those people will start companies. They will hire their colleagues. Get to them in week one.
5. **Stand up the AOL parallel list.** Same exercise, different keywords, same urgency.
The teams who win this hire cycle will be the ones who treat the December 2025 announcement as the start of the sourcing sprint, not the news. The Brightcove and Vimeo benches are already gone. The Eventbrite bench is still at their desks. That window does not stay open.
## FAQ
### When will the Eventbrite layoffs actually happen?
If the deal closes on its current track and the stockholder lawsuit does not derail it, expect the first wave within eight weeks of close, based on the Vimeo and WeTransfer precedents. Vimeo's cuts began two months after the $1.38B close and reached over 1,000 globally by month four. WeTransfer hit 75% within two months. Eventbrite was on track to be taken private by March 10, 2026, so plan for cuts beginning April through May, with a deeper second wave by summer.
### Which Eventbrite engineers are most likely to be cut first?
The Brightcove and Vimeo pattern points to deep cuts in core domain engineering. For Eventbrite that means ticketing infrastructure, payments, fraud, and the consumer mobile and web teams. Sales, marketing, and US-based G&A also typically go early in the Bending Spoons playbook. European and LATAM engineering hubs (Madrid, Cork, Mendoza) tend to survive longer because they are already on the cost basis Bending Spoons is moving toward.
### How is this different from sourcing a normal layoff?
Two things. First, the timing is predictable, so you can pre-build the bench before the cut rather than racing other recruiters after. Second, because Bending Spoons holds permanently and does not rehire, the displaced engineers are looking for permanent landings, not waiting out a downturn. They will respond faster and decide faster than engineers from a typical tech layoff who think their old employer might call them back in six months.
### Can I use Refolk for the AOL deal too?
Yes, and you should. The AOL acquisition is closing in parallel and will follow the same arc. The same plain-English query pattern works: describe the function (ad-tech backend, mail infrastructure, identity, anti-abuse), the seniority, and the geography you can hire into, and Refolk returns a ranked shortlist across GitHub, LinkedIn, and the open web. Most recruiters will be staffing only the Eventbrite story. The AOL bench will be less contested for at least the first month.