!Good to know. This is a hybrid position requiring 3 days a week on-site at the corporate Galleria office in Houston, Texas.
Overview
Turbin's analysis on the role ·
Hands-on integrations build role.Studio and Core Connectors are the core work.
The role sits in HRIS and focuses entirely on designing, coding, testing, and supporting Workday integrations across Studio, EIBs, and Core Connectors. Functional domains like HCM, Finance, and Payroll are integration touchpoints rather than configuration targets.
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
Core Connectors
EIB
XSLT
3 skills
Working knowledge
Expected, but not what you are hired for.
BIRT
Advanced Reporting
Calculated Fields
3 skills
Only mentioned
Named in the posting. Safe to skip.
Core HCM
Payroll
Finance
What you'll do
7 responsibilities
Design, build, test, and maintain integrations using Workday Studio, Core Connectors, EIBs, and APIs
Partner with cross-functional teams across HR, Payroll, and Finance to translate business requirements into scalable integration solutions
Write and maintain XSLT and MVEL expressions to manipulate data and automate business logic within Workday Studio integrations
Troubleshoot complex production issues, debug integration errors, and optimize performance
Do you fit?
Tick what you have. Only you see this.
0 of 7 must-havesTick what you have to see your match.
Must have · 7
Nice to have
Knowledge of MS Excel, SQL, C sharp, .NET with Visual Studio, TFS, HTML, JavaScript, SFTP, and encryption
Experience utilizing CI/CD tools such as Bitbucket, TFS, GitHub, Jenkins, or SVN
Experience communicating effectively with diverse business and IT staff in a multinational environment
How to pitch yourself
Turbin's advice
Lead with your technical depth in Workday Studio, XSLT, and Core Connectors, highlighting complex integrations you built and supported end to end.
1Detail specific Studio and Core Connector integrations you delivered, noting protocols, transformations, and error handling mechanisms
2Highlight experience with change-detection connectors like PECI or WECI and complex XSLT or MVEL logic
3Keep functional configuration mentions focused on how you collaborated with functional leads to gather data requirements