Technical Workday Developer

Basebiz
IN flag
Bengaluru, KA
Full-timeTechnical
SalaryTurbin est.
₹1M–1.8M≈ $12k–21k/yr
Seniority
Mid-level
Hands-on configuration
100%of the role is configuring across client tenants
Employer
Partner
Systems
Workday only

Overview

Turbin's analysis on the role ·

Hands-on Workday integrations build role.Studio and full-stack integrations are the whole job.

Every duty and skill centers on building and maintaining inbound and outbound Workday HCM integrations. Studio, EIB, Core Connectors, Web Services, and XML transformations are all core requirements rather than supporting skills. Best suited for a pure technical Workday integrations 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
  • EIB
  • Core Connectors
  • Web Services
1 skill
Only mentioned

Named in the posting. Safe to skip.

  • HCM

What you'll do

7 responsibilities
  • Develop, maintain, and customize complex inbound and outbound Workday integrations
  • Build and support complex integrations using Workday Studio
  • Develop inbound and outbound interfaces with Enterprise Interface Builder (EIB)
  • Configure, develop, and customize Workday Core Connectors

Do you fit?

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

How to pitch yourself

Turbin's advice

Lead with end-to-end Workday integration builds across Studio, EIB, and Core Connectors, highlighting SOAP and REST API work and XSLT transformations.

  1. Detail complex Workday Studio integrations you built from scratch, noting data volume, error handling, and third-party endpoints such as "built Studio inbound payroll feed for 15k employees"
  2. Highlight specific EIB and Core Connector customizations paired with XML, XSLT, and XPath transformation logic rather than just listing the acronyms
  3. Specify which third-party payroll, benefits, or HR platforms you connected to Workday HCM and whether you owned both inbound and outbound flows