Block's 4,000-Cut Résumé: From "Managed 8" to "$2M Per Head"

On February 26, 2026, Block cut roughly 4,000 people (about 40% of staff) and the market rewarded it with a same-day after-hours pop of up to 27%. Jack Dorsey's letter to shareholders reframed the layoff as a productivity thesis, not a cost cut. If you are writing a résumé this quarter, that letter is now the mental model on the other side of the desk.

Why every CEO in America is quoting Dorsey this week

Dorsey's line, "intelligence tools have changed what it means to build and run a company," landed because the numbers backed it. Block's Q4 gross profit grew 24% year over year and management raised its 2026 gross-profit guidance to $12.2 billion, all while headcount dropped from over 10,000 to under 6,000 in a single day.

Coverage keeps conflating two different 24-and-up figures. Get them straight before you write a bullet:

• 24%: Q4 gross-profit growth, year over year.
• 22 to 27%: the after-hours stock move on the same day.
• 40%: the workforce cut (~4,000 of ~10,000).

The reason this matters for your résumé: Dorsey was rewarded for a ratio, output divided by headcount, not for firing people. Marc Benioff echoed the same logic days later, saying Salesforce "needs less heads" after reducing customer support by 4,000. Amazon, Meta, Microsoft, and Verizon have all made adjacent AI-tangential cuts in the last year. The CEO reading your résumé this week is scanning for one thing: proof you already run at the new ratio.

The résumé lesson buried in the ratio

Rewrite every "managed a team of X" line into "shipped Y with a team of X." The ratio is the story, and the ratio is what a Dorsey-style reader circles first.

Old bullets read like org-chart evidence. New bullets read like P&L evidence. When middle management is the layer being deleted, "coordinated across six teams" stops sounding like leverage and starts sounding like the exact overhead that got cut. Dorsey's internal reorg makes this literal. Block employees are being sorted into three roles:

1. Individual contributors, who build and maintain systems and products.
2. Directly responsible individuals (DRIs), who own specific problems and lead projects end to end.
3. Player-coaches, who mentor teams while still shipping technical or product work.

Notice what is missing. There is no "manager of managers." No "director of program coordination." If your current title is one of those, your résumé needs to translate you into one of the three roles above before it gets read as headcount to trim.

Three rewrites that mirror the new org

Refolk writes your résumé from your own history and tailors it to every posting, which is where this rewrite actually happens at scale: paste the JD, get bullets restructured around DRI and player-coach language when the company uses it, and left alone when they do not. Refolk does this per application, not once.

Show leverage, do not just claim it

Leverage on a résumé is a fraction with a numerator (what shipped) and a denominator (team size, time, or budget). If you write only the numerator, you sound like everyone else.

The pattern to copy from Block's own framing: "A significantly smaller team, using the tools we're building, can do more and do it better." Every strong bullet on an AI-era résumé has that same shape.

• Numerator: the shipped thing, in units the business cares about (revenue, latency, cycle time, error rate, tickets closed).
• Denominator: people, weeks, or dollars.
• Tool attribution: the specific model or product that made the ratio possible.
• Date: quarter and year, so the reader knows which model generation you were using.

Worked example. Weak: "Improved sprint velocity using AI tools." Strong: "Q1 2026, cut spec-to-PR cycle from 10 days to 4 on the billing team of 3, using Claude Code and Codex 5.3 for scaffolding and test generation."

The date is not decoration. Dorsey and Block's leadership tipped into the 40% cut after the holiday 2025 window, when they sat with Anthropic's Opus 4.6 and OpenAI's Codex 5.3 and realized the model generation had jumped. Résumés that still cite GPT-4 wins from 2023 read as stale. Timestamp your AI bullets to the model that was current when you shipped.

The 2.44x tool-literacy trap

Listing "LangChain, Cursor, Claude Code" in a skills bar is now table stakes and will not differentiate you. In Refolk's index of US professionals, 18,227 list LangChain as a skill, versus 7,466 whose current title contains "AI Engineer" or "Forward Deployed Engineer." Tool literacy is roughly 2.44x broader than the job title.

Recruiters and hiring managers have caught on that a skills-bar mention costs the candidate nothing. So the signal has moved to output attributable to those tools. Two candidates with identical skills bars are separated by which one wrote:

• "Moved the eval harness from manual spot-checks to a 240-case regression suite in LangSmith; caught 3 prompt regressions before shipping."
• "Built a Claude Code workflow that took our on-call runbook execution from 45 minutes to 6."

Neither bullet is generic. Both name the tool, the before, the after, and the surface area. That is what a hiring manager at Distyl, Modal, Amp, Gecko Robotics, or Northslope Technologies (all actively hiring the forward-deployed archetype) is scanning for. Refolk scores how well you fit each specific posting against the skills and outcomes it actually asks for, which is useful when the tool bar looks identical to 18,000 other people's.

Middle managers: the "anti-signal" audit

