Dorsey Cut 4,000 at Block. The 748 Killed Reqs Are the Real List.

If you're a fintech recruiter in the Bay Area, the largest concentrated sourcing event of the year just landed on your desk, and almost everyone is going to source it wrong. Jack Dorsey cut nearly 4,000 of Block's 10,205 employees on February 26, 2026, on top of a March 2025 restructure that closed 748 open reqs and pushed 193 managers into IC seats.

Dorsey told the Long Strange Trip podcast that his ideal Block has "no layer," with everyone reporting to him. That philosophy is the mechanism producing the sourceable cohorts below, and it's the reason the layoff list is the least interesting thing about this event.

What actually happened at Block, in numbers

Block cut ~4,000 of ~10,205 employees on February 26, 2026 (a 40.7% reduction), on top of a March 2025 restructure that laid off 931, eliminated 80 manager roles, moved 193 managers into IC seats, and closed 748 open reqs. Gross profit grew 24% year over year to $2.87B in Q4 2025, so this is a structural, not financial, cut. The stock jumped more than 20% after hours from roughly $52, which is the market's way of telling you Block will not reverse this and rehire the cohort.

Dorsey framed it as AI-driven. In Steven Levy's Wired interview he named Anthropic Opus 4.6 and OpenAI Codex 5.3, released in December 2025, as the specific trigger. That matters for sourcing because it tells you which cohort inside the 4,000 he considered redundant: code-writing ICs on established codebases. It does not tell you infra engineers, payments-domain specialists, or system designers were cut for capability reasons. They were cut for org shape.

The "innercore+4" language, first used in Dorsey's March 25, 2025 all-hands email, caps org depth at Dorsey's direct reports plus four levels beneath. That is the mechanism producing the 193 forced demotions and the 748 killed reqs.

748

Why the 748 killed reqs beat the 4,000 layoffs

The 748 candidates dropped mid-loop when Block closed reqs are a higher-signal cohort than the layoff list, because they were vetted enough to be in-pipeline at a top fintech and then dropped through no fault of their own. Every recruiter in the Bay is chasing the layoff list. Nobody has an owner for the killed pipelines.

Here's the mechanism. When a req closes, the ATS relationship goes cold within days. The Block recruiters who ran those loops were themselves cut in both waves, so there is no warm-transfer path. The candidates get a form email and disappear into the silver medalist graveyard of an ATS that no longer has active users. The ratio is stark: 748 killed reqs against 931 March 2025 exits is 0.80 dropped candidates per layoff. Apply the same ratio to the 4,000 February 2026 exits and you're looking at another ~3,200 mid-loop candidates orphaned in the last 12 months.

The catch: these people never appear on a "laid off from Block" list because they never worked at Block. They're at their current employers, unhappy enough to have entered a Block loop, and now doubly frustrated. That's the exact gap Refolk closes: you describe the person you want ("senior payments engineers who interviewed at Block or Square in 2025 and are still at their previous employer") and get back a ranked shortlist across GitHub, LinkedIn, and the open web, instead of trying to reverse-engineer an ATS you don't have access to.

The 193 demoted managers: a comp-arbitrage window

The 193 managers Block force-converted to IC in March 2025 are interviewing for IC roles at IC comp while carrying manager tenure and cross-functional context, which is a rare asymmetry with a shelf life of about six months. By mid-2026, they'll have relevelled their expectations upward and this window closes.

Why it works: at Block they lost the manager title involuntarily, so they can't credibly hold out for another EM slot in this cycle. But their scope memory (roadmaps, cross-team dependencies, incident command) is intact. If you're a founder hiring engineer #8 who can also run a small pod later, this cohort is priced 20 to 30% below their steady-state market. Move now or watch Ramp and Coinbase do it for you.

The 193 demoted managers are interviewing at IC comp with manager tenure intact. That asymmetry closes by mid-2026.

Segment the pool by bucket before you outreach

The March 2025 letter split cuts into three explicit buckets (460 performance, 391 strategic, 80 manager eliminations) plus the 193 demotions and 748 killed reqs, and you should segment your outreach by which bucket the candidate came from. Treating them as one "ex-Block" list buries your best cohorts.

• Performance-managed out (460, March 2025): reputationally loaded. Skip unless you have specific signal.
• Strategic reductions (391, March 2025): safe cohort, cut for org reasons.
• Manager roles eliminated (80, March 2025): senior, likely already placed. Long tail.
• Managers demoted to IC (193): the comp-arbitrage window described above.
• Killed-req candidates (748): never worked at Block, highest signal, zero incumbent owner.
• February 2026 general cut (~4,000): broad, still being triaged by the market as of writing.

The February 2026 cohort has not yet been publicly split into the same buckets, but an unverified Blind thread claims "70% of Engineering was laid off," which is consistent with Dorsey's Opus/Codex framing. Treat that as directional until Block's next 10-Q.

The Boolean everyone is running is missing half the pool

An "ex-Square" or "ex-Block" LinkedIn Boolean systematically misses roughly half the addressable pool, because Block owns six brand headlines that people index under independently. Search only "Block" and you drop every Cash App PM who never updated their tagline. Search only "Square" and you miss the Afterpay cohort.

The brands you have to OR together:

1. Block
2. Square
3. Cash App
4. Afterpay
5. Tidal
6. TBD
7. Bitkey

(That's seven if you count Block as the parent. All seven appear as current-role text in Refolk's index.)

Even that Boolean assumes people keep their headlines current, which senior engineers famously do not. A stronger approach is to describe the person: "staff-level payments infrastructure engineer who worked on Square Seller or Cash App between 2020 and 2025, now based in the US." Refolk resolves that across profile history, GitHub commit patterns, and open-web mentions in one pass, instead of forcing you to maintain a seven-clause Boolean that decays every quarter.

Where the pool actually lives (it's not just SF)

In Refolk's index of professional profiles, the top current regions for people with Block, Square, Cash App, Afterpay, or Tidal in their headline are San Francisco, New York, San Francisco Bay Area, Brooklyn, Chicago, Los Angeles, Seattle, Bend OR, and Frisco TX. If you're only sourcing SF, you're missing roughly 60% of the pool.

This is a distributed remote cohort, not a Bay Area concentration. The Bend, Oregon and Frisco, Texas signals are the remote-first hires from 2021 and 2022 who never moved back. For a Bay Area fintech recruiter, the practical implication: your comp band needs a remote tier, and your top-of-funnel geography filter should be "US" not "SF Bay Area + willing to relocate."

Sizing the opportunity against your total addressable market

One Block restructure lands roughly 5.9% of the entire US senior fintech engineering pool onto the market inside a 90-day window, based on Refolk's index sizing.

The Block cut is concentrated, dated, geographically legible, and happens to be exactly the domain (payments, consumer fintech, crypto rails) that your Series B fintech client needs. Treat it accordingly.

The 20-week severance clock is your urgency lever

Block's February 2026 severance package is 20 weeks base plus one week per year of tenure, with equity vesting through end of May and six months of healthcare, so the effective warm window before financial pressure escalates is roughly 12 to 20 weeks post-exit. Time your outreach to that curve.

Historical layoff data shows time-to-offer accelerates sharply once severance runway drops below 8 weeks. That maps to a sweet spot for recruiters between roughly week 12 and week 16 post-exit, which for the February 2026 cohort means late May through late June 2026. Reach out too early (weeks 1 to 4) and candidates are still decompressing and holding out for their old comp. Reach out too late (week 20+) and Ramp, Coinbase, Stripe, Chime, Brex, Mercury, and Plaid have already closed them.

The $5,000 transition payment Block included is small but psychologically real: it funds a laptop refresh and a bootcamp, which nudges some engineers toward a career pivot (AI eval, security, infra) instead of a lateral fintech move. Segment for that if your req is off-lane.

A concrete sourcing plan for the next 60 days

The fastest path to closing three ex-Block hires in the next 60 days is to skip the layoff list, prioritize the 748 killed-req cohort and the 193 demoted managers, run a seven-brand Boolean across the whole US (not just SF), and time outreach for weeks 12 to 16 post-exit.

Sequence:

1. Build a target company list of the six Block sub-brands plus adjacent fintechs where ex-Block managers landed after the March 2025 wave.
2. Filter for tenure ≥ 3 years to exclude the performance-bucket noise.
3. Cross-reference against 2025 Block or Square interview mentions in public sources (Blind, X, Reddit r/cscareerquestions) to surface the killed-req cohort.
4. Segment demoted managers by looking for people whose title dropped from Manager or EM to Senior or Staff between March and September 2025.
5. Sequence outreach in week 12 to 16 of severance, ordered by fit score.
6. Position the role's scope explicitly against Block's flattening: engineers who just lived through innercore+4 want either radical flatness or radical structure, not another five-layer org.

If you don't want to run steps 1 through 4 by hand, that's the workflow Refolk automates. Describe the person in plain English (segment, tenure, sub-brand, current location, negative filters for the obvious landing pads) and get the ranked list back, with the profile evidence attached.

FAQ

What does "innercore+4" mean in Dorsey's org design?

Innercore+4 is Dorsey's cap on org depth: his direct reports (the innercore) plus a maximum of four layers beneath them. He introduced it in the March 25, 2025 all-hands email that also announced the 931-person cut and the 748 killed reqs. On the Long Strange Trip podcast he went further, describing an ideal state with "no layer" and everyone reporting to him directly. The February 2026 cut of 40.7% of Block's workforce is the operational move toward that ideal.

How is the 4,000-person February 2026 cut different from the 931-person March 2025 cut?

The March 2025 cut was structural triage (460 performance, 391 strategic, 80 manager eliminations, 193 demotions, 748 killed reqs) and small enough to bucket precisely. The February 2026 cut is roughly 4.3x larger in absolute terms and Dorsey has publicly attributed it to AI capability crossing a threshold in December 2025, specifically Anthropic Opus 4.6 and OpenAI Codex 5.3. Block has not yet published a bucket breakdown for the February 2026 wave, but the framing implies code-writing ICs on mature codebases were disproportionately affected.

Which competitors are already hiring the ex-Block cohort?

Ramp and Coinbase are the top current landing pads for US fintech engineers in Refolk's index sample, with Chime, Brex, Mercury, Plaid, and Stripe also actively picking off ex-Block ICs across the Bay Area, New York, and Brooklyn. If you're a Series B fintech competing for this pool, assume every candidate you touch is already in a loop at two of those seven companies, and price your speed accordingly.

Is it worth sourcing the "performance-managed out" bucket?

Generally no, unless you have specific reference signal. The March 2025 letter explicitly labeled 460 exits as performance-related, which creates a reputational overhang that is hard to neutralize in a competitive loop. The 391 "strategic reductions," the 193 demoted managers, and especially the 748 killed-req candidates are all higher-signal segments with none of that stigma. Start there and only touch the performance bucket when you have a warm referral vouching for the individual.