Workday Cut 525 of Its Own. Here Is the Resume Rewrite.

On September 29, 2026, Workday filed an 8-K cutting about 525 jobs, roughly 2.5% of its workforce, concentrated in the Product and Technology team. The stated reason: fund the "agentic AI roadmap." The irony: Workday is the single most-complained-about ATS on r/recruitinghell and Blind, which means the engineers who built it are now about to be screened by instances of their own software deployed at more than 65% of the Fortune 500.

This piece is for them. Here is what the filing actually says, what the market for agentic AI engineers actually looks like, and how to rewrite a Workday Product and Technology resume so it survives both the parser and the shortlist.

What the Sept 29, 2026 8-K actually says

The filing eliminates roughly 525 roles, primarily in Product and Technology, plus some leased office space, and books $65M to $80M in charges against it. CFO Zane Rowe framed the move on the Q2 FY27 call as prioritizing "investment in our agentic AI roadmap and our platform opportunity while driving operational efficiencies as we scale."

A few numbers from the Workday 8-K worth internalizing before you touch your resume:

• $40M to $55M of the charges are future cash severance and benefits.
• About $10M is non-cash stock-based comp.
• About $15M is leased office impairment.
• Q3 FY27 GAAP operating margin is now expected to be 20 to 21 percentage points below non-GAAP.
• Workday headcount still grew 3% in fiscal 2026 despite the February 2025 cut of about 1,750 and the February 2026 cut of about 400.

That last line matters. This is the third Workday layoff in under 20 months, and the first under new CEO Aneel Bhusri, who replaced Carl Eschenbach on February 6, 2026. The two prior cuts were Eschenbach's. Bhusri owns this one, and the filing explicitly notes Workday "plans to continue to hire in key strategic areas and locations throughout its fiscal 2027." Translation: there are internal landing spots on the agentic AI side for a slice of the 525. If you were cut from a product line adjacent to Developer Agent, Agent Passport, or Workday Data Cloud, the first conversation to have is an internal transfer, not an external one.

Why "agentic AI" is a scarcity keyword, not a buzzword

"Agentic AI" sounds like LinkedIn filler, but in the hiring market it is the opposite: a genuinely scarce specialty where the people claiming it credibly are a tiny slice of the broader AI engineer pool. If you shipped Workday's organic agents, you are not a generalist competing with 15,000 ML engineers. You are a specialist competing with roughly 239.

Here is the shape of the market, pulled from Refolk's index of professional profiles alongside the Sept 29 disclosure.

Read the 2.2:1 line twice. The single Sept 29 cut is more than double the entire US senior pool of credible agentic AI engineers. If even a quarter of the 525 reposition correctly, they measurably move the national supply. If you reposition correctly, you are inside the top 2% nationally on the one keyword every HR tech buyer is chasing.

The mechanism is simple. Workday told the market that "AI driving more than 25% of our new ACV" (Bhusri) and that "more than 5,500 customers now use one or more of Workday's organic agents, up more than 35% from the previous quarter." Every Workday competitor now has to answer those numbers on their own earnings calls. The buyers of your next job are reading the same filing you are.

What "repositioning correctly" means on paper

Three concrete moves:

1. Replace "AI/ML" with specific agent primitives you actually touched: Agent Passport, Developer Agent, Workday Data Cloud, the AWS partnership integration surface.
2. Quantify the agent surface, not the model. "Shipped tool-use orchestration across 14 internal domains, cutting manual HR task time 38%" beats "Built LLM features."
3. Name the eval. Agentic hiring managers in 2026 want to see trajectory evals, tool-selection accuracy, and rollback behavior. If you ran any of these, say so.

The Workday parser will mangle a Workday engineer's resume

The dominant complaint about Workday as an ATS, repeated across Blind threads titled "workday is the worst ats application as a candidate" and across r/recruitinghell, is that its parser splits sub-bullets into new "companies," wipes formatting, and forces manual re-entry despite the resume upload. If you worked on it, you know the parsing path better than the recruiters using it. Here is what that means for your document.

Keep every company and title line strictly linear. One company, one title block, one date range, left-aligned, no columns. No tables. No two-column layouts. No icons. No nested project bullets under role headers. If you have a project you want to feature, make it its own role-shaped entry with a company field (your employer at the time) and a title that reads like a title ("Tech Lead, Developer Agent"), not a project name ("Project Phoenix").

A short list of specific formatting mistakes that break Workday-style parsers:

• Side-by-side columns for skills and experience. The parser reads top-to-bottom and interleaves them.
• Role headers with a company name on the same line as a project. The parser treats the project as the company.
• Bullets that begin with a date. The parser pulls the date into the employment range field.
• Headers inside text boxes or SVGs. They vanish entirely.
• Non-breaking spaces inside company names. They occasionally split "Workday Inc." into "Workday" and "Inc."

The fix is boring and effective: single-column, standard section headings (Experience, Education, Skills), each role as Company / Title / Dates / 3 to 6 bullets, PDF exported from a text source rather than a design tool. If you want a sanity check, run your current PDF through a public resume parser and see where it puts "Developer Agent."

This is also the exact friction Refolk takes off a laid-off engineer: paste the posting, get a resume back rewritten against it with the agentic keywords lifted from your real history rather than guessed at, and formatted so the Workday parser does not split a bullet into a new employer. For 525 people on the same timeline, hand-tailoring every application is not a plan.

Where the displaced actually sit, and where to look

