!Good to know. Must be willing to work during US business hours when required.
Overview
Turbin's analysis on the role ·
Technical Workday Supply Chain config and support role.Technical depth matters more than functional domain.
Daily work centers on configuring Workday Supply Chain business processes, calculated fields, custom reports, security policies, and supporting integrations. Integration tools like Studio, EIB, and Connectors are preferred extras, while functional procure-to-pay knowledge is only supporting context.
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.
Supply Chain
Business processes
Reporting
Integrations
Security
5 skills
Working knowledge
Expected, but not what you are hired for.
Workday Studio
EIB
Workday Connectors
APIs and web services
Procure-to-pay
3 skills
Only mentioned
Named in the posting. Safe to skip.
Release management
Change control
Regression testing
What you'll do
8 responsibilities
Configure, support, and enhance Workday Supply Chain capabilities, primarily Procurement and Inventory
Support end-to-end procure-to-pay and inventory processes and maintain supply chain foundation data
Configure and troubleshoot Workday business processes, condition rules, validations, routing, and security policies
Design and maintain operational reports, dashboards, calculated fields, and reconciliation controls
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
Expected, not the bar
Working knowledge of procure-to-pay and inventory processes
Nice to have
Workday Procurement, Inventory, Financial Management, or Spend Management support experience
Hands-on experience with EIB, Workday Connectors, Workday Studio, or APIs and web services
How to pitch yourself
Turbin's advice
Lead with your hands-on Workday technical configuration across business processes, calculated fields, custom reports, and security, plus production integration troubleshooting. Highlight any EIB, Connectors, or Studio experience you have, and keep functional procurement context brief.
1Show the scale of your Workday configuration work, such as "built 20+ calculated fields and custom reports supporting procurement and finance reconciliations"
2Detail production support and change-control rigor, including ServiceNow incident resolution, regression testing, and cross-tenant migration practices
3Call out security troubleshooting experience, such as analyzing domain and business process security policies affecting reports and calculated fields
4Mention EIB, Workday Connectors, Studio, or API work concisely only where you have real hands-on troubleshooting or build experience