SUSE Cuts 190, Still Ships 363 Kernel Patches. Search git log First

If you want SUSE's kernel, openSUSE or Rancher engineers, a LinkedIn search will mostly hand you Fuse employees and German founders. SUSE told staff on Nov 2 that about 190 people, roughly 10% of a 1,900-person company, will lose their jobs, and it named "automation and AI" as the reason. The engineers worth hiring are already visible in git history, MAINTAINERS and build-service logs, and that public record maps who SUSE actually employs far better than any profile search.

What SUSE announced, and when it lands

SUSE is cutting about 190 jobs, around 10% of its workforce. Affected staff are told by Nov 4 and the FY27 strategy is presented on Nov 16. The memo from CEO Dirk-Peter van Leeuwen did not say which roles or countries are affected.

Here's the timeline as reported:

• September: voluntary separation offers go to long-serving staff, particularly people with more than ten years at the company. Apparently not enough of them accepted.
• Oct 27: SUSE announces new agentic AI capabilities for its Linux management tools.
• Nov 2: the all-staff memo goes out.
• Nov 4: affected employees are informed.
• Nov 5: employee representatives are nominated.
• The following week: one-to-one meetings begin.
• Nov 16: the FY27 strategy is presented.

Two other facts shape the picture. First, Prague employees formed the SUSE Workers Union earlier this year. It belongs to the Czech ICT Union, which also organizes Microsoft staff, so the Prague side of this process has organized employees at the table. Second, EQT has hired Arma Partners to sound out private equity buyers. SUSE brings in about $800 million in revenue and more than $250 million in EBITDA, and the reported price range is $4 billion to $6 billion. A company being prepared for sale has every reason to show buyers a leaner cost base, whatever the memo says about AI.

SUSE's kernel output didn't fall, only its share did

SUSE's contribution to the Linux kernel has held steady: 362 changesets in 7.0, 358 in 7.2 and 363 in 7.3. Its share dropped from 2.5% to 1.9% because the total pool grew, not because SUSE shipped less. A changeset is one merged patch credited to an author and, through LWN's tracking, to that author's employer.

Part of that growth is AI-assisted. In 7.2, 1,111 changes carried Assisted-by tags, up from 301 in 7.1. An Assisted-by tag is a commit trailer that discloses an AI tool helped write the patch. The same release had 2,652 developers, a big increase over the previous record. When the total swells like that, a steady contributor's percentage shrinks even if its engineers ship exactly as much as before.

358

For a recruiter, this matters because the people being cut weren't idle. SUSE was the top named employer in 7.2. If any of its kernel engineers are on the list, you're looking at people whose output was steady and visible right up to the memo.

Why a LinkedIn search for SUSE engineers fails

Profile search fails at both ends: the "SUSE" keyword drowns real employees in look-alike company names, and the "Linux Kernel" skill tag in Germany surfaces founders instead of kernel developers. A headline keyword search for "SUSE" returns 36,170 profiles in Refolk's index, about 19 times SUSE's real headcount, and only 1 profile in a 25-profile sample actually worked there. The top employers in the results are Fuse, Fuse Energy and Palo Alto Networks, a SASE vendor.

36,170

The likely culprit is loose matching: "Fuse" and "SASE" sit a letter or two away from "SUSE". The skill tag fails in a different way, and the gap between countries shows it:

Source: Refolk's index of professional profiles. The ratio rows are derived.

Germany: the tag finds founders, not kernel developers

In Refolk's index, Germany has 1,107 profiles with a "Linux Kernel" skill. The top titles are CTO and founder roles, SUSE doesn't appear among the top 10 employers, and Nuremberg isn't among the top regions. Skill tags are self-reported, so the people most eager to list a technology aren't necessarily the people maintaining it. A bigger pool here just means more of the wrong people.

Czechia: small, dense, and contested

Czechia goes the other way. It has 155 profiles, and SUSE, Red Hat and Siemens tie for top employer at 3 each in a 25-profile sample. That sample includes titles like "Senior Director, SUSE Labs" and "Principal Software Engineer - Linux networking." Prague and Brno lead the regions. The pool is small and accurate, which means everyone already knows about it.

Where SUSE engineers actually leave footprints

SUSE engineers are easiest to find where they ship code: kernel commits from @suse.de, @suse.cz and other @suse.* addresses, the MAINTAINERS file, the Open Build Service, and the Rancher GitHub org. Each source tells you something a profile can't, namely what the person built and whether they still build it.

Start with these sources:

1. Mainline kernel history. Author and Signed-off-by lines show the domain directly.
2. MAINTAINERS. This file in the kernel tree lists who is responsible for each subsystem, with email addresses. A SUSE address there marks someone who owns code, not just someone who contributes to it.
3. github.com/SUSE/kernel-source. It holds the sources, configuration files, package definitions and supporting scripts for the SUSE kernels. The people who maintain SUSE's own kernels show up here.
4. build.opensuse.org. The Open Build Service (OBS) is where openSUSE and SUSE packages are built. Package maintainer lists and commit logs name the people behind the distribution.
5. github.com/rancher. Rancher, RKE, K3s and Longhorn live here. If Rancher engineers are who you're hiring, check org membership and repo commit history, because GitHub often hides emails behind noreply addresses.

To find open source developers by commit email, a kernel clone and two commands go a long way:

