Software Engineer II (Workday Extend e Integraciones)

O'Reilly Autopartes México
MX flag
Guadalajara, JAL
Full-timeTechnical
SalaryTurbin est.
MX$800k–1.1M≈ $43k–59k/yr
Seniority
Senior

Overview

Turbin's analysis on the role ·

Hands-on Workday Extend and integrations engineering role.Extend and Studio depth matter more than functional setup.

Core duties center on building and supporting Workday Extend apps and integrations with Studio, Orchestrations, EIB, and Core Connectors. HCM, payroll, compensation, benefits, and recruiting appear only as integration domains, while reporting and security are desirable extras.

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.

  • Workday Extend
  • Integrations
  • Workday Studio
  • Orchestrations
  • Business processes
5 skills
Working knowledge

Expected, but not what you are hired for.

  • Core HCM
  • Payroll
  • Compensation
  • Benefits
  • Recruiting
4 skills
Only mentioned

Named in the posting. Safe to skip.

  • Reporting
  • Calculated fields
  • Security
  • CI/CD

What you'll do

7 responsibilities
  • Design, develop, and support complex Workday Extend applications for business processes
  • Build and maintain Workday integrations using EIB, Orchestrations, Core Connectors, Studio, and REST or SOAP services
  • Deliver technical solutions supporting HCM, payroll, compensation, benefits, and recruiting workflows
  • Lead technical discovery and translate business requirements into detailed designs and interface specifications

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

Nice to have

  • Workday certifications in Extend or Integrations
  • Knowledge of Workday Reporting, Calculated Fields, and the Workday Security Model
  • Familiarity with CI/CD practices and test automation for Workday solutions

How to pitch yourself

Turbin's advice

Lead with production Workday Extend applications and complex integrations you built end to end, especially using Studio and Orchestrations. Keep functional modules brief and framed around data flows rather than functional configuration.

  1. Detail specific Workday Extend apps you built, including business problem, architecture, and security or audit controls
  2. Highlight integration volume and tools used, such as "built Workday Studio and Orchestrations flows for HCM and payroll feeds"
  3. Show examples of code reviews, technical documentation, and production root cause analysis to match the technical leadership scope
  4. Mention familiarity with HCM, payroll, compensation, benefits, or recruiting data structures only where your integrations touched them