
ML Infra Engineer, Compute
San Francisco, CAFull-timePosted todayStill listed · checked in the last 2 days
See where you stand before you apply. No sign-up to start.
You apply on the posting's application page, with no Olive account needed.
Watch jobs like this. New roles like this one near San Francisco, CA, by email.
Don't just apply. Show up ready.
Olive works from this exact posting.
At a glance
Olive focuses on jobs in the United States, including remote roles you can work from there.
Job overview
Physical Intelligence’s ML Infrastructure team builds systems that make large-scale model training reliable, reproducible, and fast. This role owns scheduling and compute infrastructure across heterogeneous GPU and TPU clusters, including job placement, cluster management, and operational tooling. The goal is to automate resource allocation so researchers can focus on science, while supporting efficient, resilient training and extending orchestration to inference and robot deployment.
Skills & qualifications
Skills
Full job description
Who We Are Physical Intelligence is bringing general-purpose AI into the physical world. We are a group of engineers, scientists, roboticists, and company builders developing foundation models and learning algorithms to power the robots of today and the physically-actuated devices of the future. The Team The ML Infrastructure team supports and accelerates PI’s core modeling efforts by building the systems that make large-scale training reliable, reproducible, and fast. You will work closely with ML Infra (training systems), data platform, and research teams to ensure compute scheduling is never the bottleneck. About the Role Physical Intelligence builds general-purpose AI for the physical world. Training our models requires orchestrating thousands of accelerators across a heterogeneous fleet of GPU and TPU clusters — spanning different hardware generations, cloud providers, and cluster topologies. Today, researchers often need to know which cluster to target, what resources are available, and how to configure their jobs accordingly. That doesn't scale. We need a scheduling and compute layer that makes the right placement decision automatically — routing jobs to the best cluster based on availability, hardware fit, cost, and priority — so researchers can focus entirely on the science. This role owns that problem end-to-end: the scheduling systems, the placement logic, the cluster management layer, and the operational tooling that keeps it all running. This is not cloud DevOps. It's not about standing up clusters and walking away. It's a systems role for people who care about intelligent resource allocation, utilization, fault tolerance, and making large-scale distributed training seamless. In This Role You Will
-
Own Intelligent Job Scheduling and Placement: Design and build multi-tenant scheduling systems that automatically place training jobs on the best available cluster based on hardware requirements, topology, availability, cost, and priority. Support fair resource sharing across teams and projects with quota management, priority tiers, and preemption policies. Abstract away cluster differences so researchers submit jobs without needing to know where they will land.
-
Scale Multi-cluster Orchestration: Build the control plane that manages the job lifecycle across diverse clusters (mixed GPU/TPU, multi-generation hardware, on-prem/cloud) and enables seamless job migration, failover, and re-scheduling.
-
Optimize Accelerator Utilization and Efficiency: Monitor and optimize GPU/TPU utilization across the entire fleet. Implement priority, preemption, queueing, and fairness policies that balance research velocity with cost efficiency.
-
Ensure Scaling and Stability: Implement fault detection, automatic recovery, and resilience for long-running multi-node training jobs. Manage health checking, node management, and scaling to thousands of accelerators.
-
Support Inference and Robot Deployment: Extend scheduling and orchestration to inference workloads, including deploying models to edge devices on physical robots.
-
Enhance Observability and Developer Experience: Build the dashboards, alerting, SLOs, and debugging tools necessary for researchers to understand job status and for the team to ensure high scheduling quality and cluster reliability.
What We Hope You'll Bring We’re intentionally flexible on exact background, but strong candidates usually have:
-
Strong software engineering fundamentals
-
Experience building or operating job scheduling / resource management systems at scale
-
Experience with large-scale compute clusters (GPU and/or TPU)
-
Familiarity with schedulers and orchestration systems (SLURM, Kubernetes, GKE, K3S, or internal equivalents)
-
Comfort reasoning about resource allocation, bin-packing, priority scheduling, and multi-tenancy
-
Understanding of how ML training workloads behave — long-running, multi-node, sensitive to stragglers, topology-dependent
-
A bias toward owning systems end-to-end, from design to operation
-
Enjoy working closely with researchers and unblocking fast-moving projects
Bonus Points
-
Experience building multi-cluster or federated scheduling systems
-
Experience with TPU infrastructure (GCP TPU slices, Multislice, GKE)
-
Background in cluster resource managers (Borg, YARN, Mesos, or custom schedulers)
-
Linux systems engineering, networking, and infrastructure-as-code
-
NCCL/collective communication and topology-aware placement
-
Experience with capacity planning and cloud cost optimization at scale
-
Familiarity with JAX, PyTorch, or similar ML frameworks at the runtime/systems level
Pursuant to the San Francisco Fair Chance Ordinance, we will consider for employment qualified applicants with arrest and conviction records.
How this job compares
Set against the 4,714 open Infrastructure Engineer jobs on Olive Jobs, counted November 17, 2026.
- Pay
- This postingNot listed
- California median$170–254K/yr725 salary ranges
- US median$50–65/hr87 hourly ranges
- Openings
- Olive Jobs lists 905 open Infrastructure Engineer jobs in California and 4,714 across the US. 9% of them nationwide are listed as remote or flexible.
- Experience
- Infrastructure Engineer postings that state a minimum ask for 6 years of experience at the median; the middle half ask for 5 to 8 years (3,769 postings).
- Education
- 609 of the 4,714 open Infrastructure Engineer jobs (13%) ask for a bachelor's degree or higher.
Counted across the open, public US postings on Olive Jobs on November 17, 2026. Figures based on too few postings are left out.
Prepare for this role
You've read the whole posting — now see how you match it.


