Back to jobs

ML Infra Engineer, Compute

San Francisco · San Francisco, California, United States

Actively hiring, first seen by us 1 day ago
Pay
Pay not listedSimilar roles state $166K–$237K
Work setting
On-site — work setting source
Location type: On-site
From the employer’s posting
Employment
Full-time — employment source
Employment type: Full-time
From the employer’s posting
Team
Machine Learning — team source
Department: Machine Learning
From the employer’s posting

What you’ll work on

Full posting

Physical Intelligence builds general-purpose AI for the physical world.

Today, researchers often need to know which cluster to target, what resources are available, and how to configure their jobs accordingly.

  • Design multi-tenant scheduling that auto-places training jobs by hardware, cost, and priority

  • Build the control plane for job lifecycle, migration, and failover across clusters

  • Implement quotas, priority tiers, preemption, and fairness policies across teams

  • Add fault detection and automatic recovery for long-running multi-node training jobs

  • Build dashboards, alerting, and debugging tools for job status and cluster reliability

From the employer’s posting
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.
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
Build the control plane that manages the job lifecycle across diverse clusters (mixed GPU/TPU, multi-generation hardware, on-prem/cloud)
Support fair resource sharing across teams and projects with quota management, priority tiers, and preemption policies.
Implement fault detection, automatic recovery, and resilience for long-running multi-node training jobs.
Build the dashboards, alerting, SLOs, and debugging tools necessary for researchers to understand job status

About Physical Intelligence

Physical Intelligence is bringing general-purpose AI into the physical world.

In the employer’s words · Read in context · Company website ↗

Apply at Physical Intelligence

Posting record

Report an error

Actively hiringFirst seen by us 1 day ago, still listed, and not a repost of an earlier posting.

Status in our records
Live
First seen by us
Nov 16, 20261 day ago
Recorded sightings
2
Last seen by us
Nov 17, 2026

These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.

How this job compares

Pay

$166K–$237K is typical

The middle half of what similar US postings state. This one doesn’t list pay.

From 1,505 postings in the last year. Stated ranges, not salaries paid.

Time since we first saw it

Day 1

Early. Similar jobs usually come down between day 7 and day 76.

From 5,795 similar postings that came down. Coming down is not always a hire.

Physical Intelligence is hiring

5 open jobs

Open jobs by the week we first saw them, last 12 weeks.

Hiring record

See how this role fits your experience

Add your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.

  • Kubernetes
  • PyTorch
Where the posting names them
- 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
- 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.

Your next step

Complete your application on jobs.ashbyhq.com. The employer’s form will show what is required.

Applying through Ashby

  • No account needed. “Autofill from resume” at the top of the form fills the key fields from your file.

Already applied? Track this application

Job description

View original posting ↗

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.

 

Demand for ML Engineer roles

New ML Engineer postings at the employers we follow are up 12% over the last 6 weeks compared with the 6 before.

Weekly new ML Engineer postings at the same employers, from the week of August 17 to the week of November 9. The fewest in a week was 556, the most 1,080, and the latest week had 556.
August 17Last week

Each bar is one week of new postings. The darkest bars are the last 6 weeks.

Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.

About the role

We file this job under ML Engineer, by the work the posting describes.

ML engineers put machine learning models into products. They write the code that trains, ships, serves and monitors models so a recommendation or prediction works for real users.

Postings ask for strong Python and software engineering, a framework such as PyTorch, cloud services, and more and more often experience with large language models.

A data scientist often works out which model to build; an ML engineer makes it run reliably in production.

US government figures for computer and information research scientists

Median yearly pay, May 2025
$140,300
Expected change, 2025 to 2035
21.8% more jobsagainst 3.5% for all jobs

The government has no code for ML engineers, so these figures are for the closest group, computer and information research scientists.

Source: US Bureau of Labor Statistics, Occupational Employment and Wage Statistics (May 2025) and Employment Projections (2025 to 2035). Occupation code 15-1221.

Source details

View original posting ↗

Source notes

Source excerpts

Selected passages from the saved posting. Check the full description for conditions and exceptions.

Pay

No pay amount identified in the saved description.

Location & working pattern

San Francisco, California, United States

Working pattern and location restrictions need checking in the full posting.

Work authorization

No clear work-authorization passage found. Eligibility is unconfirmed.

Find answers in the posting

AI
How answers work

AI selects complete passages from this posting. Check them for conditions and exceptions.

Uses this posting and your question. No profile needed.