Technical Program Manager - Provider Management

Andromeda Cluster•San Francisco, CA

1d•Hybrid

About The Position

This role owns our provider relationships on the execution side. You'll run the programs that make a provider work well inside Andromeda. This includes onboarding new providers and sites, capacity rollouts, hardware and fabric quality issues, and major incidents. You'll be the person our providers answer to on delivery timelines and open items. When a customer's training run is down because of a provider-side failure, you're the incident commander: you run the response across our SREs, the provider's engineers, and the customer until it's resolved. You'll have no formal authority over provider teams. What you'll have is the plan, the escalation path, the contractual commitments, and the relationship. You'll need to be good at using all four. Nobody owns this end to end today; it gets picked up by whichever engineer has bandwidth, and both providers and customers have noticed the inconsistency. You'd be the first person in this role, so part of the job is defining what provider program management looks like here.

Requirements

Several years running technical programs in infrastructure.
TPM or technical project management with genuine execution ownership, ideally involving external vendors, partners, or suppliers you didn't control.
Incident management experience: you've commanded or run point on production incidents involving multiple organizations, and you're comfortable with the off-hours reality that comes with that.
Enough technical depth to hold your own with a provider's data-center engineers and our SREs on GPUs, networking, and storage. You don't need to debug an InfiniBand fabric yourself, but you need to follow the conversation and know when someone is hand-waving.
A track record of getting teams you don't manage, including external partners, aligned and moving, including through rough patches where the relationship is strained.
Solid fundamentals: planning, risk tracking, status communication, and keeping four or five programs on the rails at once.
Calm, direct communication. You'd rather deliver bad news early than good news late, and both providers and internal teams trust you because of it.
Comfort with ambiguity. The process you'll follow mostly doesn't exist yet; you'll write a lot of it.

Nice To Haves

Direct experience working with or inside neocloud, colocation, or data-center providers.
Vendor or supplier management background — SLAs, commitments, escalation frameworks.
Familiarity with the stack: NVIDIA data-center GPUs, InfiniBand/RoCE, Slurm or Kubernetes.
Experience supporting AI research labs or other large-scale GPU customers on the consuming side.

Responsibilities

Manage new provider and site onboarding, capacity expansions, remediation of recurring hardware or network issues, and provider relationships.
Act as incident commander during major provider-side incidents: assemble the right people from our SRE team, the provider, and the affected customer, run the response, own communication throughout, and drive the post-incident remediation program afterward. You own command and coordination; our SREs remain the technical leads making the engineering calls.
Keep a real plan for each program; milestones, owners, dependencies, risks. Maintain visibility to everyone involved, including the provider.
Hold providers to their commitments: structured check-ins, tracked action items, and escalation to provider leadership when things slip, backed by what's in the contract.
Coordinate internally so provider issues don't stall. Pull in SRE for validation, Engineering and Product for platform-side blockers, and keep Sales/Customer Success informed when provider timelines affect customer commitments.
Catch capacity and quality risk early, before it becomes a customer-facing problem.
Turn what you learn into playbooks and provider-facing standards, so onboarding the next site is faster and cleaner than the last.