Hands-on Workday integrations architect role.Studio and Orchestrations are core, Extend is a plus.
Responsibilities center on owning the end-to-end integration pipeline using Studio, Orchestrations, Core Connectors, EIB, RaaS, and APIs. Extend is listed in duties as well, though marked as a plus in qualifications alongside broad functional module fluency. Best suited for a deep technical integrations builder.
Skills, by how much you'll use them
From Turbin's read of the posting
5 skills
Every day
The core of the job. Lead with these.
Integrations
Studio
Orchestrations
Core Connectors
EIB
5 skills
Working knowledge
Expected, but not what you are hired for.
Extend
Calculated fields
RaaS
XML and XSLT
JSON and SQL
4 skills
Only mentioned
Named in the posting. Safe to skip.
Core HCM
Payroll
Benefits
Security
What you'll do
7 responsibilities
Own the end-to-end Workday integration pipeline from design and configuration to deployment and production support
Build and maintain integrations with internal and external platforms using Studio, Orchestrations, Core Connectors, EIB, RaaS, and REST or SOAP APIs
Ensure data integrity across inbound and outbound integrations through rigorous mapping, transformation, and validation processes
Govern the integration lifecycle including code migrations, production hypercare, release impact analysis, and regression testing
Do you fit?
Tick what you have. Only you see this.
0 of 5 must-havesTick what you have to see your match.
Must have · 5
Nice to have
Experience with Workday Extend
Working familiarity with agentic AI or LLMs such as Claude
How to pitch yourself
Turbin's advice
Lead with your production integration architecture across Studio, Orchestrations, Core Connectors, and EIB, plus your ability to debug API and transformation layers. Highlight Extend or calculated fields only if you have real build experience.
1Show scale and ownership for core integrations by noting transaction volume, error handling, and downstream systems like Greenhouse or HireVue
2Include concrete Studio and Orchestrations examples, detailing XML, XSLT, JSON, or x509 and PGP encryption work you delivered in production
3Demonstrate release governance and cross-module awareness, showing how you test integration impacts across HCM, Payroll, or Benefits changes
4Mention Workday Extend or AI tooling briefly only if you have hands-on exposure, since they are listed as bonuses rather than hard gates