Senior Workday Engineer

CoStar Group
US flag
Arlington County
HybridFull-timeTechnical
Salary
$143k–187kper year
Seniority
Senior
Hands-on configuration
90%of the role is configuring in the tenant
Systems
Workday only

Good to know. The schedule requires Monday through Thursday in the office with the option to work from home on Friday. Pre-employment substance abuse testing is required.

Overview

Turbin's analysis on the role ·

Hands-on Workday integrations engineering role.Integration builds and security are the core of the role.

The duties center on building and maintaining vendor integrations, data controls, and Workday security. Functional modules, Extend, and Prism appear mostly as configuration support or in tool lists. This fits an experienced Workday technical developer rather than a functional analyst.

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
  • Security
  • EIB and Connectors
  • Web Services
6 skills
Working knowledge

Expected, but not what you are hired for.

  • Workday Extend
  • Workday Prism
  • HCM and Recruiting
  • Payroll and Benefits
  • Absence
  • Report Writing
3 skills
Only mentioned

Named in the posting. Safe to skip.

  • Compensation
  • Performance Management
  • Business processes

What you'll do

7 responsibilities
  • Maintain inbound and outbound Workday integrations with multiple vendors
  • Configure, test, and deploy integration solutions with business and IT stakeholders
  • Configure Workday security for authorized system access
  • Assist with technical configuration for new features in recruiting, absence, payroll, performance, and benefits

Do you fit?

Tick what you have. Only you see this.
0 of 8 must-havesTick what you have to see your match.
Must have · 8

How to pitch yourself

Turbin's advice

Lead with your Workday Studio, Core Connector, EIB, and web services integration builds along with your security administration work. Keep functional module configuration and newer tools like Extend or Prism brief unless you have shipped them in production.

  1. Detail end-to-end vendor integrations you built in Studio, EIB, or Core Connectors, such as "built PECI and REST integrations for five benefits and payroll vendors"
  2. Highlight security configuration ownership and data integrity controls you put in place to protect downstream feeds
  3. Include specific examples of web service standards you used, like SOAP, REST, PGP, or SAML, and note your 4+ years of development with 3+ years in Workday
  4. Only mention Extend, Prism, or functional module configuration briefly if you have real hands-on experience supporting them