Job Description & Details
This is a heavy-hitting architecture gig focused on locking down complex SAP landscapes during enterprise transformations. If you enjoy untangling messy role designs and setting up bulletproof compliance frameworks without breaking production, this 12-month contract is worth a serious look.
What You'll Actually Be Doing
You'll be spending your days designing, implementing, and governing enterprise-wide access controls and authorization frameworks across a massive SAP footprint. You won't just be clicking buttons in PFCG; you'll be architecting end-to-end security strategies for S/4HANA, Fiori, and cloud extensions while wrangling stakeholders across business units to clean up Segregation of Duties (SoD) conflicts and pass grueling audits.
The Core Tech Stack
You need absolute mastery over SAP S/4HANA Security Architecture, SAP Fiori Security Design, and SAP GRC/IAG. The team relies heavily on these tools to automate risk mitigation and manage identity governance. If you haven't architected role designs from scratch for global transformations or handled complex integrations involving BTP or SuccessFactors, you're going to hit a wall fast.
Interview Expectations
Expect the hiring manager to throw a scenario at you where a critical business user needs emergency access to a production environment that completely violates SoD rules, and they'll want to know how you handle that risk without stopping business operations. They are secretly testing your backbone and your ability to balance enterprise security protocols with pragmatic business needs. You'll also likely get grilled on how you architect Fiori security at scale, specifically dealing with OData services, PFCG roles, and catalogs versus groups.
Application Advice
Your resume needs to scream enterprise-scale SAP transformation, not just routine maintenance. Make sure keywords like SAP S/4HANA Security Architecture, SAP GRC, SAP IAG, and Fiori Security Design are front and center in your experience bullets. Highlight specific numbers—like the size of the user bases you've managed or the number of SoD conflicts you've remediated—to prove you operate at an architectural level.