Job Summary
IDC IAM Architect 1. Role Purpose The L4 technical authority for delivering Identity Services change now. The role takes the programme\'s immediate security objectives, assesses the live environment, designs the solution needed to solve the problem at hand and gets it implemented. Depending on scale and risk, they either implement alone or in partnership with the Managed Service Provider. They work autonomously and own the outcome. The role works side by side with the Operational Delivery Owners. They run the business, and this role transforms the business. 2. Why the Role Exists • A security-heavy programme has short-term objectives that need significant identity change, with some digital workplace impact. • The Head of End User Computing lacks the bandwidth to design and validate it personally. • Delivery needs someone who can read live systems and design changes that are safe for production. • Operational teams need to stay focused on running services while a dedicated expert leads the change. 3. Key Responsibilities Architecture and Design • Design practical, short-term architecture to solve the problem at hand across identity services, on-premises and cloud. • Establish the true current state from live configuration, including risks, drift and technical debt. • Produce designs, runbooks, impact assessments and rollback plans. • Record key technical decisions. Implementation and Technical Leadership • Decide the delivery approach for each change, based on scale and risk: • Alone: implement complex or high-risk changes personally. • In partnership: work with the Managed Service Provider, giving clear step-by-step instructions and validation criteria, and quality-assuring the results. • Act as the L4 technical escalation point for change-related issues. • Coach Managed Service and IDC colleagues. Security Programme Delivery • Work with the Security Program & Project Manager to turn the Information Security Manager\'s requirements into an operable technical reality. • Deliver specific, agreed jobs within a reasonable time. • Confirm with Security that each delivered change meets the requirement. Security owns the overall security posture. Collaboration with Operational Delivery Owners • Plan change around live service needs and minimise operational impact. • Hand over changed services with documentation and knowledge transfer, so they can run them in BAU. • Use their operational insight in designs, so what is built is supportable. Planning and Governance • Break objectives into work packages with estimates and dependencies. • Report status and risks clearly to the programme and senior stakeholders. • Follow change governance. 4. Technical Scope • Identity (core): Active Directory and Microsoft Entra ID, including hybrid environments, authentication and access controls. • Security: Identity security controls, hardening and compliance. • Automation: Scripting and tooling to deliver and maintain the changes. • Digital Workplace (strong nice to have): Device and endpoint management (Intune) and policy management (Group Policy). 5. Skills and Experience Essential • 10+ years in enterprise infrastructure or identity, 5+ at architect or lead level. • Expert in Active Directory and Entra ID in complex hybrid environments. • Proven delivery of large-scale security-driven change. • Can analyse live systems and design safe change without complete documentation. • Hands-on scripting and automation skills. • Experience working in partnership with Managed Service teams and quality-assuring their work. • Excellent English communication, and works independently. Strong Nice to Have • Working knowledge of Intune and Group Policy. Desirable • Relevant Microsoft certifications (e.g. SC-300, AZ-500, MD-102). • Security framework knowledge (NIST, CIS, ISO 27001). • ITIL and global delivery centre experience. 6. Behaviours Ownership (delivers, not just designs) | Autonomy | Pragmatism | Precision in production change | Calm under pressure