Lead Applications Developer - Workday Functional Configuration

UPS
IN flag
Chennai, TN
Full-timeFunctional
SalaryTurbin est.
₹2.2M–3.4M≈ $26k–40k/yr
Seniority
Lead / Principal
Hands-on configuration
80%of the role is configuring in the tenant
Systems
Workday only

Overview

Turbin's analysis on the role ·

Workday Time Tracking and Absence lead configurator.European localization experience is essential.

Despite the developer title, this role focuses strictly on functional solution design, configuration, and prototyping for Time Tracking, Absence, and Scheduling. The posting explicitly emphasizes country-specific functional configuration across European jurisdictions.

Skills, by how much you'll use them

From Turbin's read of the posting
3 skills
Every day

The core of the job. Lead with these.

  • Time Tracking
  • Absence
  • Scheduling and Labor
2 skills
Working knowledge

Expected, but not what you are hired for.

  • Core HCM
  • Integrations

What you'll do

4 responsibilities
  • Solution Workday Time Tracking, Absence, and Scheduling configurations ensuring cohesion and mitigating cross-functional impacts
  • Gather business requirements, configure, maintain, design, and support integrations for Time Tracking, Absence, and Scheduling
  • Identify design options through rapid prototyping and recommend approaches to meet functional requirements
  • Demonstrate strong stakeholder management to achieve project objectives across global implementations

Do you fit?

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

How to pitch yourself

Turbin's advice

Lead with your hands-on configuration experience in Workday Time Tracking and Absence, specifically highlighting any work supporting European countries like the UK, Germany, Italy, or Belgium.

  1. Highlight specific time and absence business processes and rules you configured for multi-country European rollouts
  2. Detail your experience partnering with stakeholders on Scheduling and time capture integrations
  3. Note Core HCM and integration touchpoints as context rather than primary focus