# Google's 2026 Buyout Leavers: Why Zurich First, and When to Reach Out

_Google's 2026 buyouts in five countries left no WARN list. How to find the August leavers in Zurich, Munich and beyond, and when their severance runs out._

- Canonical URL: https://www.refolk.ai/blog/google-voluntary-exit-zurich-munich-sourcing
- Published: 2026-11-07
- Reading time: 9 min
- Keywords: Google voluntary exit program 2026, Google buyout Switzerland Zurich, hire ex-Google engineers Europe, Google layoffs Canada 2026, former Google engineers Munich

Google's 2026 buyouts in Canada, France, Germany, Japan and Switzerland came with no WARN filing, no headcount and no list of who left. If you want the engineers who took the deal, you have to find them yourself, and in Refolk's index more than half of the Google-associated engineers in Switzerland still list Google as their current employer.

This is a cohort you find by working out its shape: when people left, which teams Google let go, and which offices they sat in. Most of the signal is in Zurich.

## What did Google offer in the 2026 voluntary exit program?

Google's voluntary exit program for 2026 offered packages to some employees in five countries starting in June. Employees applied, and Google decided who got one. Only the Swiss terms and timeline have been reported in any detail.

The coverage gets two things wrong, and both affect how you source:

- **It was an application, not a free choice.** Reuters says Google *notified applicants of its decisions* by mid-July. Google could say no, so the people who left are people Google was willing to lose.
- **"Departures began in August" is only confirmed for Switzerland.** Leaving dates for Canada, France, Germany and Japan haven't been reported.

What is confirmed:

- Offers began in June to some employees in Canada, France, Germany, Japan and Switzerland.
- In Switzerland, packages were announced in mid-June, decisions went out by mid-July, and departures started in August.
- Swiss terms were one month's pay per year of service, capped at 12 months. Terms for the other four countries weren't disclosed.
- Google Cloud and DeepMind were left out of past buyout rounds. The Swiss program covered several divisions but excluded DeepMind.
- Reuters couldn't find out how many people accepted. Google hasn't said.

A **voluntary exit package** (a buyout) is severance an employer offers to staff who choose to leave, as opposed to a layoff, where the employer decides who goes. In practice this one sat in between, because Google approved each application.

## Why is there no public list of who left?

Because these were approved voluntary exits outside the US, nothing required Google to file a WARN notice or publish a headcount. The filings recruiters normally rely on don't exist for this cohort.

A **WARN notice** is the advance filing US employers must make before mass layoffs. It usually gives a count, a site and a date. Recruiters lean on it because it hands them a ready-made list. This program produces none of that, and Google has confirmed the program to Reuters without giving a number.

The one figure on uptake comes from a single source: at least 4 people on one team of about 50 accepted, which is roughly 8%. Treat that as one data point. It tells you the program was real and that some teams lost people. It doesn't let you estimate a total.

Switzerland also has some history behind it. Google employs about 5,000 people there and laid off more than 200 in 2023, which led to protests and a walkout. A voluntary program at a site with that history draws far less attention than a layoff, which makes it easy for outsiders to miss.

## Why should you search Zurich before Munich?

Zurich comes first because the pool is bigger and the timeline is confirmed. In Refolk's index, Switzerland has 2.1 times as many Google-associated software engineers as Germany, and about 64% of the Swiss sample sits in the Zurich area.

The query covered Software Engineer, Senior Software Engineer and Staff Software Engineer titles with "ex-Google" in the headline. The match is loose, and many of these profiles still list Google as their current employer. Read it as the pool of Google-associated engineers in each market, not a confirmed list of leavers.

| Market | Total matches | Main metro share of sample | Google still listed as current (sample) |
|---|---|---|---|
| Switzerland | 49 | Zurich + Adliswil: 16/25 (64%) | 14/25 (56%) |
| Germany | 23 | Munich area: 14/23 (61%) | 8/23 (35%) |
| Canada + France + Japan | 67 | Toronto 6, Vancouver 4, Paris area 3, Waterloo 2; no Japanese region in the top 10 | 15/25 (60%) |

