> Markdown version of [/jobs/ext/1316536-robot-platform-software-engineer](https://www.wearedevelopers.com/jobs/ext/1316536-robot-platform-software-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Robot Platform Software Engineer - **Company:** ANVILS AND ROBOTS LLC - **Location:** San Francisco, CA, United States - **Experience:** Experienced - **Contract:** Permanent contract - **Skills:** Board Bringup, Application Programming Interfaces (APIs), Artificial Intelligence, Application Layers, Computer Vision, Continuous Integration, Software Debugging, Middleware, Hardware Interface Design, PCI Express, Software Construction, System Software, Data Logging, Real Time Systems, Information Technology, Data Pipelines - **Published:** July 17, 2026 - **Apply:** https://www.indeed.com/viewjob?jk=72ce7a328d38295e ## About the Role * You care about systems that actually work in the real world, not just clean abstractions on paper. * You're wired toward root cause analysis, not durable-looking patches that just address the symptom. * You move fast: bugs resolved in days, not weeks; features shipped in weeks, not months. * You're comfortable working across boundaries - hardware, middleware, and application layers - rather than staying in one layer. * You prefer incremental improvements over large rewrites. * You're pragmatic: you choose the solution that works reliably over the one that's theoretically elegant. * 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. * Bonus: familiarity with CAN, cameras, sensors, or real-time systems; experience with containers, CI/CD, and cloud pipelines; exposure to Physical AI models, robot control systems, or computer vision. * Based in or willing to relocate to Taipei or San Francisco - we're hiring for this role in both locations: one seat next to the hardware team and production line in Taipei (strong China-based candidates are also in scope for this seat), one alongside leadership and the demo room in San Francisco - with flexible hours for cross-timezone collaboration when a deployment or debugging issue is urgent. Education & experience: * 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. * Years matter less to us than trajectory. A typical req for a role like this might ask for 3-5 years; we're looking for someone with 1-3 unusually fast-growing years (or 1-2 on a steep curve) spent working directly alongside a senior platform/infrastructure or robotics systems engineer - someone who watched how real cross-layer root-causing happens, closed a growing share of real issues personally, and is ready to carry meaningfully more of that responsibility themselves. ## Description * Reliability and root cause: keeping robots running 24/7, and fixing hardware, ROS2, and infrastructure issues at the actual root cause, not with a patch that just moves the symptom. * Clean, stable hardware interfaces - APIs between sensors/actuators and the application layers above them- so upstream teams don't have to think about the hardware boundary. * Observability and cloud: the logging, metrics, debugging tooling, and data pipelines that move information between robots and the cloud. * Internal enablement: unblocking ML, controls, and manufacturing quickly - factory testing workflows, experimental URDF or hardware branches, photoshoot/demo configurations, hardware bring-up and PCIe validation, and generally "closing the loop" on last-mile hardware+software problems. What the first 100 days look like: * By day 30: ramped on the runtime platform architecture, the ROS2/hardware stack, and current known issues. Has personally closed at least one internal-team unblock (factory testing, bring-up, or a demo config) and shadowed a customer debugging session end to end. * By day 60: has shipped a first real reliability fix or platform improvement that measurably reduces recurring internal escalations. Is the first line of response for at least one class of hardware/software boundary issue. * By day 100: internal teams (ML, controls, manufacturing) are not waiting on platform support for routine needs. Is trusted by leadership as the plain-language translator on robot learning progress, and by customers as a credible technical point of contact., * Not a feature-building software role scoped to a single service. The job is keeping the entire system working continuously, predictably, and debuggably - across layers, not within one. * Not a research role in ML, perception, or controls. You enable those teams and translate their work; you don't own their algorithms. * Not a role for someone who wants to stay in one layer - just ROS2, just hardware, or just cloud. The real work lives at the boundaries between them. * Not a scripted, decision-tree support role. Every internal or customer issue needs real root-cause judgment, not a runbook lookup. ## Related Videos - [Crypto-secure Data Management with In-Database Blockchain](https://www.wearedevelopers.com/videos/632-crypto-secure-data-management-with-in-database-blockchain) - [Developer’s Perspective: Overview of the Tezos Blockchain Ecosystem](https://www.wearedevelopers.com/videos/237-developer-s-perspective-overview-of-the-tezos-blockchain-ecosystem) - [Robots are coming into the wild! Full-Stack Robotics Engineers, be ready!](https://www.wearedevelopers.com/videos/479-robots-are-coming-into-the-wild-full-stack-robotics-engineers-be-ready) - [Build Delightful Mobile Experiences with Kotlin, Realm, and Atlas Device Sync](https://www.wearedevelopers.com/videos/694-build-delightful-mobile-experiences-with-kotlin-realm-and-atlas-device-sync) - [Exploring BOS: The Blockchain Operating System by NEAR Protocol](https://www.wearedevelopers.com/videos/781-exploring-bos-the-blockchain-operating-system-by-near-protocol) - [The New Org Chart: When AI Joins the Workforce](https://www.wearedevelopers.com/videos/100036-the-new-org-chart-when-ai-joins-the-workforce) ## Related Articles - [How to Become an AI Engineer](https://www.wearedevelopers.com/magazine/331-how-to-become-an-ai-engineer) - [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift) - [What is Software Engineering in the Age of AI?](https://www.wearedevelopers.com/magazine/640-what-is-software-engineering-in-the-age-of-ai) - [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline) - [Dev Digest 137 - AI'm not sure about this](https://www.wearedevelopers.com/magazine/485-dev-digest-137-ai-m-not-sure-about-this) - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers)