Refolk
September 25, 2026·9 min read

Klarna's 1,000-Person Silent Shrink: 12 Leavers a Week, No WARN

Klarna is shedding ~630 people a year through attrition with no WARN filing. Here is how to source the silent shrink on LinkedIn, GitHub, and the open web.

sourcing from shrinking companiesKlarna attrition sourcingrecruiting without WARN noticeshiring freeze sourcingAI headcount attrition
Klarna's 1,000-Person Silent Shrink: 12 Leavers a Week, No WARN

Sebastian Siemiatkowski keeps saying the quiet part on podcasts: Klarna will fall from roughly 3,000 employees to under 2,000 by 2030, and it will do it with zero layoffs, zero WARN filings, and zero severance lists. On the 20VC podcast he told outsiders to "go to LinkedIn and look at the insights, you're going to see how the company is shrinking." If you source for a competing fintech, that sentence is a starting gun. There will be no headline, no leak, no OWBPA list. Just twelve people a week walking out the door for the next five years.

Why Klarna is the template, not the exception

Klarna is the cleanest public case of AI-era silent attrition: a stated headcount target, a stated mechanism (natural attrition plus a hiring freeze), and a CEO on record telling recruiters where to watch. About 40% of employers now say they expect to cut workforces in response to AI automation. Most of them will pick Klarna's path over a WARN filing, because attrition costs nothing, generates no press cycle, and lets the CEO claim a humane transition.

The mechanism matters. A WARN notice is a single document listing 500 names on one day. Attrition is a five-year drip that never trips an aggregator, never shows up on Layoffs.fyi, and never lands in a Slack channel called #layoff-watch. It is louder than a layoff on LinkedIn if you know what you are looking at, and silent everywhere else.

Here is the shape of it, straight from Klarna's IPO prospectus:

MetricValueSource
Klarna FTE, Dec 20225,527IPO prospectus
Klarna FTE, Dec 20234,352IPO prospectus
Klarna FTE, Dec 20243,422IPO prospectus
Implied YoY attrition~21%Derived
Stated 2030 target<2,00020VC podcast
Implied leavers, 2025 to 20301,400+Derived, assumes no rehires

Klarna has already shrunk 21% in each of the last two years. At the same 21% rate on today's 3,000 base, that is roughly 630 people entering the open market every year, or about 12 a week.

630
Klarna leavers hitting the open market per year
Derived from Klarna's stated 21% annual attrition on a 3,000-person base.

What "no WARN to read" actually costs you

It costs you the aggregator. Every sourcing workflow built in the last five years assumes somebody else does the trigger detection: a WARN scraper, a TechCrunch alert, a layoffs.fyi row, a subreddit thread with a leaked all-hands. None of those fire on Klarna. The Bloomberg piece about the AI walkback, where Klarna said it would reintroduce human support in a gig model after admitting AI-only service degraded quality, is the closest thing to a public trigger, and it is not a list of names.

Sourcing from shrinking companies without a WARN notice means owning the detection layer yourself. That is three concrete shifts:

  1. Signal moves from event to stream. You are no longer reacting to a Tuesday announcement. You are running a standing query that surfaces "started a new position, previously at Klarna" every week for five years.
  2. Volume moves from spike to drip. Twelve names a week, not 500 in a day. That is better, not worse: you can actually run a proper outbound sequence on 12 people. You cannot on 500.
  3. Competition drops to near zero. Every other recruiter in Stockholm is waiting for a Klarna headline that will never come. You are the only inbox those 12 people see this week.

This is the exact gap Refolk closes for silent shrinks: describe the person in plain English ("engineers who left Klarna in the last 90 days, based in Stockholm or Berlin, backend or platform") and get a ranked shortlist back, refreshed as new leavers show up. No WARN needed, because the signal was never in a WARN in the first place.

The Klarna pool, sized

