Workday Financials Technical Developer

Optum, a UnitedHealth Group Company
PH flag
National Capital Region
Full-timeTechnical
Salary
Salary not listed
Seniority
Senior
Hands-on configuration
90%of the role is configuring in the tenant
Systems
Workday only

Overview

Turbin's analysis on the role ·

Technical Financials support and build role.Functional P2P depth matters as much as technical skill.

Despite the developer title, the role blends functional Financials and procure-to-pay configuration with technical reporting, security, and integration support. Core duties center on Financials modules, custom reports, and production troubleshooting, while Studio appears only within general integration support.

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.

  • Core Financials
  • Procurement
  • Reporting
  • Integrations
  • Security
1 skill
Working knowledge

Expected, but not what you are hired for.

  • Workday Studio
3 skills
Only mentioned

Named in the posting. Safe to skip.

  • Inventory
  • Release management
  • Tenant migration

What you'll do

7 responsibilities
  • Configure and enhance Workday Financial Management modules including Procurement, Supplier Accounts, Accounts Payable, and Spend Management
  • Support end-to-end procure-to-pay processes covering requisitions, purchase orders, invoicing, payments, and reconciliations
  • Configure and maintain Workday business processes, approval workflows, condition rules, validations, and notifications
  • Develop and maintain Workday custom reports, dashboards, calculated fields, and custom data sources

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 hands-on Workday Financials and procure-to-pay configuration alongside custom reporting and security administration. Highlight integration support across EIB and Connectors, and note Workday Studio only if you have supported or debugged it in production.

  1. Show end-to-end procure-to-pay configuration scope, such as "configured Procurement and Supplier Accounts business processes, condition rules, and approval workflows"
  2. Detail your reporting build work with specifics like custom data sources, calculated fields, and financial reconciliation reports used by accounting teams
  3. Include concrete production support examples covering domain security fixes, tenant migrations, and release regression testing
  4. Mention EIB, Connectors, APIs, and Workday Studio briefly with the exact troubleshooting or maintenance tasks you handled