Senior Technical Program Manager

GoDaddy

1d•Remote

About The Position

At GoDaddy the future of work looks different for each team. Some teams work in the office full-time; others have a hybrid arrangement (they work remotely some days and in the office some days) and some work entirely remotely. This is a remote position, so you’ll be working remotely from your home. You may occasionally visit a GoDaddy office to meet with your team for events or meetings. This position is not eligible to be performed in Alaska, Mississippi, North Dakota, or the Virgin Islands. Join our team GoDaddy is strengthening its software supply chain as a core part of protecting customers, preserving developer velocity, and reducing enterprise risk. Modern supply chain attacks increasingly exploit third‑party dependencies, identity gaps, and ownership blind spots across large codebases. The Senior Technical Program Manager drives a portfolio of cross‑functional initiatives that operationalize supply‑chain defences across the developer toolchain. You will partner with Developer Platform, Security, Identity, and Engineering teams to turn controls and policies into durable, measurable outcomes—closing systemic gaps while ensuring teams can continue to ship safely and efficiently. This role operates in ambiguity, leads through influence, and translates complex technical risk into clear programs, prioritized execution plans, and executive‑ready outcomes.

Requirements

7+ years of experience in technical program management (or closely related roles) supporting software engineering or platform organizations.
Proven ability to lead complex, cross‑team initiatives through influence rather than authority.
Strong technical proficiency with modern software development ecosystems, including source control, dependency management, CI/CD, developer platforms, AI & ML technologies (MLOps, Agentic AI), cloud platforms (AWS, Azure), and agile methodologies.
Demonstrated strength in written and verbal communication, including executive‑ready updates and clear, outcome-focused narratives.
Experience operating in ambiguous problem spaces where scope, sequencing, and ownership must be actively shaped.

Nice To Haves

Experience driving software supply chain security, platform governance, or large‑scale risk remediation programs.
Familiarity with third‑party dependency risk, vulnerability management, or secure software delivery practices.
Experience partnering with security, identity, or compliance teams in an engineering‑led environment.
Background working with developer tooling or platform organizations at scale.

Responsibilities

Own and drive cross‑functional programs that reduce software supply chain risk across third‑party dependencies, repositories, and identity controls
Take initiatives from problem definition → planning → execution → rollout → adoption → sustained outcomes.
Align multiple teams and workstreams into a cohesive plan with clear goals, ownership, dependencies, and success criteria.
Drive the end‑to‑end remediation of legacy cached dependencies that bypass modern intake controls.
Implement a phased remediation program (baseline risk assessment → comprehensive scanning and cataloguing → continuous monitoring) with measurable completion and ongoing governance.
Partner with platform and security, ensuring dependency controls are operationalized without degrading developer velocity.
Close repository ownership and routing gaps across thousands of repositories and multiple GitHub organizations.
Ensure security findings, incidents, and policy exceptions can be automatically routed to accountable owners without manual intervention.
Improve consistency of ownership metadata and governance signals across the repo footprint.
Support the migration to GitHub Enterprise Managed Users (EMU) as an externally directed identity governance requirement.
Coordinate across Identity, Security, and Engineering teams to ensure user lifecycle, access controls, and auditability are aligned.
Translate identity governance work into clear risk reduction outcomes and leadership‑level reporting.
Facilitate alignment across engineering, platform, and security teams with competing priorities.
Proactively manage risks, dependencies, and tradeoffs; drive decisions and escalation when needed.
Establish lightweight operating rhythms and status reporting that keep work moving and outcomes visible.