Software Engineer, Robot Interfaces
Physical Intelligence
Listing collected from Physical Intelligence's career site. NextChapter is independent of Physical Intelligence.
San Francisco, CA · Posted September 24, 2026
Just laid off? Start here: a plan for the first weeks
See every open role at Physical Intelligence
More in California job market · All Software Engineer jobs (2,058) · Technology & Software · Engineering jobs
More roles at Physical Intelligence
- Manufacturing Engineer · Fremont, CA
- Build & Release Engineer · San Francisco, CA
- Prototype Engineer · San Francisco, CA
- Controls Engineer · San Francisco, CA
- Software Engineer, Data Quality · San Francisco, CA
- ML Infra Engineer, Data Systems · San Francisco, CA
Similar jobs
- Senior Software Development Engineer, Loyalty - Full Stack · Expedia Group · San Jose, CA
- Staff Software Developer, Unified Communications · Nvidia · Santa Clara, CA
- Staff Site Reliability Engineer · Circle Internet Group · San Francisco, CA
- Senior Software Engineer, Frontend · Circle Internet Group · San Francisco, CA
- Software Engineer II · Badger Meter · Los Gatos, CA
- EO/IR Systems Integration and Test Engineer · Heico · Santa Barbara, CA
Where San Francisco, CA ranks
Where San Francisco, CA placed in our monthly rankings, month by month. Each month stays online at its own address.
November 2026
- #1Best cities for security jobs316 openings · of 20
- #1Best cities for technology jobs7,178 openings · of 100
- #1Best cities for financial services pay after cost of living$173k · of 33
- #1Best cities for entry-level jobs that want AI skills35% · of 100
- #1Best cities for entry-level jobs that want AI skills in the West Coast35% · of 54
- #1Cities with the most jobs that do not need a four-year degree in the West Coast902 jobs · of 47
Rankings about engineering jobs
- Best cities for software and engineering jobs #1 San Francisco (3,412 openings)
- Best cities for engineering pay after cost of living #1 San Mateo ($216k)
- Most requested AI skills in engineering jobs #1 AI tools in daily work (6.1%)
- AI tools named most often in engineering jobs #1 Claude (1.7%)
- Employers with the most engineering jobs #1 Amazon (2,992 roles)
Pay compared with the market
This listing does not state pay. Across 750 open software engineer listings that state pay, the middle half runs $155,000 to $247,500 and the median is $194,500.
Listed pay is what employers advertise, not what people are paid.
How AI is used in this kind of work
Among software developers, AI is already used for some of the tasks. Measured exposure for software developers: 29% (some).
Share of this job’s tasks that AI is already used for at work, from real usage. It is not a forecast of job loss, and a low number means no use seen yet. Source: Anthropic Economic Index.
Skills this job asks for
Say which you have and which you want to build. We use it to match you to jobs like this one.
About the job
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.
As a Fullstack Software Engineer, you will build internal products that help Pi's research and operations teams move faster. You will work closely with operators, roboticists, researchers, and other engineers to turn physical workflows into reliable software.
The Team
Fullstack builds the internal software the rest of Pi runs on. Our users span the path from research intent to physical execution: researchers designing experiments and requesting data, Research Ops working across task design, environments, prototyping, and instructions, and Production Ops running collection, evals, and deployments across our lab, warehouse, and real-world sites.
In This Role You Will
- Own the human-robot interfaces: The software people use to run, monitor, and debug robots, from setup and calibration through live operation and review. Someone lives in this for an entire shift, and small friction compounds fast.
- Design for the whole shift, not just the episode: Time on a robot is a fraction of the day. The rest is preparation, troubleshooting, handoffs, and feedback, spread today across several tools and several people. The goal is not to expose every tool, but to build one surface that tells someone what deserves their attention now and notices when they're stuck.
- Design for safety: Make state unambiguous, make failure obvious, and make the safe action the easy one. Assume the network drops mid-episode or a camera dies, and design so the system degrades predictably rather than surprisingly.
- Own the realtime edge: Video, robot state, and control at latency budgets tight enough that teleoperation feels direct, plus the controllers, headsets, pedals, and sensors people drive with.
- Draw the line between device and cloud: Decide what has to stay local because it is safety-critical or latency-sensitive, and what belongs in a control plane that owns identity, state, and coordination across sites.
- Ship into the physical world: On-prem and on-device deployment, versioning and rollout across lab, warehouse, and partner sites, and enough observability to know what is running where.
- Make the work measurable: Instrument these interfaces well enough that we can see where the operation loses time, then test changes against it.
- Act as your own PM: Gather requirements, prioritize, define success metrics, ship, and drive adoption. That starts by standing in the room and watching a shift.
What We Hope You'll Bring
- Strong fullstack engineering experience building production web applications and APIs, especially with React, TypeScript, and Python.
- Realtime web experience: WebRTC, WebSockets, streaming video, state synchronization, and the debugging that comes with all of it.
- Comfort with binary wire formats and schema-defined interfaces: protobuf, gRPC, or similar. Most of what these interfaces talk to is not a REST API.
- Experience shipping software that runs on machines you do not administer: on-prem or on-device deployment, degraded-network operation, versioning across a fleet.
- Strong UX instincts for high-stakes, high-frequency interfaces, where the user is standing up, under time pressure, and a mistake has physical consequences.
- Comfort designing workflows where people, hardware, and software have to function as one system.
- Strong product judgment, and experience working directly with users through ambiguous workflows and evolving requirements.
Bonus Points
- Former founder, early employee, or other demonstration of comfort with ambiguity and solving hard problems end to end.
- Experience with teleoperation, robotics, or other robot-adjacent software.
- Experience with safety-critical or industrial systems (control room, medical device, aviation, automotive, or similar) where interface decisions carry real consequences.
- Hardware-adjacent background: firmware, embedded, device integration, or having shipped software alongside a physical product.
- Experience with workflow, dispatch, or scheduling systems that direct human work in the physical world.
- Experience with our specific stack: React, TypeScript, Python, Postgres, GCP, and Kubernetes.
Pursuant to the San Francisco Fair Chance Ordinance, we will consider for employment qualified applicants with arrest and conviction records.