Technical Program Manager, Infrastructure

Responsibilities

• Own complex migrations end to end. Lead large-scale infrastructure migrations across teams and domains. Scope the work, sequence dependencies, manage risk, and drive them to completion without surprises.
• Drive process across infrastructure. Establish and run the operating rhythms that keep programs healthy: planning cadences, status reporting, decision logs, risk reviews, and escalation paths.
• Help managers build the right structures. Partner with engineering managers and leads to design the team structures, ownership boundaries, and working models a program needs to succeed.
• Own follow-ups relentlessly. Track every open item, own the action register, and close loops. Drive decisions and unblockers to resolution.
• Create clarity from ambiguity. Take loosely defined goals and turn them into scoped, sequenced, resourced plans with clear owners and measurable milestones.
• Manage risk and dependencies. Maintain a clear-eyed view of cross-team dependencies and risks; surface them early, drive mitigation, and keep leadership informed with honest, signal-rich updates.
• Communicate up, down, and across. Translate between deeply technical teams and senior leadership. Run effective program reviews and write crisp status updates.

Requirements

• 3+ years of technical program management experience, with a track record of delivering large, cross-team infrastructure or platform programs.
• Demonstrated ownership of complex migrations or comparable multi-domain initiatives from inception through completion.
• Strong execution discipline: build the structures, cadences, and tracking that keep programs on the rails, and hold the line on follow-through.
• Comfort operating across multiple infrastructure domains. Engage credibly with engineers on compute, storage, networking, and data.
• Proven ability to influence without authority, aligning teams and managers who don't report to you around shared plans and commitments.
• Excellent written and verbal communication; make complex, technical programs legible to any audience.
• A bias toward closure: uncomfortable with open loops and drive things to done.

Nice-to-Haves

• Experience designing team structures or operating models alongside engineering leadership.
• Experience with AI models, their use, and how they operate at the infrastructure level.
• Background in or exposure to software engineering, SRE, or infrastructure operations.
• Familiarity with the tooling that supports program execution at scale (e.g., issue tracking, planning, and reporting systems).