OpenAI logo

OpenAI

More roles at OpenAI

Technical Lead - Training Runtime, Data(set) Movement

Hybrid

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

Hybrid · San Francisco

Employer listed it 5 months ago · Added 2 months ago

Been open since 5 months ago. Long-running listings are sometimes left up after the role is filled.

Salary

$380k to $500k per year

Location

Hybrid · San Francisco

Timezone

Not stated

Contract

Full-time

Experience

Lead

Category

Software

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.”

Written as a nice-to-have

  • “Are comfortable working across Python and lower-level systems code; Rust or C++ experience is useful but not required.”

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

Training Runtime builds the distributed systems that power OpenAI's largest model training runs - most recently GPT-5.5! The Data Movement area owns the infrastructure that keeps training jobs supplied with the right data at the right time, and keeps model state moving safely and efficiently across large clusters.

Our work spans machine learning systems, distributed storage, high-throughput data loading, reliability engineering, and developer experience. Success means researchers can move quickly while training runs remain fast, reproducible, debuggable, and resilient at scale.

About the Role

We are looking for a deeply hands-on Technical Lead to own datasets throughout our training infrastructure. This person will set the direction for how training jobs read data: the APIs, storage contracts, versioning model, benchmarks, debugging tools, and reliability guarantees that make data access consistent across current and future training frameworks.

You will begin as the primary technical owner for dataset reads, working directly in the code while aligning researchers, training framework owners, storage teams, and infrastructure partners around a durable platform. The problem is deceptively hard at frontier scale: make enormous, heterogeneous datasets easy to consume, correct across distributed workers, observable when something goes wrong, and flexible enough to support pretraining, reinforcement learning, and multimodal training.

In this role, you will

Design and build a unified dataset read platform for multiple current and future training frameworks.

Define dataset APIs, storage-format expectations, registration/versioning, and migration paths that make data access reproducible and maintainable.

Build reliability into the read path, including stateful iteration, caching, fast restart, recovery, and clear operational contracts.

Build terminal and web-based visualizers that let teams inspect text, multimodal, and reinforcement learning data late in the pipeline, where bugs are most visible.

Write and review production code in core data loading, service, caching, and reliability paths.

Partner with teams working on training frameworks, reinforcement learning, multimodal models, storage, runtime, and cluster infrastructure.

Over Time

The long-term goal is a team that owns fast, correct, scalable, and reliable in-cluster data movement for training: data that comes in, data that goes out, and data that moves around inside the cluster. After ramping on datasets, this role will expand to ownership for broader data movement systems, including checkpoint loads/saves and snapshot transfers, while partnering closely with existing technical leads and adjacent infrastructure teams.

You might thrive in this role if you:

Have built or owned dataset, data loading, storage, or distributed training infrastructure at large scale (e.g. torch.utils.data )

Care equally about API design, debugging ergonomics, performance, and bit-level correctness.

Understand the failure modes of large distributed training jobs and know how data systems can create or prevent them.

Have experience with stateful iterators, checkpoint/restart semantics, caching, remote services, or high-throughput storage reads.

Are comfortable working across Python and lower-level systems code; Rust or C++ experience is useful but not required.

Have worked with multimodal, video, reinforcement learning, or pretraining data pipelines where small data bugs are expensive and hard to diagnose.

Obsess over developer experience by eliminating friction, such as manual preprocessing scripts and niche cluster-specific bugs, ensuring a reliable and efficient experience for researchers.

About OpenAI

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 2mo 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 software roles with comparable remote rules.

Browse all open roles

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