> **2.1x** Google-associated engineers in Switzerland vs Germany, Refolk's index
>
> Germany's overall engineering market is far larger, but Google's Zurich site outweighs Munich.

The reason is site size. Google Zurich has about 5,000 staff, it is Google's largest engineering site outside the US, and its teams work on Search, Maps, Calendar, YouTube and Gmail. Google Munich reported "more than 750 people" in 2019 and expected to pass 1,000 that year. That figure is old, so treat it as a minimum. Even so, the gap is large.

Munich is still worth a second pass. **Former Google engineers in Munich** cluster around privacy and security, Chrome and Google Account work, and the Google Safety Engineering Center at Erika-Mann-Straße 33. If you're hiring for security or browser work, Munich is the better search. For everything else, start with Zurich and Adliswil.

## What about Canada, France and Japan?

Canada and France show up in the data, but less of it. Japan barely appears in English-language searches, so don't promise Tokyo coverage the way you can promise Zurich.

If you searched "Google layoffs Canada 2026" and found nothing, that's expected. These weren't layoffs, and the Canadian matches in Refolk's index are spread thin: Toronto 6, Vancouver 4 and Waterloo 2 in the sample. Paris has 3. No Japanese region made the top 10 of the combined sample.

That gap tells you about the search method more than about Tokyo. Tokyo leavers need Japanese-language searches and different signals, which means a sourcer who reads them, not an English keyword with "Tokyo" added.

