Sr. Software Engineer - Robot Platform

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.

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.

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.