Hands-on Workday reporting and BI consulting role.Core reporting delivery matters more than ETL tools.
The duties center on designing, implementing, and supporting Workday reporting and BI solutions for clients. Advanced dashboards, data warehousing, ETL, and data modeling only appear as preferred items. A technical consultant who can translate business needs into Workday reports fits best.
Skills, by how much you'll use them
From Turbin's read of the posting3 skills
Every dayThe core of the job. Lead with these.
- Reporting
- Business intelligence
- Solution support
4 skills
Only mentionedNamed in the posting. Safe to skip.
- Dashboards
- Data warehousing
- ETL
- Data modeling
What you'll do
5 responsibilities- Collaborate with clients to gather reporting and BI requirements aligned with business objectives
- Design and implement Workday reporting and business analytics solutions
- Provide ongoing support and maintenance for client reporting and BI solutions
- Communicate complex reporting and BI concepts clearly to technical and non-technical stakeholders
- Work closely with project teams to deliver and sustain client analytics solutions
Do you fit?
Tick what you have. Only you see this.- Master's degree
- Exposure to advanced Workday reporting features including data visualization and dashboard creation
- Familiarity with BI tools and technologies such as data warehousing and ETL
- Experience applying data analysis techniques including data modeling and data mining
How to pitch yourself
Turbin's adviceLead with your hands-on experience designing, building, and supporting Workday reporting solutions for stakeholders. Treat external BI, ETL, and data modeling skills as secondary context unless you actively use them.
- 1Highlight specific Workday reports or dashboards you built, including business scope and audience, such as "designed executive headcount and turnover reports for global HR leaders"
- 2Show end-to-end delivery from gathering stakeholder requirements through ongoing maintenance and troubleshooting
- 3Include concrete examples of explaining technical reporting logic clearly to non-technical business partners
- 4Mention data warehousing, ETL, or data modeling tools briefly and only if you have real project experience with them