> **Engineering roles open in Toronto** - [see the open roles](https://www.refolk.ai/jobs/search?family=engineering&location=toronto)
>
> Live postings from Refolk's job board, for a sense of the Canadian market these engineers are re-entering.

## Why do most of the leavers still say "Google"?

Profiles update late for this cohort. 56% of the Swiss sample and 60% of the Canada, France and Japan sample still list Google as their current employer, even though Swiss departures started in August.

Two things drive the lag:

- **Severance takes away the urgency.** Someone with five months' pay in the bank has no reason to post "open to work" in week six.
- **Some leavers are taking a planned break.** People who applied for a buyout may have meant to take time off, and they won't touch their profiles until they're ready.

So searching "open to work" or "ex-Google" will miss much of the cohort. Search instead for Google roles that **ended between July and September 2026**, and treat profiles that still say "Google, present" as unconfirmed rather than ruled out. Germany's lower figure (35% still listing Google) may mean the German group updated sooner, or that more of that pool left in earlier years. The data can't tell you which.

This is where sourcing slows down. You end up opening every Zurich profile one by one, checking tenure dates, cross-referencing GitHub, and still not knowing whether "present" is accurate. The shortlist comes back thin and half-confirmed, and by then a hiring manager is asking why the role is still open.

## Which Google teams should you target?

Target Search, Ads, Android, Chrome, privacy and Maps engineers, not AI researchers. Google approved each exit, and it has been clear that AI and cloud are where it plans to keep hiring.

Alphabet CFO Anat Ashkenazi has said Google will keep adding staff in AI and cloud. Cloud and DeepMind were excluded from past rounds, and DeepMind was explicitly excluded in Switzerland. Earlier US buyout rounds covered the Android and Core engineering orgs, plus YouTube. Because Google could refuse any application, the approved group leans toward areas Google doesn't treat as top priority.

> Google chose who left. Source the teams it was willing to lose, not the ones it's still hiring for.

Here's how that maps to the offices:

1. **Zurich:** Search, Maps, Gmail, Calendar and YouTube engineers.
2. **Munich:** privacy, security, Chrome and Google Account engineers. Good for identity and browser roles.
3. **Canada and France:** smaller pools with mixed product areas. Read each profile for the team rather than assuming one.
4. **Anywhere:** deprioritise anyone whose recent work is Cloud or DeepMind. Those groups were kept out of past rounds, and DeepMind out of the Swiss one.

> **Example search:** "Software engineers in Zurich or Munich whose Google role on Search, Ads, Android, Chrome or Maps ended between July and September 2026." - [run it on Refolk](https://www.refolk.ai/start?q=Software%20engineers%20in%20Zurich%20or%20Munich%20whose%20Google%20role%20on%20Search%2C%20Ads%2C%20Android%2C%20Chrome%20or%20Maps%20ended%20between%20July%20and%20September%202026.)
>
> A ranked shortlist showing each person's Google team, tenure, end date and current location, with profiles that still say "Google, present" flagged for a check against recent public activity.

## When should you reach out?

Contact Swiss leavers before their severance runs out. At one month's pay per year of service, a five-year engineer who left in August is covered until about January 2027, so mid-tenure people are deciding what's next right now.

> **5 months** Severance runway for a Swiss Googler with five years of service
>
> One month per year, capped at 12; an August exit runs out around January 2027.

The Swiss formula gives you an outreach calendar. The dates below assume an August exit and the Swiss terms. Don't apply them to the other four countries, whose terms weren't disclosed.

| Years at Google | Severance (Swiss terms) | Runs out around |
|---|---|---|
| 3 | 3 months | November 2026 |
| 5 | 5 months | January 2027 |
| 8 | 8 months | April 2027 |
| 12 or more | 12 months (cap) | August 2027 |

Mid-tenure L4 and L5 engineers are the group to contact first. They're senior enough to be valuable, and their runway is short enough that a December conversation feels timely rather than pushy. Engineers with 12 years or more have no deadline yet, so they can pick and choose. Treat them as relationship-building for the spring.

## How do you hire ex-Google engineers in Europe without sounding like everyone else?

Mention the team they worked on, point to a real local alternative, and leave the buyout out of the opening message. They know why they left, and they don't need a stranger to tell them.

It helps to know where earlier Google leavers ended up. In Refolk's index samples, Google-associated engineers already work at:

- **Germany:** EngFlow, Delivery Hero, Trade Republic, Personio, Revolut, Nebius
- **Switzerland:** Meta, Datadog, Apple
- **Canada:** Instacart, MongoDB, AMD, Cresta

That list is your competition, and it's also your evidence. If you're pitching a Zurich Search engineer, say which Search-adjacent problem your team works on and whether the role is in Zurich.

There are two more signals worth tracking:

- **Blind (teamblind.com) threads** on Google's buyout, where engineers discussed whether to apply. They're anonymous, but they can hint at which orgs were weighing an exit.
- **Microsoft's parallel program.** Microsoft offered voluntary departure packages to about 60,000 employees the week before. If you're already sourcing that cohort, the outreach plan is the same: find people by end date, team and site.

## FAQ

### Did Google lay off engineers in Canada in 2026?

Not in the sense the search term suggests. Google offered voluntary exit packages in Canada, along with France, Germany, Japan and Switzerland, starting in June 2026. Employees applied and Google approved or refused each application. Leaving dates and terms for Canada haven't been reported. Note that in at least one earlier case, Google followed voluntary offers in a division with forced layoffs, so watch these offices closely.

### How much did Google's buyout pay in Switzerland and Zurich?

Swiss packages paid one month's salary per year of service, capped at 12 months. A five-year employee received about five months' pay, and only people with 12 or more years reached the cap. Google has about 5,000 staff in Switzerland, centred on Zurich, and departures there started in August 2026.

### Were Google Cloud and DeepMind engineers part of the program?

DeepMind was explicitly excluded in Switzerland, and both Cloud and DeepMind were excluded from past buyout rounds. Alphabet's CFO has said Google will keep hiring in AI and cloud. Concentrate on Search, Ads, Android, Chrome, privacy and Maps engineers.

### Why can't I find these engineers with an "open to work" search?

Many haven't updated their profiles. In Refolk's index, 56% of the Swiss sample and 60% of the Canada, France and Japan sample still list Google as their current employer. Severance takes away the urgency, so search for Google roles that ended between July and September 2026, and check recent public activity before you rule someone out.

---

_From the Refolk blog. More posts: https://www.refolk.ai/blog/index.md_