Workday HCM Report Developer

Engagement length: 3 months, with strong likelihood of extension

Functional area: Workday HCM

Reports to: Internal Workday / HRIS team lead

OVERVIEW

Our client is working through a large backlog of custom Workday HCM reports — roughly 100 — that their implementation vendor has handed back for internal development, with an April completion target. The internal team is absorbing the bulk of that work and is looking to add contract capacity to move faster.

Running alongside that effort, the client is building a data replication layer that writes Workday data down to an on-premise SQL Server environment. Where Workday Core Connectors don’t cover a given business object, custom reports enabled as web services (RaaS) serve as the data source their integration developers consume programmatically.

This person will build reports across both workstreams and help the client establish a consistent, repeatable report development standard their internal team can adopt. The client owns the SQL Server side with existing resources — this role is focused squarely on Workday report development depth.

WHAT YOU'LL DO

• Build custom Workday HCM reports — Advanced, Matrix, and Composite — against a defined backlog
• Enable reports as web services for downstream consumption by integration developers
• Build and troubleshoot calculated fields, including nested and date-based logic
• Partner with integration developers so report output, field structure, and performance hold up under automated consumption — not just on-screen viewing
• Document a repeatable approach to report development: how to scope a request, how to select the right data source, when to use each report type, and naming and security conventions
• Advise the internal team on that standard so reporting is built consistently across functional areas

REQUIRED EXPERIENCE

• 3+ years hands-on Workday HCM report writing — custom builds, not just running delivered reports — with depth across Advanced, Matrix, and Composite report types
• Strong command of effective dating and how it behaves in reports consumed programmatically
• Fluency with core HCM business objects and data sources — Worker, Position, Job Profile, Organization, Compensation, Absence — and the ability to traverse related business objects
• Calculated field experience, including nested logic and date-based calculations
• Experience enabling Workday reports as web services (RaaS) for integration consumption
• Understanding of Workday HCM security and how role-based access shapes what a report returns
• Able to work a backlog independently and produce volume with minimal oversight

PREFERRED

• Workday Studio experience — a strong signal of a more technical report builder
• BIRT experience for custom-formatted and print-ready report output
• Workday integrations background: Core Connector: Worker, EIB, or Studio-built integrations
• Experience feeding Workday data into an external reporting or database environment
• Prior experience defining reporting standards or conventions for a team
• Payroll or benefits reporting exposure
• Exposure to Workday Financials business objects, in the event scope extends beyond HCM

TARGET PROFILE

The ideal candidate is a Workday consultant who would describe themselves as an expert report writer — not a generalist who reports as part of a broader HRIS role — with BIRT, Workday Studio, and integrations experience behind them.

SCREENING QUESTIONS

Use these to separate genuine report builders from candidates who have only run delivered reports.

• Give me three specific reports you have built — one Advanced, one Matrix, one Composite. For each: what business object, what calculated fields, and who consumed it.
• Tell me about a report where effective dating caused you a problem, and how you handled it.
• Have you enabled a report as a web service? Who consumed the endpoint and what broke the first time?
• Walk me through how you would set a reporting standard for a team — what are the first three steps on any new report request?