Skills this job asks for
LeadershipProduct managementKubernetes
Add your CV (free) to see which of these your CV is missing.
Sponsorship verdict
No sponsorship evidence yet
No government record and no wording either way. Not a refusal: ask the recruiter.
-
?
No government sponsor record hereThis employer does not appear with approvals in the government data SponsorApply holds.
-
?
The posting doesn’t mention sponsorshipSilence isn’t a refusal — ask the recruiter before investing much time.
-
?
No salary bar for this routeH-1B has no fixed salary bar: the employer must pay at least the prevailing wage for the role and area.
-
✓
Confirmed live todayWhen a source last listed this job as open.
Details and sources
- No salary bar for this route
- H-1B has no fixed salary bar: the employer must pay at least the prevailing wage for the role and area. Cap-subject employers enter a lottery weighted by wage level. Source: https://www.federalregister.gov/documents/2025/12/29/2025-23853/weighted-selection-process-for-registrants-and-petitioners-seeking-to-file-cap-subject-h-1b, rules effective 2026-02-27.
US H-1B: cap-subject employers enter a lottery weighted by wage level — Level I gets 1 entry, Level IV gets 4 (DHS projected selection odds ≈15% at Level I to ≈61% at Level IV). Universities and non-profit research employers are cap-exempt. The $100,000 fee for new petitions from abroad is currently blocked by a court order (appeal pending).
A verdict summarises public evidence. It is not legal advice and never a guarantee: the employer and the immigration authority decide. Sign in to factor in where you can already work.
Before you apply
Sponsorship unknown
No register record and no sponsorship wording in the posting. Worth asking the employer before investing significant time.
These come from the posting’s own wording. Read the original listing to confirm. See better-fit alternatives →
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 decisio
Apply on employer site ↗