In Refolk's index of professional profiles, there are 268 current Klarna-linked engineering, PM, DS, and ML professionals reachable right now, with Stockholm and Berlin tied at the top for location and long tails in Málaga, Milan, and the Netherlands. Top titles: Software Engineer (8 exact matches), Product Manager (5), Engineering Manager (4). That 268 is your standing pool. The 12-a-week drip is the flow on top of it.

268
Sourceable Klarna eng, PM, DS, and ML profiles
In Refolk's index, concentrated in Stockholm and Berlin with tails in Málaga, Milan, and the Netherlands.

Two things about that pool are worth internalizing before you write a single outbound message.

First, the five-year average tenure means the people leaving now were hired in 2020 and 2021, at Klarna's ZIRP-era peak. That is a specific persona: senior ICs and engineering managers with pandemic-era comp expectations and real fintech scaling experience. Klarna went from 5,527 to 3,422 FTE while shipping an OpenAI-powered chatbot the company claimed did the work of 800 full-time agents. They have seen the whole arc.

Second, the IPO broke their handcuffs. Klarna listed on the NYSE last September at a $15B valuation in a $1.37B IPO, and the stock is down about 59% since. Four-year grants sized at IPO are underwater. Retention economics have inverted, which is why the drip exists in the first place.

A frozen company that still posts is telling you exactly which functions it considers untouchable, and by inversion which ones it is allowing to bleed out.

Read the porous freeze

Klarna's hiring freeze is porous, and the porousness is the signal. TechCrunch reported that Klarna kept advertising roles after announcing the freeze; it is currently hiring for roughly 10 roles, mostly in Europe. Any freeze that still posts is telling you two things at once:

  • What is being protected. The functions that keep posting are the ones leadership will not let attrition touch. At Klarna, per Siemiatkowski, that is roles built on "human connection," meaning retailer and partner relationships.
  • What is being drained. By inversion, every function that is not in the ten open reqs is being allowed to shrink. That is your target list. Recruiting from hiring freezes is really recruiting from the unposted functions.

For Klarna specifically, engineering, ops, data, and back-office are the poachable pool. Product and partnerships are the protected pool. Do not waste an outbound sequence trying to move a partner manager Klarna is actively defending.

Where Klarna alumni actually land

They land at the obvious European fintech neighbors first, then at US payments companies with European engineering hubs. Based on the geographic concentration in Stockholm and Berlin, the natural destinations for a Klarna backend or platform engineer are:

  • Adyen (Amsterdam, strong Berlin presence): closest technical analog, same merchant-side payments world.
  • Stripe (Dublin, London, Berlin): the default landing pad for senior fintech ICs in Europe.
  • Revolut (London, Berlin, Vilnius): consumer-fintech overlap and aggressive hiring.
  • Wise (London, Tallinn): payments infra, similar scaling stage.
  • Mollie (Amsterdam): smaller, but a common Klarna alumni destination in Benelux.

Watching "started a new position" against those five employers filters your Klarna alumni pool down to the ones who took a real fintech job, as opposed to sabbatical, founder, or consulting. That is a much sharper outbound trigger than the leaver signal alone, because it tells you the person is in-market and comparable roles are landing.

The playbook: how to source a silent shrink

Sourcing a silent shrink is four moves, and they generalize past Klarna to every company that copies the playbook.

1. Set a standing "previously at" query, not an alert

Alerts fire once. The Klarna shrink runs for five years. Build a saved query that returns everyone who has updated their profile from "Klarna" to a new employer in the last 30 days, and re-run it weekly. In a manual LinkedIn workflow, that is a saved search with the "changed jobs in past 90 days" filter plus a "past company: Klarna" filter, refreshed on a calendar reminder.

2. Segment by hire cohort, not by title

The 2020 to 2021 hire cohort at Klarna is different from the 2018 cohort. Pandemic-era joiners came in at inflated comp and are now the ones leaving at the five-year mark. Filter the pool by "started at Klarna between Jan 2020 and Dec 2021" if your tooling allows. That is the persona with the biggest gap between current market value and what a stable employer can actually offer them.

