Application Analyst Senior - Workday/HCM/Payroll

Cone Health
US flag
Greensboro, NC
Full-timeFunctional
SalaryTurbin est.
$90k–125k
Seniority
Senior

Overview

Turbin's analysis on the role ·

Functional Workday Payroll and HCM analyst role.Payroll is central; integrations are supporting.

The posting centres on hands-on Workday Payroll and HCM configuration, testing, and production support. Absence, Benefits, EIBs, and integrations appear as secondary knowledge rather than dedicated build duties. A functional Workday Payroll specialist fits best.

Skills, by how much you'll use them

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

The core of the job. Lead with these.

  • Payroll
  • Core HCM
  • Business processes
4 skills
Working knowledge

Expected, but not what you are hired for.

  • Absence
  • Benefits
  • Integrations
  • EIB
2 skills
Only mentioned

Named in the posting. Safe to skip.

  • Release testing
  • Third-party systems

What you'll do

7 responsibilities
  • Serve as a Workday HCM and Payroll subject matter expert for daily operations and project initiatives
  • Configure Workday business processes, workflow validations, and system designs from user requirements
  • Support Workday integrations, EIBs, and third-party application implementations
  • Plan and execute application, integration, new release, and user acceptance testing

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

Expected, not the bar

  • Knowledge of Workday Absence and Benefits
  • Support experience with integrations and EIBs

How to pitch yourself

Turbin's advice

Lead with your hands-on Workday Payroll and HCM configuration and production support experience. Mention Absence, Benefits, and EIB or integrations troubleshooting briefly if you have them.

  1. Highlight Payroll and HCM scope, such as "Supported biweekly US Payroll and Core HCM business processes for 10,000+ employees"
  2. Show concrete testing ownership across new releases, integrations, and user acceptance testing rather than listing testing generically
  3. Include examples of translating user workflows into system configuration and resolving production data issues
  4. Note Absence, Benefits, and EIB support briefly only if you have direct experience with them