If your last three bullets contain the words "coordinated," "aligned," "facilitated," or "drove alignment," you are describing exactly the work Dorsey said AI now handles.

Block's public position is that traditional middle management roles focused on reporting, coordination and status updates would largely disappear, with AI systems handling alignment and information flow. Roelof Botha co-authored Dorsey's "From Hierarchy to Intelligence" essay reinforcing the point: circle, not pyramid.

Do an anti-signal pass on your current résumé. For every bullet:

1. Underline any word from the list: coordinated, aligned, facilitated, oversaw, championed, drove alignment, ran cadence, managed stakeholders.
2. Ask what shipped because of that verb. If nothing shipped, cut the bullet.
3. If something shipped, rewrite the bullet with the shipped thing as the subject and yourself as the DRI.

Example. Underlined: "Coordinated 4 engineering teams to align on Q2 roadmap." Rewritten: "DRI for the Q2 payments roadmap; personally scoped and shipped the 3 revenue-tagged milestones on schedule with a working group of 6." Same underlying work. Completely different signal.

The counter-trade: Forrester says half of this reverses

A January 2026 Forrester report predicted that over half of AI-attributed layoffs will be quietly reversed as companies hit the operational reality of replacing human talent prematurely. That is not a reason to ignore the Dorsey playbook. It is a reason to write for the rebound.

The candidates who will get pulled back first are the ones whose résumés prove they can operate an AI stack in production, not just prompt one. Concretely, add bullets that show:

• Evals: "Built a 180-case eval set for the customer-support agent; blocked 2 releases with regression above threshold."
• Rollback: "Shipped a canary + rollback flow for LLM prompt changes; mean recovery time under 4 minutes."
• Human-in-the-loop: "Designed the reviewer queue for high-risk refunds; kept auto-approve rate at 68% with sub-1% false-approve."
• Cost: "Cut inference spend 41% by routing 70% of traffic to a distilled model with matched eval scores."

These bullets are boring on purpose. They are what a hiring manager, six months into an over-aggressive AI cut, will be desperately searching for. This is also the kind of tailoring that is tedious to do 40 times by hand across 40 postings, which is why Refolk drafts each application against the specific JD (including the cover letter) instead of asking you to run the same rewrite manually.

A 45-minute rewrite pass, in order

Do this once end-to-end before you send the next application. It is faster than it sounds and it compounds across every posting after.

1. Delete the summary paragraph unless it contains a number. "Results-driven leader" is filler; "Ran a payments team of 4 shipping at $2M gross profit per head" is not.
2. Rewrite the top three bullets of your most recent role using the numerator/denominator/tool/date pattern.
3. Do the anti-signal underline pass on every remaining bullet. Cut or rewrite.
4. Add a "How I work with AI" line under your most recent role. Two sentences. Name the models (Claude Code, Codex 5.3, Opus 4.6), name the surfaces (spec-to-PR, evals, on-call), name a ratio.
5. Rebuild the skills bar with three tiers: models, orchestration (LangChain, LangSmith, evals), and delivery (Cursor, Claude Code). Skip anything you cannot defend in a 10-minute conversation.
6. Timestamp two AI wins in the last 12 months by quarter and model version.

If you are targeting the specific companies hiring the forward-deployed IC archetype (Distyl, Modal, Amp, Gecko Robotics, Northslope), the ratio bullets are what get the reply. The generic skills bar is what gets ignored.

FAQ

Should I mention Claude Code and Codex by name on my résumé?

Yes, and by version when you can. Dorsey publicly credited Anthropic's Opus 4.6 and OpenAI's Codex 5.3 as the models that tipped Block's decision at the end of 2025. Naming the specific model generation you used, with a date, signals that your win is current. A bullet that reads "Q1 2026, Codex 5.3" ages better than "AI-powered coding assistant."

I am a middle manager. Is my résumé cooked?

No, but the framing has to change. Block's own reorg keeps player-coaches, who mentor while still shipping technical or product work. Rewrite your bullets around what you personally shipped, not what you coordinated. If you have not shipped anything in 18 months, spend the next quarter as a DRI on one visible project before you apply. That single bullet is worth more than a decade of "led cross-functional initiatives."

Is the "AI layoffs" wave real or is Forrester right that it will reverse?

Both are true and it matters for your résumé. Forrester predicts over half of AI-attributed layoffs will be quietly reversed as operational reality hits. Write for the initial cut (ratio bullets, DRI language) and for the rebound (evals, rollback, human-in-the-loop, cost). Candidates who can prove they operate the stack, not just prompt it, are the ones who get called back first.

How do I tailor this résumé for 40 different postings without going insane?

You do not do it by hand. The rewrite framework in this article is the substrate; the per-posting tailoring (which bullets to lead with, which tools to foreground, which DRI vs player-coach language to use) is what Refolk automates. Paste the posting, get your own history rewritten for it, get the cover letter drafted, and see a fit score before you send. That last part matters most when you are applying into a market where the CEO on the other end just watched Block get rewarded 27% for cutting 40%.