PayPal's 4,760 Won't Drop on a Friday. Source the Braintree Middle.

On the May 5, 2026 Q1 call, new PayPal CEO Enrique Lores told analysts the company will shed roughly 4,760 people, 20% of a 23,800-person workforce, over the next two to three years, while admitting PayPal needs to "become a technology company again." There is no WARN notice. There is no single-day list. If you wait for one, you will be sourcing the bottom quartile of a company that just declared its own engineering org under-invested.

The opportunity is the phasing. A 24 to 36 month rolling reduction telegraphs its order of operations through one of the most fingerprinted CEO playbooks in tech: Lores ran HP Inc. for nearly seven years and cut 12% of HP's workforce in 2022, then announced another 4,000 to 6,000 in November 2025 to "redesign processes with AI at the center." We know exactly which functions he eats first. We now also know PayPal's new org chart. Overlay them and you get a quarter-by-quarter sourcing map.

The three units are a literal target list

Effective June 2, 2026, PayPal collapses into three business units:

• Checkout Solutions & PayPal, under Frank Keller (permanent President).
• Consumer Financial Services & Venmo, under Alexis Sowa (interim).
• Payment Services & Crypto, under Jeff Pomeroy (interim), absorbing Braintree, SMB processing, value-added services, and PYUSD.

Two interim leaders out of three is not a stable structure. Interim plus consolidation is the universal signal for "we are still deciding who survives this." Payment Services & Crypto is the most volatile of the three because it stuffs four formerly distinct organizations (Braintree merchant processing, SMB, VAS, crypto) under one acting head. Every redundant director, every duplicate platform team, every parallel SRE rotation between Braintree and core PayPal processing is now a line item.

EVPs Diego Scotti and Michelle Gill, both tied to Venmo, small business, and financial services, are already out. Anshu Bhardwaj, formerly SVP of PayPal engineering, has been elevated to Chief AI Transformation and Simplification Officer. Antonio Lucio, Lores' CMO at HP, has been pulled in as Chief Marketing & Corporate Affairs Officer. When the CEO starts importing his old lieutenants, the incumbents in the same functions inside PayPal are usually three quarters from a goodbye email.

What the HP playbook actually predicts

Lores has run this movie twice. In November 2022, HP announced a 12% reduction and a real-estate consolidation projected to save $1.4 billion in annualized spend by end of FY2025. In November 2025, HP added 4,000 to 6,000 more cuts by end of FY2028, explicitly framed as AI-driven, hitting (in his own words) "product development, customer support and internal operations."

Translate that vocabulary to a payments company and the at-risk functions are:

• Engineering managers and directors layered between ICs and unit Presidents. AI-driven flattening always eats the middle first. Lores' own line is "redesign our processes with AI at the center."
• Customer support and dispute ops. Replaceable with LLM-routed flows, the cheapest sell to a board.
• HR, finance, and back-office ops. Especially anyone whose role overlaps with an HP veteran Lores is about to import.
• Legacy / non-AI engineers on aging payments infrastructure. Lores literally said PayPal "has not put enough money into its technology infrastructure."

The "AI Transformation and Simplification" team under Bhardwaj is the retention org. Everyone outside it is the sourcing pool. Senior engineers reading this on PayPal's intranet right now already know which side of that line they are on, which is why the first wave will be self-select departures, not stack-ranked terminations.

$1.5B

Why a phased RIF is better for sourcers than a WARN drop

A single-day WARN filing dumps 1,000+ resumes into the market on the same Tuesday. LinkedIn lights up green. Every recruiter at Stripe, Adyen, Ramp, Mercury, and Checkout.com pings the same 200 names. Reply rates collapse. Salary leverage shifts to the buyer. You spend three weeks fighting for the median candidate.

A 24 to 36 month rolling cut does the opposite. The strongest people read the signal first ("our CEO just called us legacy on a public earnings call") and start taking calls in Q2. The middle tier waits for a package in Q3 or Q4. The bottom quartile is still hoping by Q2 2027. If you source on the signal, not the announcement, you get first pick at every quarterly cohort.

This is exactly the sourcing problem Refolk was built for: instead of waiting for a layoff list to be scraped and shared, you describe the cohort in plain English ("Staff engineers at PayPal Braintree in Chicago or the Bay Area, 8+ years payments infra, not on the AI transformation team") and get a ranked shortlist across GitHub, LinkedIn, and the open web. The reduction is rolling. Your sourcing should be too.

The cohorts to sequence

Quarter one: Braintree platform engineers

Braintree was acquired in 2013 and runs deep merchant-processing infrastructure. It is now inside a unit run by an interim President. Braintree engineers are the single most pickable cohort in the entire reorg because (a) their domain knowledge is the most portable in fintech, and (b) Stripe, Adyen, and Checkout.com will pay premiums of 30 to 50% on base for proven card-not-present chops.

