Job description

Join Us, and Ship Robots Weave was founded to build the robots we’d want to have in our own home. We believe the next generation of robotics will transform everyday life by enabling people to do more and to reclaim time to spend on what’s important. We also believe robots are in a sense like any other product: to matter, they have to ship. Our robots are already operating in real homes and businesses, giving us the opportunity to rapidly improve from real-world experience. With a growing team, strong customer demand, and capital for expansion, we’re entering an exciting stage of growth—and we’re looking for people with exceptional talent and standards to help bring home robotics to millions of households. The Role Weave builds and deploys some of the first bimanual robots operating in customer homes. On and off the robot sits an entire stack that makes the whole fleet run 24/7: on-robot drivers and services, streaming and telemetry, cloud backend, inference infrastructure, and the apps customers interact with every day. You'll build across all of it. One week it's a customer-facing feature in the app, the next it's the backend that serves it, the next it's the on-robot service that feeds it data. This is a role without lanes. You'll work with Specialists across the stack, but you'll own making the robot's capabilities reach the people and systems that need them. This will involve reading, debugging, and shipping code at any layer to do it. Responsibilities • Ship features end to end: from data originating on the robot, through backend services, to pixels on a customer's screen, owning every layer in between. • Build customer applications: web, mobile, and the real-time interfaces (live video, robot state, control) that make a robot in your home feel legible and trustworthy. • Build the fleet backend: telemetry ingestion, remote operations tooling, deployment infrastructure, and the services that keep a growing fleet observable and supportable. • Work on the robot when the problem lives there: instrument a service, fix the API you're consuming, or extend an on-robot component instead of filing a ticket and waiting. • Accelerate the team: building teleoperation consoles, data browsers, and ops dashboards. A quick prototype you build in an afternoon can change how fast the rest of the company moves. What You'll Bring • 3+ years shipping production software across at least two of: frontend/mobile, backend services, infrastructure, systems software. • Language range: strong in TypeScript and Python or Go, able to read and modify C++ or Rust when the bug is on the robot. • Distributed systems fundamentals: API design, streaming data, WebSockets or gRPC, databases, and failure modes of networked hardware. • Infrastructure competence: cloud deployment, containers, CI/CD, and observability you set up yourself. • Debugging range: you follow a bug across service boundaries, languages, and machines until you find it, not until it leaves your area. • Cross-functional experience: you keep app, robot, hardware, and ML teams moving by diving into system-wide issues and resolving boundary questions at a whiteboard, not over tickets. • Product judgment: you can take a one-line request from a customer and ship the right thing without a spec. Nice to Have • Experience with low-latency and robust video streams. • 3D visualization: Three.js, WebGL, Unity. • Robotics, consumer hardware, or connected-hardware products in production. • Security depth: OAuth/OIDC, token design, secure APIs for physical devices. • VR or teleoperation interface work.

Requirements

Must-haves

Join Us, and Ship Robots
Ship features end to end: from data originating on the robot, through backend services, to pixels on a customer's screen, owning every layer in between.
Build customer applications: web, mobile, and the real-time interfaces (live video, robot state, control) that make a robot in your home feel legible and trustworthy.
Build the fleet backend: telemetry ingestion, remote operations tooling, deployment infrastructure, and the services that keep a growing fleet observable and supportable.
Work on the robot when the problem lives there: instrument a service, fix the API you're consuming, or extend an on-robot component instead of filing a ticket and waiting.
Accelerate the team: building teleoperation consoles, data browsers, and ops dashboards. A quick prototype you build in an afternoon can change how fast the rest of the company moves.
3+ years shipping production software across at least two of: frontend/mobile, backend services, infrastructure, systems software.
Language range: strong in TypeScript and Python or Go, able to read and modify C++ or Rust when the bug is on the robot.
Distributed systems fundamentals: API design, streaming data, WebSockets or gRPC, databases, and failure modes of networked hardware.
Infrastructure competence: cloud deployment, containers, CI/CD, and observability you set up yourself.
Debugging range: you follow a bug across service boundaries, languages, and machines until you find it, not until it leaves your area.
Cross-functional experience: you keep app, robot, hardware, and ML teams moving by diving into system-wide issues and resolving boundary questions at a whiteboard, not over tickets.
Product judgment: you can take a one-line request from a customer and ship the right thing without a spec.

Nice-to-haves

Experience with low-latency and robust video streams.
3D visualization: Three.js, WebGL, Unity.
Robotics, consumer hardware, or connected-hardware products in production.
Security depth: OAuth/OIDC, token design, secure APIs for physical devices.
VR or teleoperation interface work.

Application prep

Use the role’s language and application details while tailoring your materials.

Keywords to mirror

apiresttypescriptpythongorustci/cdml

Platform: dover
Effort: medium