Workday AMS Technical Consultant

Huron
IN flag
Bengaluru, KA
Posted in 3 locations
  • IN flag
    Bengaluru, KA
  • IN flag
    Noida, UP
  • IN flag
    Pune, MH
HybridFull-timeTechnical
SalaryTurbin est.
₹1.1M–1.7M≈ $13k–20k/yr
Seniority
Mid-level
Hands-on configuration
90%of the role is configuring across client tenants
Systems
Workday + ServiceNow

Overview

Turbin's analysis on the role ·

Hands-on Workday AMS integrations support role.Production support and SLA triage matter as much as builds.

Every duty and requirement centers on developing, monitoring, and troubleshooting Workday integrations in an AMS model. Studio, EIB, Cloud Connect, and web services form the core stack, while certification is preferred rather than mandatory. Strong fit for an integration developer used to SLA-driven support.

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
  • Cloud Connect
  • Web Services
1 skill
Working knowledge

Expected, but not what you are hired for.

  • XML and XSLT
1 skill
Only mentioned

Named in the posting. Safe to skip.

  • Release management

What you'll do

7 responsibilities
  • Monitor, troubleshoot, and resolve Workday integration issues in an AMS production support environment
  • Manage incident, problem, and change processes while prioritizing tickets against SLA targets
  • Perform root cause analysis and drive process optimization and automation to reduce recurring issues
  • Assess Workday updates and releases for impact on existing integrations and adopt new features

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

  • Current Workday Integration or Workday Studio certification
  • Experience with integration monitoring tools and ticketing systems

How to pitch yourself

Turbin's advice

Lead with your hands-on experience supporting and building Workday integrations in an AMS or production support setting. Highlight your SLA ownership, troubleshooting, and core integration tools.

  1. Quantify your AMS support scope, such as "Resolved P1 and P2 EIB and Studio integration incidents within SLA and ran root cause analysis for recurring failures"
  2. Specify at least three core integration technologies you use regularly, including Workday Studio, EIB, Cloud Connect, or REST and SOAP web services
  3. Include release impact testing, runbook documentation, and ticketing workflows in ServiceNow or JIRA, since teams often overlook support hygiene
  4. Note any Workday Integration or Studio certification clearly at the top, and mention XML or XSLT briefly only where you have real hands-on use