Workday Integration Engineer

Asana
CA flag
Vancouver, BC
HybridFull-timeTechnical
Salary
CA$123k–140k≈ $89k–101k/yr
Seniority
Senior
Hands-on configuration
80%of the role is configuring in the tenant
Systems
Workday only

Good to know. Standard in-office days are Monday, Tuesday, and Thursday, with Wednesdays usually optional for remote work and Fridays dependent on team needs.

Overview

Turbin's analysis on the role ·

Hands-on Workday integrations build role.Studio and technical PM both matter here.

Responsibilities focus on designing, building, and troubleshooting inbound and outbound integrations with Workday Studio, EIB, Document Transformation, and APIs. You also run integration projects end to end with HR, Finance, and IT partners, so strong technical builders who can manage scope and timelines fit best.

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
  • Web Services APIs
  • Document Transformation
3 skills
Working knowledge

Expected, but not what you are hired for.

  • Core Connectors
  • Cloud Connect
  • XML and XSLT
1 skill
Only mentioned

Named in the posting. Safe to skip.

  • Release management

What you'll do

7 responsibilities
  • Design, build, test, and deploy Workday integrations using Workday Studio, EIB, Document Transformation, and web services APIs
  • Manage People Systems integration projects from requirements gathering and effort estimation through launch
  • Maintain and optimize inbound and outbound Workday integrations for data integrity, scalability, and reliability
  • Monitor and troubleshoot complex integration issues while maintaining strict HR data privacy

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 complex Workday Studio, EIB, and API integrations you have built and supported in production, along with projects where you owned requirements through launch. Highlight Core Connectors, Cloud Connect, and XML or XSLT where you have direct hands-on experience.

  1. Detail your Studio, EIB, and API builds with scale and direction, such as "built inbound and outbound Studio and EIB integrations across global HR and finance systems"
  2. Show end-to-end technical project ownership, including gathering requirements from non-technical HR partners, estimating effort, and tracking timelines to cutover
  3. Call out production support, performance tuning, and documentation like process flows or SOPs, which many integration resumes leave out
  4. Mention Core Connectors, Cloud Connect, XML, and XSLT concisely if you have used them in live environments