SUSE Cut 190. Zero Czech Profiles Say 'SUSE Linux.' Read Commits Instead

On November 2, 2026, SUSE CEO Dirk-Peter van Leeuwen told staff the company would cut about 10% of its roughly 1,900 employees, around 190 jobs, and said the reason was "automation and AI." The memo, reported by The Register, named no roles and no countries. That would normally leave recruiters guessing, but SUSE does a lot of its engineering in public: kernel commits, Open Build Service packages, and the Rancher, K3s and Longhorn repos on GitHub. Those records tell you more than any profile search will.

What did SUSE announce, and when does it play out?

SUSE is cutting about 190 of its roughly 1,900 staff. Affected employees were told by November 4, and everyone who stays sees the FY2027 strategy on November 16. The company hasn't said which teams or countries are affected.

Here's the sequence so far:

• September 2026: a voluntary separation offer went to employees with more than ten years of service. It came from Lisa Sherwell, People, Strategy and Transformation Executive. Too few people took it.
• October 27: SUSE announced new agentic AI capabilities for its Linux management tools.
• November 2: the layoff memo went out.
• November 3: openSUSE Leap 16.1 shipped.
• By November 4: affected staff were informed, and employee representatives were nominated the next day.
• The following week: one-to-ones began.
• November 16: the FY2027 strategy goes to remaining staff.

Prague staff have also formed the SUSE Workers Union, which is part of the Czech ICT Union. That union also organizes a group of Microsoft staff in the country.

The ownership history is relevant context. EQT bought SUSE for $2.5 billion in 2018, listed it in 2021, took it private in 2023, and has reportedly explored a sale at up to $6 billion. Van Leeuwen, who came from Red Hat, wrote that "AI capabilities are advancing exponentially, forcing us to radically reimagine our work." The memo doesn't put a number on any productivity gain. Economists and Gartner have also warned that many cuts made in AI's name end up being rehired at higher cost. If that pattern holds here, the cheapest time to hire these engineers is now, not after SUSE or a competitor comes back for them.

Why does profile search miss SUSE's engineers?

Most of them don't put "SUSE Linux" in their headline. In Refolk's index of professional profiles, 49 people in Germany have "SUSE Linux" in their headline. The same query for the Czech Republic returns zero.

The German result does tell you something. In a sample of 25 of those 49 profiles:

• 21 list a SUSE entity as their current employer (84%)
• 17 are based in the Nuremberg/Erlangen area (68%)
• The most common titles are Senior Software Engineer and Linux Kernel Developer

Still, 49 people is about 2.6% of SUSE's global headcount. Searching "SUSE" on its own is worse. Across six countries it returned 14,601 hits, and most of them were false matches on words like "Fuse" and "Muse." Neither number gives you a usable list.

0

Prague staff probably describe themselves by product name or not at all. If you want to source open source contributors from a company like this, start from what they've built, because a headline search will only ever find the small group that writes "SUSE Linux" in theirs.

Did AI cause the cut? SUSE's kernel output fell first

The public evidence doesn't show it. SUSE's contributions to the mainline kernel fell 41% between Linux 6.17 and 7.0, from 612 changesets to 362, before the memo, and the memo quantifies no productivity gain. A changeset is a single accepted patch in the kernel's history, so the count is a rough proxy for how much work a company does upstream.

Source: LWN development statistics. These figures count commits, not people.

41%

A drop like this points to a shift in priorities, not to AI making people faster. If AI tools had made SUSE's kernel engineers more productive, you'd expect output to hold steady or rise. Instead it fell for two releases in a row. LWN does see an AI effect elsewhere: it says growth in first-time kernel contributors "is almost certainly driven by the increasing availability of LLM-based development tools." That's a more accurate picture of what AI is doing to kernel work than the memo gives.

For recruiters, this means some SUSE kernel engineers had less upstream work well before November. That makes them worth contacting whether or not their name is on the list.

Where do SUSE engineers leave a public trail?

Look in three places: kernel sign-offs from suse.com and suse.de addresses, maintainer and package history on the Open Build Service, and membership in the rancher, k3s-io and longhorn GitHub orgs. Each one finds people that profile keywords miss.

1. Mainline kernel commits. Look for Signed-off-by lines with SUSE email domains. Takashi Iwai, SUSE's ALSA sound maintainer, was one of the top individual contributors by changesets in 6.17. He's an example of how visible these engineers are, not a suggestion that he was affected.
2. Open Build Service (build.opensuse.org). Package pages show maintainers, and the package history shows who actually did the work. This is the most direct way to find openSUSE maintainers, including the ones who keep their profiles empty. Leap 16.1 shipped on November 3, the day after the memo, so its recent package history is a current snapshot of who was still doing the work.
3. GitHub orgs: rancher, k3s-io, longhorn. Public org membership and the people who open and review pull requests show who works on Rancher, K3s and Longhorn. If you're hiring Rancher Kubernetes engineers, this is your source list.