# Who committed from SUSE domains since the September exit round
git log --since=2026-09-01 --format='%an <%ae>' \
  | grep -Ei '@suse\.[a-z]+' | sort | uniq -c | sort -rn

# MAINTAINERS changes touching SUSE addresses
git log --since=2026-09-01 -p -- MAINTAINERS | grep -Ei '@suse\.[a-z]+'

Senior people tend to show up across several of these sources. Thorsten Kukuk, who has introduced himself as a distinguished engineer at SUSE and leads its "Future Technology Team," is easy to place from public footprints alone. Before you name anyone in outreach, confirm their current MAINTAINERS entries, because subsystem ownership changes.

The slow part is everything after the grep. You have to match each address to one person, a city and a current public profile across four systems. That's the gap Refolk closes: you describe the engineer in plain English and get back a ranked shortlist that ties GitHub, LinkedIn and open-web footprints to the same person.

Watch for the email switch, but don't wait for it

A commit address changing from a SUSE domain to a personal one is the clearest public sign that someone has left, but under the German and Czech process it can trail the layoff by weeks. Representatives are nominated Nov 5 and one-to-ones start the week after, so affected engineers may keep committing from @suse.de or @suse.cz while their exit is being worked out. That's a mechanism, not a measured lag, but it means waiting for the switch leaves you behind every other recruiter.

These signals show up sooner, and all of them are searchable on lore.kernel.org:

• .mailmap updates. .mailmap is the file that maps a developer's old addresses to their current one. A new entry pointing a SUSE address at a personal one is close to an announcement.
• MAINTAINERS patches that change someone's address or mark an entry "Orphan," meaning nobody maintains it anymore.
• Signed-off-by lines from personal addresses. Signed-off-by is the trailer certifying who wrote or passed along a patch. Someone who signs off from Gmail while still listed with a SUSE address is in transition.

Look back to September as well. The voluntary round targeted staff with more than ten years at SUSE, and those are the most experienced people. Anyone who took the package has probably already changed address, so a search that starts on Nov 4 misses the most senior group completely.

Brno and Prague are a contested market

Hiring Linux kernel engineers in Czechia means competing with Red Hat and Siemens for the same small pool. Refolk's index shows 155 profiles with the skill, and all three companies tie for top employer. Expect any SUSE engineer who becomes available in Brno or Prague to hear from several recruiters at once.

That's where in-house sourcing hurts. You can spend days matching commit addresses to people, checking subsystem ownership and writing patch-specific openers, and still reach a maintainer the day after Red Hat's recruiter did. Hand it to an agency instead and the fee on a principal-level hire is real money, for a shortlist drawn from the same 155 people.

The union matters for timing too. Prague staff have the SUSE Workers Union behind them, so expect the Czech exits to involve formal representation rather than a quick handshake. Some engineers will start taking calls early, while others will wait until their terms are settled. Ask where they are in the process, and don't assume.

How to reach SUSE engineers without burning the pool

Contact SUSE engineers through the public setting where their work already lives, like mailing-list threads, conferences and GitHub, rather than bulk email to scraped commit addresses. Germany and Czechia are EU countries, and harvesting @suse.* addresses into a cold-outreach list likely runs into GDPR's notification duties under Article 14. Treat that as general guidance and run your process past counsel before you scale it.

Tone matters as much as channel. Christian Brauner, a former SUSE employee, wrote on Mastodon that it is sad "this pointless churn in the name of profit maximizing keeps happening to a great company." "A great company" is the part to take note of. A pitch that badmouths SUSE, or treats the layoff as an opening for a deal, will go badly.

Open with their patch, not their layoff. Kernel engineers answer people who have read their code.

A sequence that respects the process:

1. Find the person through their work, using commits, MAINTAINERS and OBS rather than headline keywords.
2. Name a specific patch or subsystem in the first line, and explain why your problem needs that exact expertise.
3. Time it around the process. Until Nov 16, people are in one-to-ones and waiting for the FY27 strategy. A short, low-pressure note now and a real conversation after that date works better than pushing for an interview this week.
4. Offer upstream continuity. If they maintain a subsystem, say plainly whether the role lets them keep doing it.

FAQ

Which SUSE teams are affected by the 2026 layoffs?

SUSE hasn't said. The Nov 2 memo announced about 190 cuts, roughly 10% of a 1,900-person workforce, but named no roles or countries. Affected employees are informed by Nov 4, and the FY27 strategy is presented on Nov 16. Until more is public, watch signals like MAINTAINERS changes and commit address switches rather than rumors.

How do I find open source developers by commit email?

Clone the project, then filter git log output by author or Signed-off-by domain. For SUSE that means @suse.de, @suse.cz and other @suse.* addresses. Cross-check against the MAINTAINERS file to see who owns subsystems, and search lore.kernel.org for .mailmap and MAINTAINERS patches that change an address. For Rancher, use org membership and commit history in the github.com/rancher repos, since GitHub often hides emails.

Is it legal to email engineers at the address in their commits?

Commit emails are public, but public doesn't mean free to use for marketing. In the EU, collecting those addresses into an outreach list likely triggers GDPR notification duties under Article 14. The safer route is contact through public, work-related channels (mailing-list context, conferences, GitHub), with a legal check on any bulk process.