Chime Cut 150 After Going 29% to 84% AI-Authored. Sourcing Playbook.

On July 31, 2026, five days before Q2 earnings, Chime CEO Chris Britt announced 150 layoffs and told the company that "AI is changing what's possible but requires new skills." The same company had already disclosed that AI-assisted code shipped internally jumped from 29% to 84% in four months.

That makes this the first named public-company cut where the AI-fluency signal is quantified on both sides of the memo, and it is the cleanest sourcing event fintech recruiters will see this quarter.

Why this cohort is different from every other 2026 fintech layoff

The ex-Chime engineers cut on July 31 are the rarest profile in fintech right now: production experience shipping AI-authored code inside a regulated banking stack. That is not a resume claim, it is a disclosed operating metric.

Most "ex-fintech engineer" pools in 2026 are generic. Block cut about 4,000 in February. Coinbase trimmed 700 in May. Bolt shed about 30% in April. Crypto.com cut roughly 180 in March. Those are big numbers, but the engineers land on the market with the same story every other candidate has: "I used Copilot sometimes." The Chime cohort lands with a specific, disclosed, publicly cited claim: they were the humans in the loop when a regulated neobank tripled its AI-authored code share in a single quarter, while engineers reported average time savings of around four hours a week.

That includes the review workflows, the hallucination guardrails, the compliance sign-off procedures for AI-generated code, and the internal tooling that let 84% of shipped code originate with an assistant. Almost no one outside the top 20 fintechs has done that yet.

29% → 84%

The pool is 223. The window is about three weeks.

Refolk's index shows 223 U.S. engineers with a Chime affiliation in their profile, 16 of whom currently list Chime as employer. If the July 31 cut skews engineering-heavy, a meaningful share of Chime engineering hit the market on the same Friday.

Here is the math. Chime had about 1,500 employees at the end of last year. If engineering is around 30% of that (a conservative fintech ratio), that is roughly 450 engineers. A 150-person cut that concentrates in engineering and AI-integrated support could put up to a third of Chime engineering on the market simultaneously. That is a batch-liquidity event, not a trickle.

First-mover recruiters get the top decile. By week three, the engineers with the sharpest AI-native story have signed. This is where "search LinkedIn for ex-Chime" fails: the query returns everyone who ever interned there, ranked by keyword density, not by whether they touched the code-review pipeline that got 84% of production shipped by an assistant. Describing the profile in plain English is the exact gap Refolk closes: ask for "senior backend engineers who left Chime in the last 60 days, based in the Bay Area, with signals of AI tooling ownership," and get a ranked shortlist instead of a keyword dump.

Where the engineers actually are

The Chime engineer pool is San Francisco heavy, with a thin but real presence in New York, Austin, and Chicago. That geography is the entire sourcing strategy.

Concentration by region, from Refolk's index of Chime-affiliated engineers:

• San Francisco: 6
• SF Bay Area (broader): 5
• New York: 2
• Additional presence in Chicago, Menlo Park, McLean VA, San Jose, Sunnyvale, Boulder, and Austin

Ramp's engineering footprint (244 U.S. engineers, 21 currently at Ramp) sits in New York (9), SF Bay Area (3), Denver (2), and Austin (2). That is a clean overlap on the Bay Area and Austin nodes, and Ramp already has a "Software Engineer, Applied AI" title on its engineering ladder. It is the closest one-to-one absorption slot for the profile Chime just cut.

Mercury and Brex, both SF-based, pull from the same commute radius. Brex has publicly leaned into AI-native ops. Against Ramp's 21-engineer current bench, the 150-person Chime cut represents roughly 7.1x their in-seat engineering headcount, which means the acquisition math actually works.

The RTO clause is a second push factor, and most recruiters will miss it

Britt's memo did not just announce cuts. It also mandated more in-office work, which turns geography into a lever competitors can pull without a comp bump.

The exact language: "the best innovations, the fastest decision making and winning culture is created when tight knit teams collaborate in person." Read against the layoff, that is a two-part message to the survivors: the ones who stay come in more, and the ones who left were not part of the "tight knit" plan.

For sourcing, this means the outbound message writes itself. A Bay Area engineer who joined Chime under a flexible arrangement and now faces either termination or a return-to-office mandate is not looking for a 15% raise. They are looking for a company that will let them keep the life they built. Mercury (hybrid) and any remote-friendly Series B can win those candidates on lifestyle terms before comp is on the table.

Britt needed a Q2 story. The engineers who left did not fail. They just were not the story.

The support and ops engineers are in this cut too

Chime said in a July 29 post on X that it was included in a recent Bain & Company report as an example of a company that rebuilt its customer service around AI. Read against a layoff announced two days later, that means the July 31 cut hit AI-integrated support and ops roles, not just backend SWEs.

The cohort on the market includes:

