Anvil Robotics

Anvil Robotics

Robot Platform Software Engineer

San Francisco, CA · Full-time

Sponsorship not specifiedDetected 6 days ago
CI/CDLinuxMachine LearningData EngineeringComputer VisionSystems EngineeringRoboticsElectrical EngineeringControlsResearchLeadershipCollaborationPlain LanguageActuators

About the role

  • You'll be the reason Anvil's robots keep running when nobody's watching - and the person who can explain why, in plain language, to both leadership and the customer standing next to a frozen arm.
  • Devkits are the wedge, not the business.
  • Every step of that strategy rests on one unglamorous fact: the robots already in the field have to keep working.

Responsibilities

  • We own and operate our own manufacturing in Taipei - no contract manufacturer in the loop - and in our first 12 months we built and shipped 200+ robots (OpenARM and OpenYAM manipulators,
  • internal teams (ML, controls, manufacturing) are not waiting on platform support for routine needs.

Requirements

  • Bachelor's or Master's in computer science, electrical engineering, robotics, or a related field.
  • A PhD isn't required or expected - this is a build-it-and-keep-it-running role, not a research role.
  • A typical req for a role like this might ask for 3-5 years

Nice to have

  • experience with containers, CI/CD, and cloud pipelines

Skills

  • the logging, metrics, debugging tooling, and data pipelines that move information between robots and the cloud.

Benefits

  • Every one of those 200+ robots runs on a platform layer nobody notices until it breaks: process orchestration, logging, health, and lifecycle, spanning hardware, ROS2 middleware, and the application layer above it.
  • Is trusted by leadership as the plain-language translator on robot learning progress, and by customers as a credible technical point of contact.

Company info

  • Anvil ships real robots to real customers, and each one depends on a runtime platform that currently has no single owner - reliability work happens, but it's not anyone's full-time job.
  • The same engineers who should be heads-down on
  • Most "it doesn't work" reports actually live at the boundary between hardware, ROS2 middleware, and application code - and the root cause is rarely in the layer where the symptom shows up.
  • This role is deeply communicative in two directions that have nothing to do with writing code: keeping Anvil's leadership informed on what's happening in robot learning and what it means for product and customers, in plain language; and working directly with deployment customers to understand their constraints and get them to a working outcome. Both audiences are non-technical relative to you, and making them smarter is part of the job, not a distraction from it.
  • You're comfortable debugging when the problem is unclear, the logs are incomplete, and the issue comes from an interaction between multiple complex systems.
  • You can genuinely explain deep technical reality in plain language to people who don't share your technical depth - Anvil's leadership and Anvil's customers alike.
  • Anvil is building the platform layer for Physical AI - robotics hardware and software that's radically more accessible than legacy industrial solutions.
  • That volume has earned us a custom force-sensing actuator partnership with major actuator OEMs, and the install base becomes both the distribution channel for our next- generation robots and a platform that software partners build on.

This listing is sourced directly from Anvil Robotics's careers page and normalized into a canonical job model.