Senior Technical Program Manager, Release Management

Microsoft•Mountain View, CA

6h•$142,800 - $304,200

About The Position

At Microsoft AI, compute is the foundation everything else is built on: every frontier training run, every eval, and every inference workload depends on our GPU fleet. GPUs are our scarcest and most valuable resource. Leadership sets how that fleet is allocated; this role owns the entire system that makes those allocation decisions real - moving, provisioning, and validating quota across a constrained pool as fast and as cleanly as possible. We are looking for a Technical Program Manager. This is a high-agency, service-oriented role for someone who is relentless on detail and follow-through, never lets anything drop, and likes turning a fragmented, high-stakes process into a clean, scalable machine.

Requirements

Significant experience in technical program management within infrastructure, platform engineering, or other compute-intensive environments.
A record of proactively improving operating models: spotting process failures, convening the right people across organizations, and driving automation and streamlining without waiting to be asked.
High agency and a service-oriented mindset, comfortable relentlessly chasing and pushing across teams, without formal authority, to get things done fast.

Responsibilities

Own release management for every model we ship. Our current clip is one (1) model release per month.
Design MAI's launch process and launch gates, working closely with Product, Research/Eng, Responsible AI, Legal, Security, Regulatory (for Health), Creative, and Marketing.
Own the workback plan for each model from announcement.
Build our release playbooks from scratch in close collaboration with Product and Go-to-Market. There's no existing process to inherit, this roles would be defining how we launch our models.
Own relationships with all the key people up to and including Mustafa. Sit in technical meetings day to day, make sure the right people are on the right things, and catch it early when we've committed the same resource to more than one launch in a similar timeframe. In a field moving this fast, that kind of coordination is the difference between shipping first and shipping late.