Doing all of this by hand is the slow part. You collect commit authors, match email domains to real people, check whether they've already left, and then find a way to reach them. Refolk is built for that step. You describe the person in plain English, and it returns a ranked shortlist drawn from GitHub, professional profiles and the open web, including people whose headline never mentions SUSE.

Who is most likely among the 190?

Long-tenured staff working on classic SLES tooling are probably more exposed than Rancher engineers. That's an inference from public signals, not something SUSE has confirmed.

Here's what points that way:

• The September offer targeted 10+ years of service. It was aimed at the longest-serving staff, and too few accepted. Forced cuts followed, so the voluntary offer shows roughly where the company wanted to reduce.
• YaST was deprecated on openSUSE Leap 16 and SLES 16. The engineers who maintained it have lost a flagship project.
• Kernel share dropped from 4.7% to 2.5%. Upstream kernel work was already shrinking.

Be careful with this inference. A ten-year SUSE veteran who maintains a core kernel subsystem may be just as safe as a recent Rancher hire. Use the signals to decide who to contact first, and never assume someone was laid off.

If you hire Linux kernel engineers, this is a good group to approach. A decade on enterprise Linux means packaging, backporting and long-term support experience you can't train into a new hire quickly. Live demand for that work, from other employers, appears below.

When should you reach out? Germany and the Czech Republic run on different clocks

Start conversations now. For German candidates, make a concrete offer just after November 16. For Czech candidates, plan start dates for Q1 2027, with February as a realistic earliest exit. Employment law in each country sets a different timeline.

Germany: be early with a concrete offer

German law gives the works council at least two weeks to respond. If consultation isn't done properly, every dismissal in the wave is void, not just one. That's a big risk for SUSE, so the company has every reason to push severance agreements, where an employee signs to leave in exchange for a package. Expect affected staff to be weighing those packages in late November, right after the strategy meeting. A written offer in hand when someone is deciding whether to sign carries far more weight than a vague "let's talk" sent in January.

Czech Republic: start now, but plan for February

In Prague, SUSE has to inform the union at least 30 days before issuing notices. Add the labour office waiting period and a two-month notice period, and the whole process takes about 3.5 to 4 months. So a Czech engineer you contact this week probably can't start until around February 2027. Start the conversation now, but don't build your plan around a December start date.

That timing is a real problem if you've had a kernel or Kubernetes role open since summer. Waiting three months for a Prague engineer means another quarter with the seat empty. Contacting a long list of commit authors who may or may not be leaving also eats sourcing hours without guaranteeing anyone, and paying an agency to wait for the same people doesn't make the quarter any shorter.

What should the first message say?

Open with their public work and a concrete timeline. Don't mention the layoff. Nobody needs to admit they were cut in order to reply to you, and many of the people you contact won't have been.

A message that works usually does these things:

• Cite a specific commit, package, or pull request. "Your backport work on the SLES 16 kernel" shows you did the research. "I saw SUSE is cutting staff" shows you read The Register.
• Don't assume they're affected. The memo named no one, and people who stay hear from recruiters too.
• Match the timing to the country. For German contacts, offer a timeline that lets them decide before a severance deadline. For Prague contacts, say plainly that a Q1 start is fine.
• Say how much upstream time they'd keep. For maintainers, that can matter as much as salary.
• Skip the AI framing. Implying that someone was "replaced by AI" is inaccurate, given that SUSE's kernel output was already falling, and it's insulting.

Cite the patch, not the layoff. Nobody at SUSE has to admit they were cut to answer you.

If your list started from a headline search, you'll be writing to the same 49 people everyone else is writing to. Start from the commits instead, so your first message goes to someone whose work you've actually read.

FAQ

How many people did SUSE lay off in 2026?

About 190 people, roughly 10% of SUSE's approximately 1,900 employees. CEO Dirk-Peter van Leeuwen announced the cut in a memo on November 2, 2026. It followed a September voluntary separation offer to staff with more than ten years of service, and too few people accepted it.

Which SUSE teams and countries were affected by the layoffs?

SUSE hasn't said. The memo named no roles or countries. Public signals, including the voluntary offer's 10+ year tenure target and the deprecation of YaST in SLES 16, suggest long-tenured staff on classic Linux tooling are more exposed than Rancher engineers, but that's an inference. Most German "SUSE Linux" headline matches in Refolk's index sit in the Nuremberg/Erlangen area, and Prague is a known SUSE site with its own union.

How do I find openSUSE maintainers and SUSE kernel engineers?

Search public work, not profile headlines. In Refolk's index, only 49 people in Germany and none in the Czech Republic have "SUSE Linux" in their headline. Use kernel Signed-off-by lines from suse.com and suse.de addresses, maintainer roles and package history on build.opensuse.org, and membership in the rancher, k3s-io and longhorn GitHub orgs.

When can laid-off SUSE engineers in Prague start a new job?

Probably not before around February 2027. Czech law requires SUSE to inform the union at least 30 days before issuing notices, and the full process, including a two-month notice period, typically takes 3.5 to 4 months. Start talking now and plan start dates for Q1.