1. Backend and platform engineers who owned the AI-in-CI pipeline
2. Applied ML engineers who tuned the code-authoring stack
3. Support tooling engineers who integrated LLM agents into the customer service flow
4. Ops engineers who owned the human-review layer on top of AI decisions

Decagon, Sierra, and Crescendo are the natural buyers for cohorts 3 and 4. They are hiring engineers who have already integrated agents into a regulated support workflow at consumer scale, which is exactly the resume Chime just handed out.

What changed between April and July

Britt spoke at the Semafor World Economy Summit on April 15, 2026, and by July 31 he was cutting 10% of the company. The 29% figure was disclosed earlier in the year. By the July memo, that number was 84%. Two mechanisms explain the jump, and both matter for how the outreach lands:

• Compounding tooling. Once code review, CI, and merge automation catch up to AI authorship, the ceiling on assisted code moves fast. Engineers who built that pipeline are the ones to target.
• Pre-earnings margin pressure. Chime went public in June 2025, shares are down about 10% this year, and the cut hit five days before Q2 results. The honest question for the business is whether AI produces durable efficiencies or simply gives management a more modern label for trimming payroll.

Either framing works for outreach. The candidate does not need to believe management's story. They need to believe that the next company will not repeat it. Recruiters who lead with "Chime needed a Q2 story, your resume did not fail" get replies. Recruiters who lead with "we saw you were laid off" do not.

The broader July context shortens the window

Employers announced 62,075 job cuts in July, a 29% increase from June and a 140% surge over July 2024. That macro backdrop means every fintech recruiter is fishing in the same pond, and the ex-Chime cohort will be worked hard.

Every ATS-native sourcer is going to build the same Chime saved search this week. That is fine. The differentiation is not the search, it is the ranking. The 223-person pool is not the shortlist. The shortlist is the 15 to 25 engineers whose GitHub, LinkedIn history, and open-web footprint show they actually owned an AI-in-production surface, not just used Copilot at their desk.

That ranking is where a plain-English query beats Boolean. "Ex-Chime senior backend engineer, last two years, AI-in-CI or code review automation signal, based in SF or open to hybrid in NY" is a sentence, not a filter stack. The point is not to replace the recruiter, it is to compress the 223 down to the 20 who actually match, in an hour, not a week.

What to do this week

Move now, with three specific actions. The pool is finite, the story is dated, and the competition already saw the same headlines.

1. Pull the 223 today, not next Monday. Filter to engineers with tenure of 12+ months at Chime and a title of Senior Software Engineer or above. Refolk's index shows 10 Senior Software Engineers and 13 Software Engineers in the Chime-affiliated pool, so the sharp end of the list is small.
2. Segment by geography against your own footprint. If you have a New York office, the six SF-based Chime engineers are not your primary target unless you are remote-open. Play to overlap, not aspiration.
3. Lead outbound with the disclosed number, not the layoff. "You worked at the company that went 29% to 84% on AI-authored code in four months. That is the exact experience we are hiring for." That message respects the candidate and puts the recruiter on the right side of the memo.

The July 31 cut is a rare event: a named layoff at a public neobank with quantified AI-fluency signal on both sides. It will not repeat cleanly. The recruiters who treat it as another "ex-fintech" list will spend Q3 wondering where the AI-native hires went. The ones who treat it as a three-week sourcing window will have offers out before Chime's Q2 call is over.

FAQ

How many ex-Chime engineers are actually reachable right now?

Refolk's index shows 223 U.S. engineers with a Chime affiliation, of whom 16 currently list Chime as employer. The July 31 cut affects nearly 150 employees total across engineering, support, and ops. If engineering is around 30% of Chime's 1,500-person headcount, up to a third of the engineering org could be on the market at once, concentrated in San Francisco and the broader Bay Area.

Why is the 29% to 84% figure more important than the layoff itself?

Because it is a rare, disclosed, quantified operating metric. Almost no engineer outside the top 20 fintechs can honestly claim production experience with AI-authored code inside a regulated banking stack. The Chime engineers can, and Chime itself put the number in writing. That makes the cohort defensible in a hiring committee in a way that "used Copilot at a previous job" is not.

Which companies are the natural buyers for this cohort?

Ramp is the closest match, with 244 U.S. engineers in its orbit, 21 currently at Ramp, and an existing "Software Engineer, Applied AI" title. Mercury and Brex compete on similar consumer-adjacent and corporate banking surfaces. For the support and ops engineers hit by the Bain-report cohort, Decagon, Sierra, and Crescendo are the natural absorbers because they specialize in AI customer support tooling.

How fast do I need to move?

About three weeks. The top decile of any named layoff cohort signs quickly, and July 2026 had 62,075 announced cuts overall, meaning every recruiter is working similar lists. The advantage is not being first to the pool, it is being first with a ranked shortlist of the 15 to 25 candidates who actually match your open roles.