Front's WARN Says 53. Paris Cuts Would Face a 3.5-Month PSE Clock

Front's California WARN filing gives recruiters one hard number: 53 San Francisco jobs, with Oct 27, 2026 as both the notice date and the last day of work. It says nothing about Paris, where Front built much of its engineering team and where French law would put any layoff on a clock that runs for months.

CEO Dan O'Connell's LinkedIn post on Oct 28 called it "an incredibly painful day at Front" and tied the cut to a push to "build a more sustainable business." He didn't say how many people were let go or when the cuts take effect. So if you recruit engineers, you're working with a floor in SF and an open question in France.

How big are the Front layoffs, really?

The only hard number is 53 San Francisco jobs in California's WARN file, and that's a floor, not a total. Depending on which headcount you believe, those 53 jobs are somewhere between 5% and 19% of the company.

A WARN notice is the advance warning US employers have to file before a mass layoff. California's version, Cal-WARN, requires 60 days' notice from employers with 75 or more employees. Front's notice and last day fall on the same date, so the gap is zero days. The usual way a company does that legally is by paying people in lieu of notice. That's an inference. The filing lists no severance terms, and Front hasn't confirmed anything.

53

The share is hard to pin down because nobody agrees on how many people work at Front:

The 280 comes from Front's own employer page, which also says Front has raised $204 million and has staff across the US and Europe. Companies update those pages when they feel like it, so the figure could be stale in either direction. LinkedIn's 500 to 1,000 counts everyone who lists Front as their current employer. That includes people who never updated their profile after leaving and, because "front" is an ordinary English word, some profiles that belong somewhere else entirely. I'd weight the 280 more heavily than the LinkedIn range, but nobody outside the company knows.

The filing also won't tell you which roles went. It predates California SB 951, which from January 1, 2027 requires WARN notices to disclose extra information when a layoff results wholly or substantially from technology automating the work, including which job functions are being automated. Front's notice carried no such obligation.

The SF market got three batches in one week

Front's 53 didn't arrive alone. Dropbox filed for 57 SF jobs on Oct 28, and Airtable has 190 workers in county filings. If you're sourcing in San Francisco this month, you're competing with every other recruiter who reads the same WARN feed.

Why the WARN filing says nothing about Paris

WARN covers California worksites only, so Front's Paris office, where much of its engineering was built, doesn't appear in any US filing. Whether Paris is cut at all is unknown, and the best public signal points toward "not cut."

Paris isn't a satellite office. Mathilde Collin, now Front's Executive Chair, met software engineer Laurent Perrin at the Paris startup studio eFounders in 2013, and they co-founded Front together. In 2018 Collin said Front opened in Paris because "we wanted to scale engineering," and that every function was there, including product and engineering. At that point roughly 20% of the team was in Paris and 80% in SF. That split is eight years old, so treat it as a sign of intent, not a current headcount.

O'Connell's post didn't say where the cuts fell. That leaves three scenarios for Paris:

