Automattic's Staggered Layoffs: Watch Gutenberg PRs, Not WARN Filings

On October 21, 2026, TechCrunch reported that Automattic had started layoffs in communications, social, WordPress.com and its VIP enterprise business, and a company spokesperson confirmed the cuts are being staggered on purpose. If you're waiting for a WARN notice, a headcount number, or a morning when LinkedIn fills up with "open to work" badges, you'll be waiting until mid-2027 and you'll miss most of the people. The better signals are already public: Gutenberg pull requests, Five for the Future rosters, and the VIP agency ecosystem.

Why won't Automattic's layoffs appear in WARN filings?

Automattic's cuts won't show up in WARN data because the company is fully remote, and remote staff have no clear "single site of employment," which is what triggers a WARN notice. Staggering the cuts doesn't create that gap. Being distributed does.

The WARN Act is the US federal law that requires advance notice before mass layoffs at a single site of employment. The statute never defines "single site of employment," and that is exactly where the dispute over remote workers lies. Without a clear site, no state filing gets triggered.

Many recruiters assume the staggering is the trick. It isn't. Courts can add separate rounds together: if an employer lays off 30 people on March 1 and 25 on April 10, those can be aggregated when they come from the same business decision. Spreading cuts over months doesn't get a company out of WARN. Having no office does.

Automattic's workforce is also spread across many countries. Earlier public profiles described 1,957 Automatticians in 95 countries speaking 121 languages. A US federal notice wouldn't cover anyone outside the US even in the best case.

The practical takeaway: stop using WARN trackers for distributed companies. For Automattic, WordPress.com and VIP, they will stay empty.

What has Automattic cut so far, and what comes next?

Confirmed cuts have reached communications, social, WordPress.com (including marketing and product staff in October) and the VIP enterprise business. No headcount figure has been published, and insiders expect more cuts over the coming months, ahead of debt renegotiations in June 2027.

Here's how this round differs from the last one:

Spokesperson Chenda Ngak's explanation: "We're staggering our organizational changes to be more generous with severance and allow more time with each Automattician." Matt Mullenweg said the terminations were "not above its normal numbers," and when asked about the growing total, said he was "mostly focused on PHP."

The leadership context explains why there's no clean number. A board move against Mullenweg collapsed within 33 hours, and the three directors behind it were gone: founding CEO Toni Schneider and board member Sue Decker resigned, and Gen. Ann Dunwoody was removed. CFO Mark Davies and chief legal officer Andy Missan were out in September, and interim CFO Jeremy Klaperman left after less than a month. With that much finance and legal turnover, I wouldn't expect anyone to publish a tidy layoff tally.

Sources say the cuts are spread out to improve fourth-quarter revenue figures before the June 2027 debt talks. The company hasn't confirmed that. If it's true, people will keep leaving for about eight months, with no single peak.

A staggered layoff has no peak. A sourcing plan built around one will miss most of the people.

How many WordPress VIP and Gutenberg people can you actually find?

In Refolk's index of professional profiles, 286 mention "WordPress VIP" in their headline and 267 pair the WordPress skill with "Gutenberg." Each pool is about a fifth the size of Automattic's listed headcount of 1,397.

The percentages come from the top-25 results, so read the region shares as lower bounds. The point holds anyway: the profiles you can see with a headline search are a small and skewed slice of the people being let go.

The company was also shrinking before this round started.

29%

Why does searching "Automattic" mostly return noise?

A keyword search for "Automattic" in Refolk's index matches 26,804 profiles, but only 24% of the top 25 (6 of 25) actually work there. The rest match "automatic," "Automatiq" and similar strings.

The name sits one letter away from a common English word, so keyword matching sweeps in everything that looks like it. Two more things make the parent-company search worse:

• Brand over parent. In the VIP headline set, WordPress VIP itself is the most common current employer. Staff who list a brand like WordPress.com or WordPress VIP instead of Automattic slip past a search on the parent name.
• Headline language. A workforce that speaks 121 languages doesn't write every headline in English.

This is the gap Refolk is built for. You describe the person ("Gutenberg block editor engineer, recently at WordPress.com, contributes to WordPress core") and get back a ranked shortlist matched on what they did, not a list of people whose headline happens to include a string that looks like "automatic."

Where do laid-off Automatticians leave a public trail?

Automatticians leave public trails in three places: the WordPress/gutenberg GitHub repo, the Five for the Future pledge pages, and WordPress.org contributor profiles. All three change whether or not the person ever updates a LinkedIn headline.

Five for the Future is WordPress.org's program in which companies pledge employee hours to the open-source project. Automattic's pledge has already swung hard once: in January 2025 it went from 3,539 hours per week on January 1 to just 45. After contributions resumed, its landing page listed 76 people contributing 500 hours per week across 16 Make WordPress teams. That's a public roster with names on it.

What to watch in each place:

