Technical Lead - Workday Integration

Aristocrat
IN flag
Noida, UP
Full-timeTechnical
SalaryTurbin est.
₹2.4M–3.5M≈ $29k–42k/yr
Seniority
Lead / Principal
Hands-on configuration
60%of the role is configuring in the tenant
Systems
Workday only

Overview

Turbin's analysis on the role ·

Hands-on Workday integrations lead role.Studio and PECI are core, not secondary skills.

Every duty centers on designing, building, testing, and maintaining Workday integrations, with Studio and PECI named specifically. Reporting tools like RaaS, custom reports, and calculated fields support those feeds, while middleware like Boomi or MuleSoft is only a plus. Fits a senior technical 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
  • Studio
  • PECI
  • EIB
  • Web Services
6 skills
Working knowledge

Expected, but not what you are hired for.

  • Custom reports
  • Calculated fields
  • RaaS
  • iLoads
  • XSLT
  • XPath
4 skills
Only mentioned

Named in the posting. Safe to skip.

  • Data conversion
  • Business processes
  • Dell Boomi
  • MuleSoft

What you'll do

8 responsibilities
  • Lead the development of complex Workday integrations connecting HR, payroll, and benefits partners
  • Build and configure integrations using Workday Studio, PECI, EIB, RaaS, web services, XSLT, and XPath
  • Develop Workday custom reports and complex calculated fields to support integration solutions
  • Lead data conversion efforts and manage impacts on business processes, including Workday iLoads

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 with middleware such as Dell Boomi or MuleSoft

How to pitch yourself

Turbin's advice

Lead with end-to-end Workday Studio and PECI integrations you have built for HR, payroll, and benefits partners, including design, testing, and production support. Keep middleware like Boomi or MuleSoft brief unless you have hands-on integration experience with it.

  1. Show Workday Studio and PECI complexity with concrete scope, such as "Built PECI payroll and benefits feeds using Studio, XSLT, and custom calculated fields for multi-country employees"
  2. Highlight full lifecycle ownership from technical design specifications and unit or system integration testing through production cutover and vendor monitoring
  3. Include data conversion and Workday iLoads experience alongside how your integrations interacted with core business processes
  4. Mention RaaS, EIB, web services, or Boomi and MuleSoft briefly and only where you have real delivery experience