Coinbase Cut 700. The Ex-Coinbase Senior IC Pool Is 293.

Two months after Brian Armstrong cut ~700 people (14% of Coinbase) on May 5, 2026, the resumes hitting your inbox are lying to you in a very specific way. "AI-native pod." "One-person team." "Player-coach across eng, design, and PM." Most of the affected engineers worked in conventional service orgs. The label is retrofitting.

Here is what the pool actually looks like, which Coinbase surfaces produce real senior IC signal, and why teams running loops past day 28 are losing this cohort to whoever moved first.

The pool is 293 senior ICs and it skews away from managers

In Refolk's index of professional profiles, there are 293 senior, staff, and principal engineers in the US with Coinbase in their headline, and only 19 are still listed at Coinbase. The remaining ~274 are ex-Coinbase or transitional, with early landing spots already visible at Bridge, EarnIn, Polymarket, Phantom, and Meta.

The manager number is the tell. Refolk's index shows only 69 engineering managers, senior EMs, and directors with Coinbase headline signal in the US. That is a 4.2 : 1 ratio of senior ICs to eng managers in the ex-Coinbase pool, which quantifies what staffing firms have been saying anecdotally: the May cut disproportionately hit a senior IC bench that a prior reorg had protected.

Kore1's candidate-flow read is blunt about the mechanism:

Line ICs had been pushed into the new player-coach model six months ago. The senior bench had not.

So the "senior IC glut" is a mechanical artifact of which layer the prior reorg spared, not a talent-quality signal. Treating this cohort like a performance filter is a mistake. Being cut from Coinbase in May 2026 is closer to a random draw within the affected orgs.

4.2x

What "AI-native pod" on a Coinbase resume actually means

In most cases it means nothing specific. Armstrong's memo proposed one-person pods as an experiment, framing the rebuild as "an intelligence, with humans around the edge aligning it." The vast majority of the ~245 to 315 engineering cuts came from international product, trust and compliance, and platform groups. Traditional service teams. Not pods.

When you see "AI-native pod" on a resume, screen for three artifacts. If the candidate cannot name all three, the phrase is post-hoc rebranding:

1. The agent framework they owned. LangGraph, a homegrown orchestrator, an internal fork. Name it.
2. The model gateway or router. Which providers, which fallback logic, which cost controls.
3. The eval loop. How regressions were caught, who owned the golden set, what shipped/didn't ship based on evals.

The "one-person team hiring" pattern Armstrong described (a single IC balancing eng, design, and PM) is real but rare. If someone genuinely ran one, they will describe it in mechanics, not adjectives. If they describe it in adjectives, you are reading marketing.

There is also a source-level reason to discount the "AI-native" framing entirely. Mizuho Securities analyst Dan Dolev told Bloomberg the crypto downturn is "probably the real reason for most of the cuts" and that AI is "an easy excuse." That is the counter-frame worth carrying into every screen: the layoff conveys almost no negative signal about the engineer, and the "AI-native" label conveys almost no positive one.

The Coinbase teams that actually produce signal

Not all Coinbase surfaces are equal. Per Kore1's candidate flow, three product areas were protected in the May cut: Onchain Payments, Base (the L2), and the exchange core. Engineers who left those groups after May are self-selected voluntary movers, and they carry the deepest crypto-native signal in the pool.

The cut concentrated on:

• International product
• Trust and compliance
• Platform groups not directly serving Onchain Payments, Base, or the exchange core

For sourcing senior IC crypto engineers, that split matters. An ex-Coinbase platform engineer from a compliance-adjacent team is a good generalist backend hire. An ex-Base engineer who left voluntarily in June is a different (and much scarcer) animal. Do not price them the same.

This is the exact gap Refolk closes when you're hiring ex-Coinbase engineers: instead of a "past company: Coinbase" LinkedIn filter that returns 293 profiles with no context, you describe the person in plain English ("senior Solidity engineer who shipped on Base and left Coinbase after May 2026") and get a ranked shortlist with the team signal already resolved.

The numbers, in one table

Two things to notice. First, the pool is small: 293 senior ICs across the US is not a firehose, and roughly half cluster in San Francisco, Mountain View, and New York. Second, the landing spots are competitive bidders. Bridge (stablecoin infra), Polymarket (prediction markets), and Phantom (wallets) are actively hiring the same profile you are.

Solidity is priced up, not down

The crypto slump did not soften the Solidity market. It sharpened it. Per Kore1's read of 2026 fintech candidate flow, a senior Solidity offer below $240K base in 2026 will lose, because supply of engineers who can audit and ship production-grade smart contracts at scale never caught up with L2, app-chain, and agentic-payments demand.

If you walk into this pool assuming "crypto is down, so onchain talent is cheap," you will lose every meaningful loop. The pricing logic is:

• Generalist senior fintech ICs from Coinbase compliance or platform: softening, negotiable.
• Solidity, Base, and Onchain Payments ICs: premium, competitive, moving fast.
• ex-Coinbase engineers with agentic-payments exposure: essentially uncapped, because the receiving market includes stablecoin infra plus every AI-payments startup.

The 28-day cliff is real, and severance is the reason

Teams that keep the interview loop under two weeks are closing this cohort. Teams running three rounds plus panel plus committee lose the candidate by day 28. The mechanism is severance.