• Untouched. The cut was SF-only.
• Small. Fewer than 10 redundancies, so no PSE (France's collective-redundancy plan) is required and the procedure is shorter. Your window closes faster.
• PSE. Ten or more, which starts the full process covered in the next section.

What's known and what isn't:

• The threshold. A PSE applies at 10 or more redundancies in a company with 50 or more employees. Front's French headcount isn't public, so you can't tell from outside which side of the line Paris is on.
• The anti-splitting rule. A company that dismisses more than 18 people in a calendar year without a PSE is forced to set one up. Front can't get around the process by cutting Paris in small batches.
• The counter-signal. Welcome to the Jungle showed a Front Software Engineering Intern role in Paris for Spring/Summer 2027, paying €2.5K a month. A company planning to gut its Paris engineering team doesn't usually post interns for next summer. The crawl date isn't clear, so check that the listing is still live before you read too much into it.

Any recruiter who tells you Front's Paris engineers are "on the market" is guessing. The honest position is "unknown." Plan for both cases.

How long does a French PSE take?

For fewer than 100 redundancies, the fastest legal PSE runs about 3.5 to 3.7 months from the first staff-council meeting to the first dismissal letters. In practice it often takes four to eight months end to end, counting redeployment measures.

A PSE (plan de sauvegarde de l'emploi) is the job-protection plan French law requires when a company with 50 or more employees makes 10 or more redundancies. The CSE (comité social et économique) is the elected staff council the company has to consult. DREETS is the regional labour administration that reviews the plan before anyone can be dismissed.

The minimum steps are fixed:

1. CSE consultation. Two months for 10 to 99 dismissals (two to four months for larger cuts). The CSE has to meet at least twice, at least 15 days apart.
2. DREETS review. 15 to 21 days.
3. Waiting period. At least 30 days before individual dismissal letters go out.

3.5 months

Here's what that means on a calendar if Front held its first CSE meeting in early November:

None of those steps can be squeezed. The 15-day gap between CSE meetings is a legal minimum, and so is the 30-day wait. So any affected Paris engineer would almost certainly still be employed and paid well into Q1 2027.

That works for recruiters in two ways. You have months to build a relationship before anyone is actually available. It also means this is the wrong time for an exploding offer. Asking someone to walk out of a legally scheduled exit early so you can hit a December start date is a pitch most engineers will turn down, and they'd be right to.

In San Francisco, Front's leavers were free on Oct 27. In Paris, even the fastest PSE starting in November puts the first letters in late February.

Why searching for "Front" engineers returns almost nothing

Front's name is an ordinary word, so headline keyword searches fail. In Refolk's index of professional profiles, searching for "Front" in headlines with engineering titles returned 1 profile in the US (a false positive at another company) and 0 in France.

The collision shows up right in Front's own job titles. "Front Software Engineering Intern" reads like a front-end role to any keyword engine. Every Boolean string that includes "Front" pulls in front-end developers and drops the people who actually work there. Stacking skill filters makes it worse: a France search in Refolk's index for engineers with TypeScript plus Node.js in the Computer Software industry also came back with 0. Rigid filters give you either noise or nothing.

To find Front people, search for the company as an entity:

• Company filters, not headline keywords. Match on the employer record, which tells Front apart from the word "front."
• The legal and domain names. "Frontapp" (the name on the WARN filing) and "front.com" show up in profiles, commit emails and conference bios where "Front" alone is useless.
• GitHub organization membership. Engineers who contribute under Front's org can be identified by the org, not by their bio.
• eFounders alumni. Front came out of that studio, and early Paris hires often overlap with its network.
• Paris plus US-overlap signals. Engineers who mention collaborating with SF are a narrow, telling subset.

Doing this by hand across LinkedIn, GitHub and the open web takes days of tab-switching, and it's exactly the gap Refolk closes. You describe the person in plain English, and the search resolves "Front the company" instead of "front the word."

Front's Paris engineers already work US hours

Front's culture book says the Paris team shifts its schedule so there are set hours each day for real-time collaboration across offices. These engineers are used to US-facing workdays, which makes them unusually good fits for US companies hiring remote engineers in Europe.

The usual failure with EU-remote hires isn't skill. It's the 5 p.m. Paris standup that slowly wears people down. Front's Paris engineers have built their routines around that overlap because it was how the company worked, not a favor to one manager. If you're a US startup with a distributed team, your pitch is "same overlap you already do, a scope you don't have today."

It's also why "hire laid off engineers Paris" is the wrong frame for some of these candidates. Many may not be laid off at all. What you're really offering is a better seat for someone whose employer just had a painful week.

A timeline playbook for recruiting Front engineers

Run SF and Paris as two separate campaigns. San Francisco leavers are on the market now. Paris engineers, if affected at all, won't be free before late February or March 2027.

1. This week, SF. The 53 people in the WARN file stopped working on Oct 27. Move fast, because Dropbox and Airtable leavers are hitting the same inboxes.
2. November, Paris mapping. Build the list without pitching an exit. Use the entity-based search above, note who sits on teams that work SF hours, and keep the outreach to a conversation.
3. Watch for real signals. Look for public mention of a CSE consultation, French press coverage, or engineers saying so themselves. Don't treat silence as confirmation either way.
4. December to February, relationships. Run interviews if candidates want them. Make offers with start dates that fall after their letters plus any notice, so nobody has to choose between your role and their package.
5. March 2027 onward, closing. If a PSE runs on the fastest legal path, this is when Paris candidates can actually sign and start.

The catch is that your req may not wait until March. A hiring manager who needs a TypeScript engineer with US overlap in Q1 can't sit through a French legal calendar, and the SF pool is being worked over by every agency with a WARN alert. That's when a months-long sourcing cycle turns into an expensive agency search.

FAQ

How many people did Front lay off in 2026?

Front hasn't given a global number. The only public figure is California's WARN filing, which lists 53 San Francisco jobs with a last day of Oct 27, 2026. That covers California only, so it's a floor. Against headcount estimates of 280 to 1,000, the SF cut alone is between 5.3% and 18.9% of the company.

Are Front's Paris engineers affected by the layoffs?

Nobody outside Front has said. O'Connell's post didn't mention locations, the WARN filing covers only San Francisco, and a Paris engineering intern listing for Spring/Summer 2027 suggests Front was still hiring there. Treat Paris as unknown and map the team without assuming anyone is leaving.

How long does a PSE plan de sauvegarde de l'emploi take?

For 10 to 99 redundancies, the legal minimum is two months of CSE consultation (with at least two meetings 15 days apart), then 15 to 21 days of DREETS review, then at least 30 days before dismissal letters. That's about 3.5 to 3.7 months at the fastest. In practice, four to eight months is common once redeployment measures are included.

Can I recruit engineers in France before a PSE ends?

Yes. You can talk to them, interview them and make offers, because they're still employed and paid while the process runs. Just don't push for a resignation or an early start date. Set start dates after their dismissal letter and any notice period, so they never have to pick between your offer and seeing the process through.