Workday Associate Consultant

Strada
US flag
Kuala Lumpur, MY
Full-timeTechnical
SalaryTurbin est.
$85k–115k
Seniority
Mid-level
Hands-on configuration
90%of the role is configuring across client tenants
Systems
Workday only

Good to know. Candidates must have current and future work authorization in the employing country without visa sponsorship. Offers are contingent on background checks, which may include identity, education, employment, criminal history, global watchlist, credit, or drug screening.

Overview

Turbin's analysis on the role ·

Hands-on integrations build role.Studio and EIB are the core, not extras.

The responsibilities center on building and maintaining integrations with Studio, EIB, Core Connectors, Cloud Connect, and web services, backed by a three-year Workday integration and Studio requirement. Custom reporting and middleware sit around the edges. Fit goes to a hands-on integration 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
  • Web Services
  • XML and XSLT
3 skills
Working knowledge

Expected, but not what you are hired for.

  • Reporting
  • Middleware platforms
  • JSON
4 skills
Only mentioned

Named in the posting. Safe to skip.

  • HR business processes
  • Finance business processes
  • Release management
  • Data privacy

What you'll do

8 responsibilities
  • Build and maintain integrations using Workday Studio, EIB, Core Connectors, and Cloud Connect
  • Develop custom reports, data extracts, and transformation logic using XML, XSLT, and JSON
  • Use Workday Web Services (SOAP and REST) and APIs for real-time data exchange
  • Monitor, troubleshoot, and audit integrations to maintain data integrity

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

Nice to have

  • Workday Integration certification

How to pitch yourself

Turbin's advice

Lead with your hands-on Workday Studio, EIB, and web services builds, and show you can own integrations from requirements through troubleshooting. Keep custom reporting and middleware secondary unless you used them directly alongside your integration work.

  1. Highlight end-to-end Workday Studio and EIB builds, noting scope and data flows such as "built Studio and EIB feeds between Workday HCM and payroll"
  2. Spell out your hands-on work with XML, XSLT, SOAP, and REST APIs for real-time or scheduled data exchange
  3. Include examples of gathering requirements from HR, Payroll, or Finance teams and translating them into technical specifications
  4. Mention custom reporting or middleware platforms briefly and only if you have direct experience using them in production