Hands-on Workday integrations build role.Strong integration coding beats prior Workday years.
Duties center on designing, building, and testing Workday Studio and EIB integrations across HCM and financials. Requirements accept SAP, Oracle, or PeopleSoft integration backgrounds alongside XML, XSLT, Web Services, and middleware. This fits a technical integration developer.
Skills, by how much you'll use them
From Turbin's read of the posting5 skills
Every dayThe core of the job. Lead with these.
- Integrations
- Studio
- EIB
- Web Services
- XML and XSLT
5 skills
Working knowledgeExpected, but not what you are hired for.
- EDI
- Middleware
- Java and .NET
- HCM
- Financials
2 skills
Only mentionedNamed in the posting. Safe to skip.
What you'll do
5 responsibilities- Comprehend point-to-point data integrations and interchange services to ensure data quality and reliable digital exchanges
- Identify, assess, and solve business problems when integrating Workday with external systems across HCM and financial areas
- Design, build, and support testing of Workday integration code including Studio, EIB, and supporting third-party code
- Follow strategic direction from client leadership when establishing Workday project goals
- Identify and escalate risks in a timely manner while developing alternative technical and functional approaches
Do you fit?
Tick what you have. Only you see this.- Designer and developer experience delivering coded integration work to a production environment
- Self-starter able to work creatively and analytically in a fast-paced, team-oriented environment
- Experience with Excel, Visio, and PowerPoint
- Proven communication effectiveness with project leadership
- Bachelor's degree, with a technical degree strongly preferred
How to pitch yourself
Turbin's adviceLead with hands-on integration builds in XML, XSLT, Web Services, or Workday Studio and EIB, showing you can deliver coded integrations into production. Even if your HRIS integration background is in SAP, Oracle, or PeopleSoft, highlight end-to-end delivery and testing.
- 1Detail specific integration builds, naming tools like Workday Studio, EIB, XML, XSLT, or Web Services and the business systems connected
- 2Include production delivery outcomes, such as "Delivered 6 outbound payroll and benefits integrations from design through production cutover"
- 3Show how you translated functional requirements across HCM or financial processes into technical integration designs and resolved data issues
- 4Mention middleware, Java, .NET, or EDI briefly if you have used them in point-to-point or enterprise integration work