Concentrate sourcing in Chicago (Braintree's legacy HQ) and the Bay Area. The senior engineers here are the highest-leverage targets in the entire 4,760.

Quarter two: dispute, risk, and SMB ops engineering

Lores' HP cuts hit "customer support and internal operations." The PayPal analog is the dispute-resolution and risk-tooling engineering teams, plus the SMB processing groups now folded under Pomeroy. These are well-paid IC engineers building internal tools, not user-facing product. They are also exactly the roles AI vendors pitch as "fully automatable" in board decks, which means they are first to be benchmarked against an LLM and found wanting (see Block).

Quarter three: middle management across all three units

Watch for title-flattening announcements roughly six months after the June 2 reorg date. Lores' HP language was "stripping out redundant structures." That is corporate for "we are removing a layer of directors." Engineering managers with 5 to 8 reports inside a 30-person org are the bullseye. Ramp, Mercury, and Klarna all want engineering leaders who have shipped at fintech scale and will not insist on a VP title in year one.

Quarter four and beyond: India ops

Roughly 2,400 PayPal-tagged software engineers sit across Bengaluru, Hyderabad, and Gurugram. India ops is typically the last cohort to feel a US-announced RIF, but it is also where consolidation savings compound. By late 2026, expect platform-team duplication between US and India org charts to be resolved unilaterally toward the cheaper geography in some teams and away from it in others. Watch for hiring freezes in specific Bengaluru orgs as the leading indicator.

The Block cautionary tale, and why it argues for sourcing harder

Earlier in 2026, Block cut nearly 40% (~4,000 people) on an AI productivity thesis. By March, Block was quietly inviting laid-off engineers and recruiters back, with employees saying certain tasks "can't really AI that." The lesson for recruiters at fintech competitors is not "PayPal will rehire too." It is that any company over-cutting on an AI thesis creates a six to nine month window where the released engineers are available, validated by a competitor's hiring desperation, and emotionally done with the original employer. PayPal's window is longer because the reduction is phased.

The strongest engineers leave on the signal. The median ones leave on the package. The rest leave on the WARN notice.
</pull>

## Outreach: lead with domain, not with sympathy

The worst PayPal outreach in your competitors' inboxes right now reads like a condolence card. "I saw the news, must be a tough time, would love to connect." This pattern-matches to a layoff scavenger and gets archived.

What works on senior PayPal and Braintree engineers:

1. **Name the specific system they own.** "I noticed you've been on the vault tokenization side of Braintree since 2019" beats any generic pitch.
2. **Acknowledge the technology-company-again framing without dunking on PayPal.** These engineers know the infrastructure debt. They do not need you to tell them.
3. **Lead with the equity and architecture differential.** Stripe, Adyen, Ramp, and Mercury are all hiring payments-infra engineers right now. The pitch is "you'd be in a green-field rebuild, not a legacy maintenance cycle."
4. **Skip Venmo engineers.** Venmo posted 14% TPV growth in Q1 2026 and is the structural bright spot of the new org. Those people are retention targets and your reply rates will reflect that.

If you are sourcing PayPal engineers at any scale across the next 24 months, the bottleneck is not the list, it is the segmentation. Which IC sits inside Bhardwaj's AI transformation org and which sits adjacent to it? Which Braintree engineer reports up to Pomeroy versus Keller? This is where Refolk earns its keep: plain-English queries over the org reality, not stale title taxonomies.

## What to monitor as leading indicators

- **HP-to-PayPal exec moves on LinkedIn.** Antonio Lucio was the first. Each additional HP veteran landing in ops, finance, or HR is a one-quarter warning on the incumbent team they're displacing.
- **Internal req volume by unit.** Checkout Solutions under Keller (permanent leader) will hire offensively; Payment Services & Crypto under Pomeroy (interim) will mostly backfill. The hiring/cutting ratio inside each unit will diverge within two quarters.
- **Bhardwaj's AI org headcount.** Growth there is the cleanest signal of who is "in." Cross-reference against the rest of engineering for who is "out."
- **Bengaluru and Hyderabad team-level posting drops.** When a specific Bengaluru team stops posting for six weeks, the consolidation decision has been made internally even if it has not been announced externally.

The 4,760 is not a deadline. It is a calendar. Read it like one and fintech engineer hiring across the next six quarters looks less like a scramble and more like a draft.

## FAQ

### Should I wait for a public PayPal layoff list before reaching out?

No. The strongest engineers will be gone by the time any list circulates. Phased RIFs reward sourcers who act on signal (CEO public framing, interim leaders, EVP departures) rather than on confirmation. By the time a name shows up on layoffs.fyi, three of your competitors have already had two coffee chats with them.

### Are Venmo engineers worth sourcing right now?

Generally no. Venmo posted 14% TPV growth in Q1 2026 and is the rare growth pocket inside PayPal. Engineers there are retention targets with retention comp packages attached. Reply rates will be poor and any wins will be expensive. Spend your cycles on Braintree, SMB processing, dispute and risk tooling, and middle-management layers in Checkout and Payment Services.

### How does the Lores HP playbook differ from a typical big-tech RIF?

It is slower, more surgical, and explicitly AI-framed. Lores does not do single-day actions. The 2022 HP cut ran through FY2025; the 2025 HP cut runs through FY2028. He targets middle management, customer support, internal operations, and legacy product engineering in that order, and he imports trusted lieutenants from his prior org to displace incumbents. Expect the same shape at PayPal across 2026 through 2028.

### What does "become a technology company again" mean for sourcing?

It means PayPal's own CEO publicly classified the existing engineering org as under-invested infrastructure rather than a competitive moat. That language gives every senior PayPal engineer permission to take a recruiter call without feeling disloyal. Lead with the architecture and green-field opportunity at Stripe, Adyen, Ramp, Mercury, or Checkout.com, and you will see reply rates that you would not get from a comparable signal at a healthier employer.