Member of Technical Staff - Product Engineering

Physical Intelligence Physical Intelligence · AI Frontier · San Francisco, CA · Software Engineering

Product Engineering role focused on building and owning the platform that enables external partners to use Physical Intelligence's models, including data ingestion, APIs, remote inference endpoints, and deployment integrations. The role requires strong software and systems engineering skills to support partners end-to-end, bridging research and partner needs.

What you'd actually do

  1. Build the platform that lets other companies use PI's models: give partners access to our models, fine-tuning, remote inference, and the services around them, so a robotics company can build on PI the way developers build on API-based LLMs. This spans data ingestion and APIs, a partner portal, and deployment integrations, all working end to end and self-serve.
  2. Ingest partner data end to end: take a new data or robot partner from their first sample to featurized, validated data in our system, and to a checkpoint they can eval.
  3. Deploy and serve partner models: stand up remote inference endpoints, validate them, and get partners running our policies at low latency in their own environment.
  4. Be the engineer embedded in partner engagements: sit in the partner channel, debug their deployment across the full stack, unblock them, and translate what they need into what we build.
  5. Write production-quality code that interfaces with PI's infrastructure.

Skills

Required

  • exceptional generalist software engineer
  • strong backend and systems design instincts
  • understand how to run inference with our models
  • strong engineering skills
  • clean Python
  • ability to interface with infrastructure
  • sharp debugging instincts
  • design a scalable system (databases, caching, APIs, services)
  • enough ML to run inference
  • deploy, serve, and debug our models
  • practical, ownership mindset
  • clear communication with researchers, operators, and partners
  • comfort with ambiguity
  • on-site, embedded partner work

Nice to have

  • robotics or ML research background
  • low-latency and real-time networking experience (inference transport, streaming, QUIC or websockets)
  • experience with robot manipulation platforms, VLAs, or other ML models
  • Familiarity with our stack: Python, Postgres, ClickHouse, GCP, Kubernetes, Modal, React and TypeScript

What the JD emphasized

  • own the product surface our partners touch
  • remote inference
  • partner data ingestion and APIs
  • deployment integrations
  • take a new partner from raw data to a deployed, evaluated model with little hand-holding
  • self-serve
  • run inference with our models
  • debug their deployment across the full stack
  • low latency

Other signals

  • building a platform for external partners
  • remote inference
  • partner data ingestion and APIs
  • deployment integrations
  • self-serve