Workday Integration Engineer

Meta
US flag
Menlo Park, CA
Full-timeTechnical
Salary
$145k–202kper year
Seniority
Senior
Hands-on configuration
70%of the role is configuring in the tenant
Systems
Workday only

Overview

Turbin's analysis on the role ·

Hands-on integrations build and architecture role.Studio and connectors are the bar, not Extend.

Responsibilities center on designing, building, and troubleshooting high-volume Workday integrations across internal and vendor systems. Studio, EIB, and Core Connectors are required at six years, while reporting sits in support and Extend or tenant admin tasks are nice-to-have extras.

Skills, by how much you'll use them

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

The core of the job. Lead with these.

  • Integrations
  • Workday Studio
  • EIB
  • Core Connectors
3 skills
Working knowledge

Expected, but not what you are hired for.

  • Custom reports
  • Calculated fields
  • Workday Extend
3 skills
Only mentioned

Named in the posting. Safe to skip.

  • Tenant configuration
  • Payroll
  • Data loads

What you'll do

6 responsibilities
  • Serve as subject matter expert for large collections of Workday integrations
  • Lead research, design, development, testing, and delivery of new Workday integrations
  • Create detailed integration specifications, field mappings, and deployment designs
  • Perform root cause analysis on integration failures and report findings to leadership

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

  • Experience with Workday Extend application implementation and orchestrations
  • Experience applying AI tools and ethical AI practices to optimize workflows
  • Experience driving large architectural changes across Workday and other systems
  • Familiarity with Workday tenant configuration, data loads, and payroll maintenance

How to pitch yourself

Turbin's advice

Lead with end-to-end integration builds in Workday Studio, EIB, and Core Connectors at scale. Mention custom reporting, Extend, or AI workflow experience briefly only if you have actually delivered them.

  1. Show the scale and volume of your Workday integrations, such as "Built 25+ Studio and Core Connector feeds linking HCM and payroll to external vendors"
  2. Highlight root cause analysis and architectural improvements where you redesigned failing or slow integrations across multiple downstream systems
  3. Include cross-functional stakeholder alignment on data flows and multi-month delivery timelines, which the role emphasizes alongside coding
  4. Note custom reports, calculated fields, or Workday Extend briefly to match secondary requirements without overshadowing core integration work