Workday's cut is not a Pleasanton story. In Refolk's index, the top regions for engineers and PMs with "Workday" in their headline are Bengaluru, Dublin, San Francisco, and Hyderabad. The top current employers after Workday itself (11 profiles) are Workday Strategic Sourcing, Tech Mahindra, Lowe's India, Walmart Global Tech, Paychex, Hexaware, and AUTODOC. That tells you three things.

• Dublin cuts carry EU statutory severance timelines and collective-consultation obligations that Pleasanton cuts do not. Your runway is longer; your rehire window is also later because EU employers plan around the same calendar.
• Bengaluru and Hyderabad have a dense secondary market in HR tech services firms (Tech Mahindra, Hexaware, Capgemini) that absorb Workday-platform specialists for implementation work. That is a different resume than the agentic AI pivot, oriented around certifications and integration counts.
• The US cohort should look sideways at ServiceNow, Salesforce (Agentforce teams, which cut more than 1,000 in 2025 and are now rebuilding), Oracle, and SAP SuccessFactors, plus agent-native startups building on top of Workday's Data Cloud and partner APIs.

If you built on the Workday / AWS integration surface, Amazon's internal HR tech teams are a natural landing. If you worked on recruiting-side agents specifically, Greenhouse, Lever, and SmartRecruiters are the ATS platforms candidates on Blind actually prefer, and they are all investing in agent features to catch up.

The resume rewrite, section by section

Rewrite in this order: headline, summary, most recent role, skills, older roles. The first three carry the shortlist decision; the rest carry the interview.

Headline

One line. Format: "Senior Software Engineer, Agentic AI Platforms (ex-Workday Developer Agent)." The parenthetical is the point. The 2026 market reads "ex-Workday" as a credential on agent work the way "ex-Stripe" reads on payments. Do not bury it.

Summary

Three sentences, zero adjectives. Sentence one: what you built, with the agent primitive named. Sentence two: scale, as a number. Sentence three: the eval you ran. Example shape: "Tech lead on Workday's Developer Agent surface, shipping tool-use orchestration across 14 HR domains. Deployed to a share of the 5,500+ customers on Workday's organic agents. Owned trajectory evals and rollback behavior for 7 production tools."

Most recent role

Six bullets, each starting with a verb, each with a number, each naming a specific agent primitive or system. If you have a bullet that reads "Collaborated with cross-functional stakeholders," delete it. You will not get it back and you will not miss it.

Skills

Group into three buckets: Agent systems (Agent Passport, Developer Agent, tool-use orchestration, trajectory eval), Platform (Workday Data Cloud, AWS, Kafka, whatever you actually used), Languages. No "soft skills" section. No proficiency bars.

Older roles

Compress. Two to three bullets each, numbers where you have them, no project narratives. The reviewer has already decided by the time they get here; the goal is not to lose the shortlist on an irrelevant 2017 bullet.

The internal-transfer play most pieces skip

The 8-K says Workday "plans to continue to hire in key strategic areas and locations throughout its fiscal 2027." That is boilerplate, but it is also actionable. If your manager's org survived, the agentic AI roadmap teams are the strategic areas, and the window to pitch an internal move is the severance notice period, not after.

Three concrete steps:

1. In the 72 hours after your notice, email your skip-level and the hiring manager on the agent team you want. Attach a one-page memo (not a resume) titled "Agent primitives I can own in Q4 FY27." Name three.
2. Ask HR specifically about the internal mobility policy during the severance window. Workday's own policy varies by region; Dublin and India have different rules than Pleasanton.
3. Keep your external search running in parallel at the same intensity. Treat the internal path as a long shot; your external resume still has to win.

The HR tech engineer job search in late 2026 is unusually bifurcated: a tiny senior agentic pool (239 people) and a huge generalist pool (15,252). You want to be filed in the small bucket. Everything above is in service of that one filing decision.

FAQ

Does "ex-Workday" help or hurt on a 2026 resume?

It helps, if you pair it with a specific agent primitive. Workday is still the dominant HR cloud at more than 65% of the Fortune 500, and the agentic AI buyer at a competitor wants to hire the people who built the thing their CEO just asked them to catch up to. "Ex-Workday" on its own reads as generic enterprise SaaS. "Ex-Workday, Developer Agent" reads as a credential.

Should I apply through Workday ATS instances or go around them?

Apply through them, but also route around them. For every Workday-hosted posting at a target company, find the hiring manager on LinkedIn and send a two-sentence note with your resume attached. The Workday parser will mangle sub-bullets regardless of how clean your PDF is, and a direct message gets a human read before the parsed version lands in the queue.

How many applications is realistic for the Sept 29 cohort?

Enough to generate real conversations, which in practice means a steady stream of tailored applications over 10 to 14 weeks rather than a one-week blast. The constraint is not volume, it is tailoring. Generic applications at this volume get filtered out by the same agentic screening Workday is building. Tools like Refolk that write a per-posting resume and cover letter from your real history exist specifically because this math stopped working by hand.

Is the agentic AI engineer resume different from a standard ML resume?

Yes, materially. ML resumes emphasize models, datasets, and offline metrics. Agentic AI engineer resumes emphasize tool-use orchestration, trajectory evals, rollback behavior, and production agent surface area (how many tools, how many domains, how many customers). If your resume reads like a 2022 ML resume, you will lose to the 239 people whose resumes read like 2026 agent resumes, even if your underlying work is stronger.