!Good to know. Expectation to work in the Fort Wayne or Indianapolis office at least two days per week. Does not qualify for relocation assistance. Must be authorized to work in the U.S. without employment-based visa sponsorship now or in the future.
Overview
Turbin's analysis on the role ·
Hands-on Workday integrations engineering role.Studio and API builds are the job, not functional config.
Responsibilities and requirements both center on building integrations with Workday Studio, EIB, and REST or SOAP APIs to connect Workday with an internal .NET and Azure stack. Workday Extend appears in duties without a matching requirement, while middleware and Azure tools are preferred extras.
Skills, by how much you'll use them
From Turbin's read of the posting
4 skills
Every day
The core of the job. Lead with these.
Integrations
Workday Studio
REST and SOAP APIs
EIB
4 skills
Working knowledge
Expected, but not what you are hired for.
Workday Extend
Core Connectors
OAuth 2.0
JSON and XML
3 skills
Only mentioned
Named in the posting. Safe to skip.
Security model
Release cycle
Middleware
What you'll do
8 responsibilities
Design, build, and maintain Workday integrations using Workday Studio, EIB, SOAP/REST APIs, and Workday Extend
Architect event-driven, batch, and real-time integration patterns between Workday and .NET, PostgreSQL, and Azure systems
Develop and own integration documentation including data flow diagrams, API contracts, and Architecture Decision Records
Evaluate and recommend middleware and iPaaS tooling such as Azure Integration Services or MuleSoft
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 integrating Workday with .NET or Azure-based systems
Familiarity with iPaaS or middleware platforms such as Azure Logic Apps, Azure Service Bus, MuleSoft, or Boomi
Exposure to Docker, Azure Container Apps, CI/CD pipelines, Git/GitLab, and observability tooling
Workday Pro certification in Integration, Studio, or a related track
How to pitch yourself
Turbin's advice
Lead with end-to-end integrations you have built using Workday Studio, EIB, and REST or SOAP APIs. Mention any Workday Extend, middleware, or Azure integration experience briefly if you have it, since those are secondary or preferred.
1Show scope and architecture for your Workday Studio and EIB builds, such as 'Built Studio integrations syncing employee and finance data via REST APIs with custom error handling'
2Highlight software engineering practices the team values, including API contracts, JSON and XML payloads, OAuth 2.0 authentication, and CI/CD or version control workflows
3Include documentation and cross-team delivery examples such as data flow diagrams, Architecture Decision Records, or partnering with application developers
4Mention Workday Extend, Azure Logic Apps, MuleSoft, or Workday Pro Integration certification briefly only if you have real experience with them