!Good to know. Background and reference checks are part of the selection process. Applications are open until November 30, 2026, though the role may close earlier.
Overview
Turbin's analysis on the role ·
Workday security and reporting lead role.Integration governance is expected, not building.
Daily work centers on Workday security configuration, access governance, custom reporting, and audit support across HR processes. Integration tools like Orchestrate, Studio, and EIB are only nice-to-haves, while understanding ISUs and ISSGs is needed for access governance.
Skills, by how much you'll use them
From Turbin's read of the posting
4 skills
Every day
The core of the job. Lead with these.
Security
Reporting
Access governance
Audit support
3 skills
Working knowledge
Expected, but not what you are hired for.
Integrations
ISUs and ISSGs
APIs
2 skills
Only mentioned
Named in the posting. Safe to skip.
Release management
GDPR
What you'll do
8 responsibilities
Configure and maintain group-level Workday security groups, roles, domain security, and business process security policies
Ensure consistent Workday security design across countries, legal entities, organizations, and HR processes
Manage access requests, role assignments, access reviews, exceptions, and security clean-up activities
Maintain Workday security-role and data-access documentation, including ownership and approval requirements
Do you fit?
Tick what you have. Only you see this.
0 of 6 must-havesTick what you have to see your match.
Must have · 6
Expected, not the bar
Understanding of Workday integrations, Integration System Users, and Integration System Security Groups
Nice to have
Workday Security, Reporting, HCM, or Integration certification
Experience with Orchestrate, EIB, Studio, Core Connectors, APIs, RaaS, Extend, Prism Analytics, or TIGA
Experience with Workday release management, regression testing, structured change management, and international organizations
How to pitch yourself
Turbin's advice
Lead with hands-on ownership of enterprise Workday security policies, security groups, access reviews, and custom audit reporting. Treat integration topics as access governance rather than hands-on integration development.
1Highlight security configuration scope such as "owned domain and business process security policies across multiple countries and legal entities"
2Detail your audit and governance work, including periodic access reviews, privileged access controls, and preparing evidence for external auditors
3Include concrete reporting examples like building custom reports and calculated fields to support security reconciliations and compliance tracking
4Mention working knowledge of ISUs, ISSGs, or tools like EIB, Studio, or TIGA briefly only if you have directly configured or governed them