Interim Identity and Engineering Access Programme Lead

Align engineering access with real responsibilities

Map the identities, privileged roles, service accounts and approval paths used across delivery environments. Identify ownership gaps, shared credentials and access that persists beyond the work that justified it. Review how emergency access operates and whether actions can be attributed and examined afterwards.

Candidate identity and delivery experience

Candidates need identity, access or technical programme leadership experience in complex engineering environments. They should understand privileged access, automation and operational support, and have delivered changes involving multiple service owners. Strong candidates can show how they balanced security objectives with practical adoption and measured whether the new arrangements worked.

Implement a workable access model

Lead the definition and rollout of roles aligned to actual tasks. Coordinate with platform owners, security teams and engineering managers to test whether proposed restrictions support necessary work. Where segregation of duties is required, establish a usable approval route rather than simply removing access and leaving teams to find informal workarounds.

Migrate automation as well as people

Plan migration and clean-up in stages, with clear validation and recovery arrangements. Ensure service accounts and automated processes are considered alongside human users; changing access without understanding an automated dependency can interrupt delivery or production. Build review responsibilities into the permanent operating model.

Delegation, exceptions and maintenance

The lead will own programme execution, dependency management and remediation reporting within the approved remit. They will not grant themselves access or assume authority to accept unresolved risk. Those decisions remain with designated owners. The engagement should leave a documented access model, accountable ownership and a repeatable joiner, mover, leaver and review process appropriate to the environment. Handover must identify temporary exceptions, their expiry or review conditions and the actions still required to remove them safely.