Back on May 5, PayPal put a number on its turnaround: roughly 4,760 jobs, 20% of the workforce, two to three years to execute, $1.5 billion in savings as the target. CEO Enrique Lores framed the cuts as PayPal “becoming a technology company again.” The first roles named as likely to go, according to employee accounts surfacing at the time, were merchant support, customer service, and PayPal’s own internal AI team.
Four months later, the first concrete tranche has a filing behind it, and it names a different set of jobs than the May story predicted.
The filing
On Sept. 4, PayPal filed a WARN Act notice with California’s Employment Development Department covering 251 employees at its San Jose headquarters, effective Oct. 30. The filing itemizes roles: more than 100 engineering positions, over 50 senior software engineers, nearly 50 directors, and more than 40 senior managers. Add those categories up and they account for roughly 240 of the 251 names on the list — more than 95% of this tranche.
There is no merchant-support or customer-service line in the breakdown. The two job families singled out in May as first-in-line are not the job families that actually appear in PayPal’s first WARN filing.
The math against the plan
251 people is 5.3% of the 4,760-person target Bloomberg reported in May. At this rate of disclosure, PayPal has a long way to go before the 20% figure is real — this is one site, one filing, one slice of a multiyear plan with roughly 4,500 more departures still to be named.
What the filing does establish is composition, not pace. A round of cuts that is 95% engineering and management, with zero visible support-staff headcount, is not the shape most 2026 layoff filings take. Retail, telecom, and customer-operations-heavy layoffs — the kind that dominated WARN filings earlier this year — skew toward frontline and support roles because those are the highest-headcount, most automatable categories on paper. PayPal’s San Jose filing runs the other direction: senior individual contributors and middle management took the first hit, not the call-center floor.
What changed between May and September
The gap between the May story and the September filing traces back to how Lores is actually restructuring the company. PayPal collapsed its org chart into three business units — Checkout Solutions, Consumer Financial Services & Venmo, Payment Services & Crypto — each with its own GM. A flatter structure with three GMs needs fewer directors and senior managers sitting between the CEO and the individual contributor layer than the prior matrix organization did. That is a headcount reduction driven by restructuring the reporting lines, not by an AI tool doing the work a director used to do.
The May story and the September filing are not actually in conflict — they are two different cutting mechanisms running inside the same 4,760-person plan. Support and merchant-facing roles get automated away. Directors and senior managers get org-chart-flattened away. Both funnel into the same $1.5 billion target; they arrive by different roads.
The labor read
SFGate has reported that PayPal senior director postings have carried total comp above $300,000. That is the compensation band this WARN filing is cutting into first — not the entry-level or support tier that most AI-displacement coverage assumes goes first.
For engineers and directors at other fintechs running the same “AI transformation” playbook — Lores ran this exact model at HP before PayPal — San Jose’s filing is the leading indicator worth watching: seniority and technical depth are not, on their own, protection from a restructuring-driven cut. The next test is whether PayPal’s remaining ~4,500 departures keep skewing toward management layers, or whether a later filing finally shows the merchant-support and customer-service cuts the May story predicted. Either way, the WARN Act’s 60-day notice window means the next filing is discoverable before it is announced.
