Skip to content
KiweelyKiweelyKiweely

Workday Agent Factory FDE Playbook from Public Careers Pages

Workday’s FDE careers pages place the org across Agent Factory, Sana, Data Cloud/Products, and the Developer Platform—with live-tenant deploy, product feedback, and 6-month graduation milestones.

  • By Kiweely
  • 2 min read
On this page

Workday does not publish a standalone “Agent Factory” product guide on www.workday.com or blog.workday.com as of this check. What it does publish—on current Forward Deployed Engineer careers pages—is how the FDE organization works when agents ship: pods sit across Agent Factory, Sana, Products/Data Cloud, and the Developer Platform, go into live tenants early, and feed friction back into product.

This playbook stays inside that public careers language (JR-0111511 and JR-0111465, fetched 2026-11-18). It is not a private SOW, and it does not invent Agent Factory APIs.

Where Agent Factory sits in the FDE map

Posting Org wording
PostingJR-0111511 Org wordingFDE org across Agent Factory, Sana, Products, and the Developer Platform
PostingJR-0111465 Org wordingFDE org across Agent Factory, Sana, Data Cloud, and the Developer Platform; Developer Platform team focuses on custom agents on Workday rails

When Workday launches new AI agents and platform capabilities, both postings say early deployments surface unstructured tenant data, intricate configurations, and edge-case workflows. That is the Agent Factory-adjacent field problem FDEs are hired to absorb.

Playbook steps Workday names on the postings

  1. Deploy into active engagements. FDE pods “deploy directly into active customer engagements to resolve technical friction, debug complex setups, and build lightweight integrations” (JR-0111511). Developer Platform FDEs build, configure, test, and debug custom agents inside live tenants against live data, business processes, and security (JR-0111465).
  2. Stay beside Services and architects. Both roles collaborate with AI Deployment Architects, Product Managers, and Workday Services leads. JR-0111465 is explicit: Workday Services owns the customer project; FDEs own defined technical workstreams.
  3. Run a 6-month milestone arc. Structured milestones from kickoff to graduation, enabling self-sustaining customer ownership within standard 6-month deployment cycles.
  4. Operate the product feedback loop. FDEs are the “primary” / “critical” feedback engine for Product and Engineering—field insights and recurring friction become scalable, out-of-the-box capabilities (and, on Developer Platform, toolkit improvements for Developer Agent, Agent-Ready Tools, and the Agent Harness).
  5. Productize, don’t permanently customize. Identify recurring deployment challenges and turn custom fixes into standardized capabilities, reference architectures, playbooks, and pattern guidance “that let customers and partners build without us” (JR-0111465).

Developer Platform cut of the same playbook

If the engagement is custom-agent heavy, JR-0111465 adds the stack Workday expects FDEs to use in the field: Agent Harness, Developer Agent, Agent-Ready Tools, open standards including A2A, plus governance through Extend AI, Agent System of Record, Agent Passport, and Data Cloud. Surfaces named on that posting: Workday, Sana, or the AI tools people already use.

What this playbook refuses to invent

  • No Agent Factory release train, SKU list, or admin task sequence—those are not on the careers pages or a public Agent Factory product page.
  • No partner firm rate card or SOW economics—the postings talk about collaborating with Services and productizing for “customers and partners,” not about buying partner days.
  • No claim that every FDE is an Agent Factory engineer; Agent Factory is one named surface of the FDE organization.

Use this as a staffing and operating checklist aligned to Workday’s own job text. For tenant registration gates, pair with the first-party agent prerequisites guide; for Services vs FDE ownership language, see the partner-vs-services note grounded in the same postings.

Your Workday work, done by AI.

Kiweely Vine is the AI agent that builds, deploys and tests Extend apps as real people, makes changes in any Workday task screen, answers from your real tenant and builds reports.

Get the next one in your inbox.

One email a month for Workday teams: what’s changing in Workday and what to retest, one tip tried in a real tenant, and what’s new at Kiweely.

We’ll email you once to confirm. Unsubscribe in one click from any issue.