Affected US Coinbase employees received:

• At least 16 weeks of base pay, plus two weeks for every year of service
• Their next equity vest
• 6 months of COBRA (healthcare continuation)

That is roughly 16 to 24 weeks of runway before financial pressure kicks in. Combined with Kore1's benchmark that average time-to-hire across their IT placements is 17 days, the math for the receiving team is unforgiving: candidates have no reason to tolerate a slow loop, and every additional round is a roughly 15 to 20 percent conditional drop-off in this cohort.

The practical rewrite for Coinbase layoffs 2026 engineering hiring:

1. Recruiter screen and hiring manager screen collapsed into one 45-minute call, day 1 to 3.
2. Technical loop (2 to 3 sessions) run on a single day, day 7 to 10.
3. Debrief and offer, day 11 to 14.
4. Sign, day 14 to 21.

If your committee meets weekly and your panel needs three calendar weeks to assemble, you are not competing for this pool. You are watching Bridge and Polymarket compete for it.

How to actually screen the "AI-native" claim

Assume the phrase is decorative until proven otherwise. AI-native pod resume screening works when you replace the label with three specific questions and hold the candidate to naming artifacts, not adjectives.

Use this decoder in the first 15 minutes of the recruiter screen:

• "Name the eval you owned." Not "we used evals." Which suite, which metrics, who signed off on regressions.
• "What was the model gateway?" In-house, LiteLLM, Portkey, something else. If they cannot answer, they were not close to production LLM traffic.
• "How many humans were in your pod, honestly?" Armstrong's "one-person team" was an experiment. Most ex-Coinbase engineers worked in 6 to 12 person teams. That is fine. Lying about it is not.
• "Which of these did you touch: Onchain Payments, Base, exchange core?" Cross-check against team-level signal. This is where the real crypto-native engineers self-identify.

The candidates who answer these cleanly are the ones worth the premium. The candidates who pivot to adjectives ("we were very AI-forward, very pod-shaped") are fine hires, just not for the reasons their resume claims. Refolk's plain-English queries make this easier upstream: you can ask for "ex-Coinbase engineers who shipped LLM eval infrastructure, not just used it," and skip the resume-label game entirely.

Parallel pools worth cross-referencing

The Coinbase pool is not the only supply hitting the market in Q2 2026. If you are doing serious sourcing senior IC crypto engineers, cross-reference these peer cuts:

• Crypto.com: 180 cuts, March 2026
• Block: 4,000 cuts, February 2026
• Bolt: 250 cuts, April 2026
• MARA Holdings: 40 cuts, April 2026
• Gemini: 200 cuts, February 2026
• PayPal: ~4,760 jobs reduced over 2 to 3 years, announced May 5, 2026 (same week as Coinbase)

The PayPal cohort matters because it overlaps ex-Stripe payments engineers, which is the same profile Bridge and the agentic-payments startups are chasing. If you are only sourcing from the Coinbase 293, you are ignoring a much larger adjacent pool with overlapping skills and less competitive pricing.

What to do this week

Three moves, in order:

1. Rewrite the loop to close in 14 days. Anything longer loses to competitors already in-flight.
2. Segment the 293 by team, not by title. Onchain Payments, Base, and exchange core alumni are premium. Compliance and international platform are the generalist tier.
3. Price Solidity at $240K base or higher. Below that, do not bother running the loop.

The layoff itself is not a filter. Armstrong's memo is not a spec. The only real signal in this pool is which team the engineer sat on and what artifacts they can name. Get those two questions right in the first screen and you will out-hire the teams still reading "AI-native pod" as if it meant something.

FAQ

How many ex-Coinbase senior engineers are actually available in the US?

Refolk's index shows 293 senior, staff, and principal engineers with Coinbase in their headline in the US, of whom 19 are still at Coinbase. That leaves roughly 274 who are ex-Coinbase or actively transitional, concentrated in the SF Bay Area, New York, Seattle, and Denver. Early landing spots include Bridge, EarnIn, Polymarket, Phantom, and Meta, all of which are competitive bidders.

Is "AI-native pod" on an ex-Coinbase resume a real credential?

Almost never. Armstrong's May 5 memo proposed one-person pods as an experiment, and the vast majority of the ~245 to 315 engineering cuts came from conventional service teams (international product, trust and compliance, platform). Screen the claim by asking the candidate to name the specific agent framework, model gateway, and eval loop they owned. If they cannot, the label is retrofit.

Should crypto engineers be priced down given the market?

No, at least not for the onchain sub-bench. Per Kore1's read of 2026 fintech candidate flow, a senior Solidity offer below $240K base in 2026 will lose, because supply of engineers who can ship production-grade smart contracts at scale never caught up with L2, app-chain, and agentic-payments demand. Generalist ex-Coinbase platform engineers are softening; the Solidity, Base, and Onchain Payments cohort is priced up.

Why does a 28-day interview loop lose this cohort specifically?

Coinbase's US severance package includes at least 16 weeks of base pay (plus two weeks per year of service), the next equity vest, and 6 months of COBRA. That gives candidates 16 to 24 weeks of runway with no financial pressure to accept a slow loop. Adjacent fintech data shows a 17-day average time-to-hire wins; loops that stretch past day 28 lose to whoever closed first, typically Bridge, Polymarket, or Phantom.