3. Cross-reference GitHub for the engineering pool

LinkedIn tells you they left. GitHub tells you what they actually built. Klarna's open-source footprint (the klarna org on GitHub, plus personal repos from ex-Klarna engineers) is where you separate the platform engineers from the CRUD engineers.

4. Time outbound to the walkback

Klarna's AI walkback, reintroducing human support in a gig model, is the leading indicator every AI-forward copycat will hit within 12 to 18 months. When the walkback lands at Company B, the people leaving Company B are the ones who watched the strategy fail from the inside. That is your best outbound window, because those candidates now have a story about why AI-only headcount plans break, and every hiring manager wants to hear it.

The macro: this is going to be most of your pipeline

About 40% of employers expect to cut workforces because of AI. Most will pick attrition over WARN, because attrition is cheaper, quieter, and legally simpler. That means the sourcing workflows that depended on WARN filings, layoff aggregators, and severance leaks are about to cover a shrinking share of the actual talent movement in the market.

The recruiters who win the next five years are the ones who stop waiting for a trigger and start running a stream. Klarna's 630-people-per-year drip is the worked example. Copy the four moves above, point them at whichever AI-forward CEO in your sector announces a headcount target next, and you will be the only inbox those leavers see.

FAQ

How do I find candidates without WARN notices when a company is shrinking silently?

Run a standing query on "previously at [Company]" plus "started a new position in the last 30 to 90 days," and re-run it weekly for the duration of the stated shrink. That is the mechanism Siemiatkowski explicitly pointed to when he told outsiders to "go to LinkedIn." Cross-reference with GitHub for engineers and with the company's own open reqs to identify which functions are being drained versus protected. The signal is a stream, not an event, so your tooling has to support saved queries, not just one-off alerts.

Is the Klarna hiring freeze real if they are still posting jobs?

The freeze is real for most functions and porous for a handful. TechCrunch reported roughly 10 open roles, primarily in Europe, after the freeze was announced. Those roles map to functions Klarna's leadership considers strategically untouchable, mostly relationship and partnership work. Everything not on that list is being allowed to shrink through attrition, which is where your outbound should focus.

Why does the IPO stock drop matter for sourcing Klarna talent?

Klarna's stock is down about 59% since its NYSE debut at a $15B valuation, which means four-year grants issued at IPO pricing are underwater. Employees whose retention math depended on that equity now have a broken hook. That flips Klarna from a hard-to-poach employer to a porous one for the exact cohort (2020 to 2021 hires) that also happens to be at the five-year tenure mark where Klarna employees typically leave anyway.

How many Klarna candidates are actually reachable right now?

In Refolk's index of professional profiles, 268 current Klarna-linked engineering, PM, DS, and ML professionals are reachable now, concentrated in Stockholm and Berlin with tails in Málaga, Milan, and the Netherlands. On top of that standing pool, roughly 12 new leavers per week are entering the open market based on Klarna's stated 21% annual attrition on a 3,000-person base. That is more than 600 new candidates per year from a single employer, with no WARN filing to compete over.

Try it on the search you came here for

Stop building boolean strings. Just describe the person.

Type one sentence. I plan the search, read GitHub, public LinkedIn and Crunchbase records, and the open web as it is right now, and hand back a ranked list with the reason next to every name.

  1. 01Describe them

    One plain sentence. Role, city, stack, stage, whatever matters to you.

  2. 02I read the web live

    GitHub, public LinkedIn and Crunchbase records, the open web. Not a database that went stale last quarter.

  3. 03You read the shortlist

    Ranked, with the reasoning under every name. Open a profile, ask a follow-up, narrow it down.

  • No boolean, no filters, no seat to buy. One box.
  • Read at search time, so a profile updated yesterday counts today.
  • Every step visible as it runs, every name with its reason.

500 free credits on sign-up. No card, no demo call. See real searches.

Read next