Workday Studio Integration Developer

Tata Consultancy Services
IN flag
Bengaluru, KA
Full-timeTechnical
SalaryTurbin est.
₹1.3M–2.6M≈ $15k–31k/yr
Seniority
Senior
Hands-on configuration
90%of the role is configuring across client tenants
Systems
Workday only

Overview

Turbin's analysis on the role ·

Hands-on Workday Studio integration build role.Studio is the job, not a nice-to-have.

The title and required skill set center on Workday Studio integration development across HR, payroll, and finance. Connectors, EIB, XSLT, and Document Transformation support that core build work, while Advanced Reporting and Prism appear only in the competency list.

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.

  • Studio
  • Integrations
  • Core Connectors
  • EIB
  • XSLT
3 skills
Working knowledge

Expected, but not what you are hired for.

  • Advanced Reporting
  • Prism
  • Calculated fields
4 skills
Only mentioned

Named in the posting. Safe to skip.

  • HCM
  • Payroll
  • Time Tracking
  • Absence

Do you fit?

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

Nice to have

  • Workday Integration and Advanced Reporting
  • Workday Prism Reporting and Analytics
  • Workday HCM, Payroll, Time, and Absence
  • Workday Studio integrations across HR, Payroll, and Finance
  • Workday Core Connectors and Workday Payroll Connectors
  • Workday Calculated Fields, EIB, XSLT, and Document Transformation

How to pitch yourself

Turbin's advice

Lead with end-to-end Workday Studio, Core Connector, and EIB integrations you have built across HR, payroll, and finance. Include Advanced Reporting, calculated fields, and Prism briefly only if you have real experience with them.

  1. Detail complex Workday Studio builds with scope and scale, such as "Built Studio payroll and finance integrations using XSLT and Document Transformation"
  2. Highlight experience with Core Connectors, Payroll Connectors, and EIBs across HCM, Time, and Absence data flows
  3. Mention Advanced Reporting, calculated fields, or Prism concisely if you used them to support integration testing or reporting outputs