Senior Developer Workday

Empower (empower)
IN flag
Bengaluru, KA
Full-timeTechnical
SalaryTurbin est.
₹2.2M–3.4M≈ $26k–40k/yr
Seniority
Senior
Hands-on configuration
80%of the role is configuring in the tenant
Employer
Customer
Systems
Workday only

Overview

Turbin's analysis on the role ·

Hands-on Workday integrations developer role.Studio and Core Connectors are central, not extras.

Every duty centers on designing, building, testing, and supporting Workday integrations with third-party systems. Core technical tools like Studio, EIB, Core Connectors, and Web Services are the bar, while HCM module breadth, BIRT reporting, and security model understanding serve as supporting knowledge.

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
  • Web Services
5 skills
Working knowledge

Expected, but not what you are hired for.

  • Workday HCM
  • BIRT Reporting
  • RaaS
  • Business processes
  • Security model
3 skills
Only mentioned

Named in the posting. Safe to skip.

  • Document Transformation
  • XML and XSLT
  • SOAP and REST

What you'll do

6 responsibilities
  • Gather and analyze requirements and provide technical advice and best practices for Workday integrations
  • Design, build, test, and deploy custom Workday integrations across the full implementation lifecycle
  • Monitor integration runs to ensure successful completion and resolve production defects
  • Enhance existing Workday integrations to support evolving business requirements

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

Expected, not the bar

  • Solid understanding of Workday security model including integration users and groups

How to pitch yourself

Turbin's advice

Lead with end-to-end integration builds using Workday Studio, EIB, Core Connectors, and Web Services, and note your HCM module, BIRT reporting, and security knowledge as supporting strengths.

  1. Detail full-lifecycle integration builds, specifying scale, third-party endpoints, and tools like Studio, EIB, or Core Connectors
  2. Highlight production support experience, such as 'monitored integration runs and resolved defect backlogs with minimal supervision'
  3. Specify which three or more Workday HCM modules you know functionally and how that domain knowledge informed your integrations
  4. Mention BIRT reporting, RaaS, and integration security user setup briefly if you have real experience with them