Senior Technical Program Manager

Staff Technical Program Manager, Cybersecurity

We're looking for a Staff Technical Program Manager to drive delivery across our Enterprise Cybersecurity portfolio. Your first charter is our identity and access management (IAM) program — anchored by a large-scale migration from Client Entra  Okta — but this is a portfolio role, not a single-program role. As the identity program matures, you'll flex across the broader cybersecurity roadmap: security operations (SOC), governance/risk/compliance (GRC), vendor risk, security awareness, and whatever the function needs delivered next.

This role lives on relationships and prioritization as much as on plans. You'll coordinate across enterprise security, infrastructure, compliance, legal, endpoint/digital workplace, and enterprise application teams; align our identity roadmap with the product security teams' own identity projects; and manage external implementation partners — keeping many threads moving, visible, and correctly sequenced against each other. If you're equally comfortable talking federation cutover sequencing with an IAM architect, reconciling priorities across two security organizations, and translating program risk into a crisp update for executive sponsors, this role is for you.

• Own end-to-end program plans across the cybersecurity portfolio: scope, milestones, dependencies, resourcing, and critical path — starting with the Entra  → Okta migration, decomposing the multi-year identity vision into executable milestones.
• Coordinate federation, SSO, provisioning, and application onboarding work streams, sequencing cutovers and rollback/hypercare plans to protect business continuity, and managing the external implementation partner through delivery.
• Serve as the connective tissue between Enterprise Cybersecurity and the product security teams' identity initiatives: maintain a shared view of roadmaps and dependencies, surface collisions and overlaps early, and broker sequencing and ownership decisions so the two portfolios reinforce rather than block each other.
• Run the operating cadence — planning, status reporting, RAID (risks, actions, issues, decisions) tracking, and stakeholder syncs — across internal teams and external partners, managing dependencies and controlling change in a fast-moving environment.
• Drive cross-functional prioritization: build and maintain the relationships needed to get commitments from teams you don't manage, negotiate trade-offs when work streams compete for the same people, and keep leadership equipped to make priority calls with current, honest information.
• Juggle multiple complex problems in parallel and find creative solutions with limited resources — this is a lean team, and the answer is rarely "add headcount"; it's a smarter sequence, a lighter-weight process, or an unconventional path to the same outcome.
• Drive governance of non-human identities — service accounts, service principals, workload identities, and API credentials — spanning discovery, ownership assignment and attestation, least-privilege scoping, rotation, and decommissioning, with full lifecycle (joiner/mover/leaver) coverage for human and non-human accounts.
• Coordinate the identity↔endpoint seam with digital workplace and infrastructure teams: device trust, conditional/adaptive access, and device-posture signals informing access decisions.
• Partner with compliance and audit teams to operationalize controls, coordinate evidence collection, and keep programs aligned to framework requirements (TISAX, ISO 27001, NIST CSF/800-53).
• Report up and down with equal fluency: help prepare the reports, briefings, and materials that keep executives, sponsors, and delivery teams aligned on the same priorities — playing a pivotal role in the team's success by making its work visible, understood, and correctly prioritized.
• Translate technical requirements into terms non-technical teams (legal, procurement, facilities, HR, business stakeholders) can act on, communicating priorities so every team understands what's needed from them, why, and by when.
• Maintain program artifacts and single sources of truth (roadmaps, Gantt/status decks, RACI, action logs) in…