1. WordPress/gutenberg on GitHub. Look for a regular committer whose merged PRs stop after a steady weekly pace, or whose GitHub bio drops an Automattic or WordPress.com reference.
2. Five for the Future pledge pages. Compare the named contributors on Automattic's page from month to month. A name that disappears from the corporate pledge and shows up as an individual pledge is a strong signal.
3. WordPress.org profiles. Track the profile names that match your Gutenberg and pledge-page lists, and note when a previously active contributor goes quiet.

None of these signals depend on the person posting about the layoff. That matters for a cut designed to be quiet. Megan Fox, Automattic's director of communications, said on LinkedIn that her role was "eliminated," but you can't count on engineers posting anything like that.

Why is an ex-Automattic Gutenberg engineer worth more than the visible pool suggests?

The Gutenberg pool you can see on LinkedIn is mostly freelancers: 52% of the top-25 regions are in Bangladesh, India or Pakistan, the top employers are Upwork (3), WordPress (2), Fiverr (2) and rtCamp (1), and none of the top results work at Automattic. A Gutenberg engineer leaving Automattic is a scarce senior profile, not a substitute for that pool.

The likely reason the two groups look so different: freelancers put "Gutenberg" in their headline because clients search for it, while Automatticians let their employer speak for them. So a headline search for Gutenberg surfaces people selling block development to clients, and the people who built the editor barely appear.

Pricing follows from that. If your benchmark for "WordPress developer" comes from freelance marketplaces, you will underbid for someone who has shipped core editor code to a platform at WordPress.com's scale. Benchmark against senior frontend and platform engineers instead.

The VIP pool looks different again. It's 32% South Asia and 20% US in the top 25, with US profiles clustered in places like Austin and Boston. Teams hiring WordPress VIP engineers are fishing in a smaller, more US-weighted pond than the Gutenberg numbers suggest.

Who else is recruiting Automattic's leavers?

Your main competitors are WordPress VIP partner agencies and WP Engine. In Refolk's index, the agency Multidots appears alongside WordPress VIP among the top employers of VIP-tagged profiles, and rtCamp appears in the Gutenberg set.

Agencies have a structural advantage: a VIP partner already works on the same platform and serves the same kind of enterprise clients, so hiring a former VIP engineer means very little ramp-up for them.

WP Engine is the other obvious destination. It was Automattic's opponent in the 2025 fight over contributions, and some leavers will see joining it as a statement. Others will avoid it for the same reason. Find out which applies before you pitch.

Teams outside the WordPress world can still win. Automatticians have worked fully remote, so a return-to-office role is unlikely to look like a step forward. A remote engineering offer from a non-WordPress company competes on scope, not on familiarity.

How do you recruit from a layoff spread over eight months?

To recruit from staggered layoffs, set up recurring searches now, check them every week through June 2027, and pitch individuals as they come free instead of running one campaign. Waves this small won't produce a burst of availability, so the advantage goes to whoever looks consistently.

A workable cadence:

1. Build the watchlist this week. Pull the named contributors from Automattic's Five for the Future page and the most active WordPress/gutenberg committers with Automattic affiliations.
2. Snapshot it. Record each person's current employer, last merged PR date and pledge status, so you have something to compare against.
3. Re-run weekly. Run the same saved search again and compare it against your snapshot to see who has changed employer or gone quiet.
4. Reach out when activity stops, not when they post. A gap in commits after a steady pace is your cue.
5. Pitch slower than you would after a mass layoff. The spokesperson framed the staggering as more generous severance. These people have time, so a rushed pitch reads as desperate.
6. Name their work. Mention the specific PR, component or Make team. Every other recruiter in their inbox will open with "saw the news about Automattic."

This is the core of staggered layoffs recruiting. The supply is real but spread thin, and the first recruiter to notice a person is usually the one who was already watching their commits.

FAQ

Will Automattic's layoffs show up in WARN notices?

Almost certainly not. WARN applies to mass layoffs at a single site of employment, and a fully remote company has no clear site for remote staff. Courts can combine staggered rounds when they come from the same business decision, so the staggering isn't the reason. The distributed workforce is, and it spans 95 countries that a US notice would never cover.

How many people has Automattic laid off in 2026?

No headcount figure has been reported. Automattic's About page lists 1,397 employees, and Mullenweg said the terminations were "not above its normal numbers." Confirmed cuts have hit communications, social, WordPress.com and VIP, and insiders expect more over the coming months.

When will the Automattic layoffs end?

Sources say the cuts are being spread out to improve fourth-quarter revenue figures before debt renegotiations in June 2027, though the company hasn't confirmed this. Plan for a steady trickle of departures through roughly mid-2027 rather than one final wave.

Where can I hire WordPress developers who worked on Gutenberg?

Start with the WordPress/gutenberg GitHub repo and Automattic's Five for the Future pledge page, not LinkedIn headlines. In Refolk's index, 267 profiles pair WordPress with Gutenberg in their headline, but the top results are mostly freelancers on Upwork and Fiverr, and none of them work at Automattic. The engineers who built the editor are easier to find by their commit history than by their job titles.