If your resume still opens with tickets per day, it describes the exact work Block just said it no longer needs people for. On November 4, 2026, Block told staff in Customer Operations, Risk Operations, and Learning & Content Operations that their roles were being eliminated. Its reasons were "using better tools to handle routine tasks" and "refocusing our teams' time on complex cases and decisions." The news came one day after Block reported Q3 gross profit up 22% to $3.24 billion. Hiring managers have read that explanation too, and they will screen for judgment. Write every bullet for the second job, not the first.
What happened in the Block layoffs in November 2026?
Block started its second layoff round of 2026 on November 4. The cuts hit Customer Ops, Risk Ops, and Learning & Content Ops at Cash App and Square, and the company said better tools now handle routine tasks. Business Insider broke the story from an internal message it reviewed.
The details matter if you're one of the people affected:
- Scope. The email described "reducing the number of roles, changing some responsibilities, and shifting some reporting lines."
- Stated reason. "Using better tools to handle routine tasks" and "refocusing our teams' time on complex cases and decisions."
- Financial backdrop. Q3 gross profit came in at $3.24 billion, up 22%. Cash App rose 27% to $2.07 billion and Square rose 14% to $1.16 billion. Block also raised its gross profit guidance to $12.626 billion, up 22% year over year.
- Exit terms. Some people leave with separation packages. Others face a formal consultation process. That does not mean a move into consulting jobs.
- Severance. At least seven weeks of base pay plus a week per year of tenure, with three months of COBRA. In February the offer was 20 weeks plus a week per year, with six months of COBRA.
The history makes this round harder to take. In February Block went from more than 10,000 workers to fewer than 6,000, and Jack Dorsey said he wanted one big cut instead of a series of smaller ones. He also said AI would sit at the center of "how we build trust and manage risk, how we build products and how we serve customers." So the risk and customer functions were already named back in February.
Not everyone buys the AI explanation. Mizuho analyst Dan Dolev said "the vast majority of these cuts were probably not due to AI." The wider labor data is mixed too. October's jobs report showed financial activities up 7,000 and information down 1,000, and no major industry posted a significant loss. The longer trend is the one to watch: financial activities has shed 129,000 jobs since May 2025.
Where should laid-off Block ops workers look next?
Look at risk first, because it's the bigger door. In Refolk's index of professional profiles, US financial services has about 3.3 times as many people with risk and fraud analyst titles as with customer ops titles, and they are spread across more employers. Trust & Safety is a different market, and outsourcers handle most of its volume.
| Segment (US) | Profiles in Refolk's index | Sample signal (25 profiles) |
|---|---|---|
| Risk / fraud analyst titles, financial services | 4,766 | 68% (17/25) hold analyst titles |
| Customer ops / support titles, financial services | 1,452 | 48% (12/25) at JPMorganChase |
| Trust & Safety / Content Moderator, all industries | about 1,000+ | 40% (10/25) at Cognizant, Accenture, or Wipro |
| Escalations Specialist share, customer ops sample | n/a | 4% (1/25) |
The percentages come from 25-profile samples, so treat them as directional rather than precise. The counts measure people holding those titles, not open postings.
From Refolk's index, about 3.3x the customer ops pool in the same industry.
The two pools look different up close. In the risk sample, the most common titles were Risk Analyst (10), Fraud Analyst (5), and Risk Operations Analyst (2), at employers such as PwC, Tradeweb, BNY, and BNP Paribas. The customer ops sample was concentrated: JPMorganChase alone held 12 of 25 profiles, and Brex, Ramp, Bluevine, and AtoB showed up once each.
That should shape your strategy. If you worked support at Cash App but made account-restriction or dispute decisions, you can honestly retarget toward Risk Analyst postings. That market has more employers and depends less on one bank's hiring cycle. The reframe only works if it rests on decisions you really made, so the bullets below do the heavy lifting.
How do you write a customer operations resume after a layoff?
Lead with the escalations you owned, not the queue you cleared. Escalation work rarely shows up in a job title: only 1 of 25 sampled financial-services customer ops profiles in Refolk's index carried an Escalations Specialist title. Your bullets have to show the work your title hides.
That gap is why so many strong ops people undersell themselves. The judgment work happened under a title like "Customer Support Specialist," so the resume shows a generic title and generic volume. "Handled 80 tickets a day" tells a reader how much work came in and how fast your tooling let you close it. It doesn't say what you did when a case didn't match the macro, and a recruiter screening for "complex cases" sees nothing to stop on.
Tickets per day measures the queue. The hiring manager wants to know what you decided when the queue got weird.
Rebuild each role in four steps:
- List the decisions you could make that a new agent couldn't. Refunds above a limit, account unlocks, dispute rulings, identity overrides.
- Name the policy or playbook behind them. "Under the P2P dispute policy" is more specific than "resolved disputes."
- Name the outcome. Money recovered, repeat contacts avoided, cases routed correctly the first time, a policy changed because of your flag.
- Keep one volume line at most, as context. Volume shows the scale you worked at. It shouldn't be the achievement.
Before and after, with placeholders for your own figures:
- Before: "Resolved 80+ customer tickets daily with [X]% CSAT."
- After: "Owned tier-2 escalations for disputed P2P payments. Ruled on [N] cases a month where the policy was ambiguous, and flagged a recurring pattern that led to a revised refund rule."
- Before: "Handled account access requests."
- After: "Made account-restriction and reinstatement calls on [N] high-risk cases a week, documenting rationale used to train [N] new agents."
Digging these out of years of tickets is the slow part. It's also the exact work Refolk takes off you: it writes the resume from your own history, pulls the decisions to the top, and rewrites it for each posting so a Risk Analyst application and a Customer Operations application lead with different proof.
What do strong fraud analyst resume bullets look like?
Strong fraud analyst bullets tie each decision to dollars of loss avoided. Transaction losses are a line item companies account for, so a bullet in that currency reads like P&L work. Block's own 10-Q showed $59,051 thousand in accrued transaction losses as of March 31, 2026, primarily related to Cash App transactions such as peer-to-peer payments, overdrafts, and negative balances.
That number is why loss prevented counts as finance work and throughput doesn't. A risk leader reports losses upward. If your bullet says what you did to that number, you're speaking their language before the interview starts.
A risk operations resume should cover three things:
- The decision. What you approved, blocked, held, or escalated.
- The mechanism. The rule, model threshold, or pattern you used or built.
- The dollars or the rate. Loss avoided, chargebacks reduced, false positives cut so good customers stopped getting locked out.
Examples:
- "Identified a negative-balance abuse pattern across linked accounts. Wrote the detection rule now used by the team, preventing an estimated $[X] in losses over [N] months."
- "Tuned review thresholds for overdraft risk, cutting false-positive holds by [X]% without raising loss rate."
- "Led manual review for [N] high-value P2P disputes a month, with a reversal rate of [X]% on audit."
If you don't have exact loss figures, don't make them up. Use what you can defend: the number of cases, the share that held up on audit, or the policy that changed. An interviewer will push on any dollar figure, and a smaller number you can defend beats an impressive one you can't explain.
What should trust and safety resume examples emphasize?
Trust and safety bullets should center on policy, vendor calibration, and edge cases. In Refolk's sample, 40% of T&S profiles sit at outsourcers (Cognizant, Accenture, or Wipro), so the queue work has largely moved to vendors already. In-house teams pay vendors for speed. They hire staff for judgment.
Smaller employers such as TrustLab and Tools for Humanity also showed up in the sample. Whatever the size of the team, the in-house seat is the one that decides what the rules should be, not just the one that enforces them fast.
Good T&S bullets:
- "Drafted the escalation policy for [content type], adopted by [N] vendor reviewers."
- "Ran weekly calibration sessions with outsourced moderators, raising decision agreement with in-house reviewers from [X]% to [X]%."
- "Ruled on edge cases the policy didn't cover and wrote them up as precedent for the vendor playbook."
Learning & Content Operations, the third team Block cut, works the same way. "Wrote [N] knowledge base articles" is volume. "Rebuilt dispute-handling training after an audit found inconsistent rulings, and tracked accuracy on the next audit" is a workflow you designed, with an outcome. Training that changes how other people make decisions is judgment work too.
How should the shorter severance change your search?
Plan for much less runway than February's cohort had. This round pays at least seven weeks of base pay plus a week per year, against 20 weeks plus a week per year in February, and health coverage dropped from six months of COBRA to three.
Both rounds add one week per year of tenure on top.
Less runway makes a slow, generic search more expensive. Sending one resume to every ops, risk, and support posting and then waiting feels productive, but each week of silence comes out of a shorter cushion. Check fit before you apply. A Cash App support agent applying to Risk Analyst roles at BNY and to Customer Operations roles at Ramp needs two different resumes. Some of those postings will be a reach worth taking and some won't.
If you're still at Block, or at a fintech that sounds the way Block did in February, you face a different version of the same problem. Dorsey said he wanted one big cut and a second came anyway, and you can't search openly while you're still employed.
FAQ
Should I mention the Block layoff on my resume?
No. Put the end date on the role and leave the reason off. If a cover letter or recruiter screen asks, one sentence is enough: your team was part of Block's November 2026 reduction in Customer, Risk, or Learning & Content Operations. Block's stated reason was tools handling routine work, so follow that sentence by naming the non-routine work you did. That turns the layoff into a lead-in for your best bullet.
Can a customer support agent credibly apply for fraud analyst roles?
Yes, if you made risk decisions and your resume shows them. Account restrictions, dispute rulings, identity checks, and pattern flags are fraud work done under a support title. Refolk's index shows the US financial-services risk and fraud pool at 4,766 profiles against 1,452 for customer ops, so the door is bigger. Lead with the decisions, name the policy, and cut the ticket counts down to one supporting line.
What if I don't have dollar figures for loss prevented?
Use the numbers you can defend: cases reviewed, the share that held up on audit, false positives reduced, or a policy that changed because of your work. Rough estimates are fine if you can explain how you got them. Never invent a loss figure. A risk interviewer will ask how you calculated it, and a vague answer costs more than a modest number.
Was AI really the reason for Block's ops cuts?
Block said so, citing "better tools to handle routine tasks." Mizuho's Dan Dolev was skeptical, saying the vast majority of the cuts were probably not due to AI. For your resume it doesn't matter who's right. Hiring managers have read Block's explanation, and they'll screen ops candidates for the "complex cases and decisions" half of the job. Write your bullets for that half.