ML Engineer - API Platform

Physical Intelligence
San Francisco, CA
On-site

Who this role is best for

Best suited to backend engineers with experience in developer platforms and AI infrastructure working in San Francisco.

Best fit for

  • Backend engineers with a track record in developer platforms and AI infrastructure
    — “We’re particularly excited about people who have built developer platforms, model APIs, or infrastructure products outside of robotics.”
  • Individuals who can design systems that scale from small to large user bases
    — “Design systems that can scale from a small number of deeply integrated partners to thousands of organizations and potentially millions of robots.”
  • Candidates familiar with Python and cloud infrastructure technologies
    — “Strong Python skills and the ability to work comfortably across infrastructure and product boundaries.”

Things to consider

  • The role requires a strong focus on production systems and product APIs, not just ML research
    — “This is a software and systems role first. Robotics experience is not required.”
  • Candidates should be prepared to work closely with researchers and engineers on evolving model capabilities
    — “Work closely with researchers to turn new model capabilities into stable, usable product surfaces.”

How to stand out

  • Highlight experience with multi-tenant infrastructure and rate limiting in your resume and interviews
    — “Architect reliable, multi-tenant infrastructure around rate limiting, isolation, backpressure, versioning, observability, and SLOs.”
  • Emphasize your ability to build low-latency inference systems and handle real-time workloads
    — “Build and operate low-latency inference systems that allow Pi models to control robots running in real-world environments.”
  • Showcase your experience with deploying and debugging ML models in production environments
    — “Enough familiarity with machine learning systems to deploy, serve, and debug models in production.”
  • Demonstrate your ability to design product surfaces that simplify complex systems for external users
    — “You’ll own this experience end to end, turning capabilities that today require close collaboration with our team into a platform.”
  • Show a clear understanding of how to build systems that handle large-scale operational complexity
    — “An understanding of the problems that emerge as systems scale: reliability, latency, multi-tenancy, versioning, observability, and operational complexity.”
Pace · Fast PacedCollaboration · HighAutonomy · MediumDecision Impact · Team

Derived from job-description analysis by Serendipath's career intelligence engine.

What success looks like

  • building scalable model API
  • turning research into usable product surfaces
Typical background
strong software engineering fundamentalsbackend and systems experience

Skills & requirements

Required

API DevelopmentBackend SystemsDistributed SystemsInfrastructureProduction Code

Preferred

AI ExperienceRobotics Experience

Stack & domain

API DevelopmentModel APIData IngestionFine-tuningEvaluationLow-latency InferencePartner-facing ToolsDeployment IntegrationsMulti-tenant InfrastructureRate LimitingIsolationBackpressureVersioningObservabilitySlosPartner DataProduct ExperienceValidationProcessingLow-latency Inference SystemsRoboticsAIInfrastructureApisServicesDatabasesCachingDistributed SystemsDeveloper PlatformsModel ApisInfrastructure ProductsTeamworkProblem SolvingCommunicationAdaptabilityLeadershipAttention To Detail

About the role

Original posting from Physical Intelligence via Ashby

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.

We’ve made significant progress toward building models that can control many different robots across a wide range of tasks. Now, we’re building the platform that will make those models accessible to the broader world.

As an API Product Engineer, you’ll build the product surface that allows other companies to use Pi’s models much like developers use an LLM API today: bring their own data, fine-tune models, evaluate them, and run low-latency inference in their own environments.

You’ll own this experience end to end, turning capabilities that today require close collaboration with our team into a platform that can eventually support thousands—and ultimately millions—of robots.

THE TEAM

Software Engineering at Pi builds the systems that scale research breakthroughs into reliable products in the physical world.

This role sits at the intersection of our AI, infrastructure, and external partners. You’ll work closely with researchers and engineers to turn rapidly evolving model capabilities into APIs and tools that external users, from hobbyists to large organizations, can actually build on.

Today, onboarding a new partner to Pi can involve significant hands-on work. The goal is to make that increasingly unnecessary: partners should be able to bring us data, fine-tune a model, evaluate it, and run inference through a product that is intuitive, reliable, and built to scale.

IN THIS ROLE YOU WILL

This is a software and systems role first. Robotics experience is not required, and we’re particularly excited about people who have built developer platforms, model APIs, or infrastructure products outside of robotics.

  • Build Pi’s model API end to end, including data ingestion, fine-tuning, evaluation, low-latency remote inference, partner-facing tools, and deployment integrations.
  • Design systems that can scale from a small number of deeply integrated partners to thousands of organizations and potentially millions of robots.
  • Architect reliable, multi-tenant infrastructure around rate limiting, isolation, backpressure, versioning, observability, and SLOs.
  • Turn partner data into a first-class product experience, from initial upload through validation, processing, fine-tuning, and evaluation.
  • Build and operate low-latency inference systems that allow Pi models to control robots running in real-world environments.
  • Work closely with researchers to turn new model capabilities into stable, usable product surfaces.
  • Learn from how partners use the platform and turn recurring friction into better APIs, tooling, documentation, and abstractions.
  • Write high-quality production code that integrates deeply with Pi’s existing infrastructure.
  • Define what the developer platform for general-purpose robotics should look like. There is no established playbook for this yet.

WHAT WE HOPE YOU'LL BRING

  • Strong software engineering fundamentals and experience building production systems.
  • Deep backend and systems experience across APIs, services, databases, caching, distributed systems, and infrastructure.
  • Experience building and scaling developer platforms. We’re especially interested in people who have shipped platforms for model fine-tuning, inference, or other compute-intensive workloads.
  • An understanding of the problems that emerge as systems scale: reliability, latency, multi-tenancy, versioning, observability, and operational complexity.
  • Enough familiarity with machine learning systems to deploy, serve, and debug models in production. You do not need to be an ML researcher.
  • Strong Python skills and the ability to work comfortably across infrastructure and product boundaries.
  • A high degree of ownership. You’re comfortable taking an ambiguous problem, building the first version end to end, and then designing the system so it no longer depends on you.

BONUS POINTS IF YOU HAVE

  • Experience building low-latency or real-time systems, including streaming, inference transport, WebSockets, QUIC, or similar technologies.
  • Experience building model-serving, inference, fine-tuning, or developer-platform infrastructure.
  • Experience at an early-stage infrastructure, AI, robotics, or autonomous systems company.
  • Familiarity with our stack: Python, Postgres, ClickHouse, GCP, Kubernetes, Modal, React, and TypeScript.
  • Experience with security, authentication, authorization, or multi-tenant infrastructure.

WHAT THIS ROLE IS NOT

  • This is not a Customer Success role. You won’t own ongoing partner support or change management inside customer organizations.
  • This is not a Partner Roboticist or Applied Research role. You won’t be responsible for training policies for individual partners or debugging robots on site.
  • This is not a traditional ML infrastructure role focused primarily on training systems, compilers, or accelerator scheduling. You’ll work closely with those systems, but your focus is the product and platform through which the outside world uses Pi’s models.

Pursuant to the San Francisco Fair Chance Ordinance, we will consider for employment qualified applicants with arrest and conviction records.

Source: Physical Intelligence careers (Ashby)

Similar roles