Workday Integration Analyst

Glencore
IN flag
Chennai, TN
Full-timeTechnical
SalaryTurbin est.
₹1.4M–2.4M≈ $17k–29k/yr
Seniority
Mid-level
Hands-on configuration
90%of the role is configuring in the tenant
Systems
Workday only

Good to know. The role is listed for Chennai, India, with Melrose, Johannesburg, South Africa also noted in the posting. Applications may be subject to background checks.

Overview

Turbin's analysis on the role ·

Hands-on Workday integrations build role.Studio, PECI, and web services are all core.

Every duty centers on designing, building, and supporting Workday integrations across Studio, EIB, Core Connectors, PECI/PICOF, and SOAP/REST APIs. HCM and Payroll appear as data domains for those feeds rather than functional configuration work, fitting a hands-on integration developer.

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
  • Workday Studio
  • EIB
  • Core Connectors
  • PECI and PICOF
4 skills
Working knowledge

Expected, but not what you are hired for.

  • XML and XSLT
  • SOAP and REST
  • Secure transfer protocols
  • Deployment automation
4 skills
Only mentioned

Named in the posting. Safe to skip.

  • HCM
  • Payroll
  • Tenant refreshes
  • Upgrades

What you'll do

8 responsibilities
  • Design, develop, test, and deploy Workday integrations using EIB, Workday Studio, Core Connectors, PECI/PICOF, and SOAP/REST web services
  • Build and maintain inbound and outbound integrations supporting HCM and Payroll
  • Transform, validate, and map integration data using XML, XSLT, and scripting
  • Troubleshoot production integration issues, perform root-cause analysis, and implement corrective actions

Do you fit?

Tick what you have. Only you see this.
0 of 8 must-havesTick what you have to see your match.
Must have · 8

How to pitch yourself

Turbin's advice

Lead with end-to-end Workday integrations you have built in Studio, EIB, Core Connectors, and PECI/PICOF, along with production troubleshooting. Mention your XML, XSLT, and secure transfer experience briefly to demonstrate technical depth.

  1. Detail specific Studio, EIB, and PECI/PICOF feeds you built, noting external domains such as payroll, timekeeping, benefits, or identity systems
  2. Include concrete troubleshooting and automation examples, such as resolving failed production runs, adding alerting, or streamlining deployments
  3. Show ownership of technical design documents, runbooks, test plans, and upgrade or tenant refresh support, plus any mentoring of junior analysts
  4. Mention XML, XSLT, SOAP/REST, and protocols like SFTP or OAuth only where you have directly configured and used them in integrations