OpenAI logo

OpenAI

More roles at OpenAI

Technical Program Manager, Research Compute Services

Hybrid

Part remote, part office, you need to live within commuting distance of a named location.

Hybrid · San Francisco

Employer listed it 13 days ago · Added 12 days ago

First listed 13 days ago and still open.

Salary

$207k to $285k per year

Location

Hybrid · San Francisco

Timezone

Not stated

Contract

Full-time

Experience

Mid

Category

Operations

Published by the employer

What the advert says

Quoted word for word from the employer's advert. Where it says nothing, we say so.

Working hours
Not mentioned in the advert
Where you can work from
Background checks for applicants will be administered in accordance with applicable law, and qualified applicants with arrest or conviction records will be considered for employment consistent with those laws, including the San Francisco…
Contract
Not mentioned in the advert
Experience asked for
Not mentioned in the advert
Pay
Not mentioned in the advert

Remote flexibility

Hybrid

This role is only partly remote, the employer expects time in the office around San Francisco, Hybrid, so you need to live within commuting distance.

What the employer says

  • Source listing states candidate location: "San Francisco, Hybrid"
  • Listing mentions "Hybrid"

What Nomaders makes of it

  • Not suitable if you plan to move between countries

The quotes above are the employer's own words; the reading is ours. Always check the original listing and employment terms before working from another country.

Before you apply

Experience: employer states

Written as a requirement

  • “AI is an extremely powerful tool that must be created with safety and human needs at its core, and to achieve our mission, we must encompass and value the many different perspectives, voices, and experiences that form the full spectrum of humanity.”

Questions worth asking: Nomaders interpretation

  • This role involves office time, but the advert does not say how often. Ask how many days a week are expected on site.
  • The advert does not say whether this is employment or a contractor arrangement. Ask, as it affects tax and benefits.

Produced automatically from this advert's text; not reviewed by a person. The employer's own page is the final word.

About the role

About the Team

Research Compute Services builds the systems that help researchers use OpenAI’s compute fleet effectively. We partner with Research and Compute Infrastructure to support workloads across the compute stack, including pretraining, synthetic data generation, sampling, research inference, and reinforcement learning.

Our work connects changing research needs with capacity planning, allocation, and scheduling. We build tools and services that help researchers express their compute needs, access the right resources, and run their workloads effectively. As the fleet and our research ambitions grow, we continually improve how compute is planned, allocated, and used.

About the Role

You will be part of an engineer-first TPM team, partnering closely with the Research Compute Services team. Your primary responsibility will be to build and own the tools, data, and platform that turn Research plans and workload signals into concrete compute demand and manage allocations across the fleet.

This is a hands-on technical role. You will build alongside researchers and engineers, working directly with code and data to prototype solutions, automate workflows, and deliver tools that teams use every day. You will combine technical judgment and program leadership to connect capacity planning with the deployment, scheduling, and optimization systems that make allocated compute usable.

You will work across a broad range of Research workloads, understanding their different requirements and ensuring those needs shape the platform. Success means researchers can express their needs, understand their allocations, and use compute effectively as priorities and workloads change.

In this role, you will:

Build with Research. Work directly with researchers across pretraining, research inference, and other workloads. Treat these communities as core users, and translate their needs into improvements across compute services, tooling, and scheduling.

Own Research demand and allocation systems. Own the roadmap and delivery of the tools, data, and platform used to capture demand, support allocation decisions, and manage allocations. Carry this work from requirements and design through adoption and ongoing improvement.

Turn research plans into actionable demand. Develop systems that translate evolving plans and workload requirements into concrete capacity needs, including resource requirements, timing, and constraints.

Connect capacity supply and demand. Partner with Capacity Planning, Research, and infrastructure teams to reconcile demand with available supply. Build the tools and workflows needed to evaluate scenarios, manage changes, and make allocation tradeoffs visible to decision makers.

Build reliable data and useful tools. Create data models, views, and automation that show what researchers need, what capacity is available, what has been allocated, and how it is being used. Improve self-service workflows for requesting and managing compute.

Connect allocations to workload execution. Partner with engineers working on Kubernetes deployments and scheduling systems so allocation plans reflect workload constraints and translate into resources that researchers can use.

Improve allocation and scheduling efficiency. Work with engineers to evaluate optimization approaches, including solvers operating at fleet and local scheduling levels. Help define constraints and objectives, assess tradeoffs, and measure improvements in fleet utilization.

Find and address systemic gaps. Use workload and fleet data to identify bottlenecks, unused capacity, and recurring manual work. Build durable improvements to the tools and systems behind those problems.

Lead technical delivery across teams. Own plans, dependencies, and decisions across Research, Research Compute Services, Capacity Planning, and infrastructure engineering. Keep teams aligned on what needs to be built, how it will be adopted, and who will operate it.

Make progress and tradeoffs clear. Give working teams and leadership a clear view of demand, allocation constraints, delivery progress, and decisions that need attention.

You might thrive in this role if you:

Have a strong engineering foundation, developed through relevant education or demonstrated technical experience.

Have led and delivered complex technical programs involving large-scale compute, distributed systems, infrastructure platforms, or research environments.

Have practical experience with capacity planning, including supply and demand management, compute allocations, and the tools and data that support those decisions.

Have personally built or materially contributed to tools, data systems, or automation used by engineering or research teams. You are comfortable working directly with code and operational data.

Are familiar with Kubernetes deployments and scheduling systems, and understand how resource constraints and placement decisions affect workload execution.

Requirements

The employer hasn't listed requirements separately, they're described in the role summary above and on the original listing.

Benefits

No benefits package published with this listing. Ask about it at first interview.

How to apply

  1. 1Check the flexibility label above, hybrid, matches where you plan to live and work.
  2. 2Tailor your CV to the role at OpenAI, mentioning your remote working experience.
  3. 3Apply directly on the employer's careers page using the button below. Nomaders never handles your application.

Found 13d ago. Last checked today. Always confirm the details on the original posting, salary and location can change after publication.

Listing sourced from Company boards.

Similar roles

Other open operations roles with comparable remote rules.

Browse all open roles

$207k to $285k per year · You'll be taken to the employer's careers page.