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 RoleAs an Embedded Software Engineer, you'll build the software closest to our hardware, on a compute platform we design ourselves: custom carrier boards, MCUs, and the sensors and actuators around them. MCU firmware, bus protocols, drivers, board bring-up, user-space drivers. When a new board arrives, you're the first person to make it do anything. You'll sit at the seam between electrical engineering and the rest of software, turning new hardware into a reliable platform the rest of the robotics stack can be built on.
ResponsibilitiesDevelop production embedded software: Design, implement, test, and maintain embedded software for robotic systems using modern C++. Develop firmware, device drivers, communication stacks (SPI, I2C, RS-485, CAN/CAN FD, Ethernet, or EtherCAT), and interfaces for sensors, actuators, and other embedded peripherals.
Bring up new hardware: Collaborate with hardware and electrical engineers to integrate new circuits, and validate system functionality. You’ll need to be able to read and understand component datasheets to build and debug drivers for them.
Build real-time systems: Develop deterministic software that meets timing constraints while managing concurrency, resource limitations, and hardware failures.
Own the buses: GMSL SerDes links, RS-485, CAN, SPI/I²C. Electrical-to-software debugging with a scope and analyzer when a bug refuses to pick a layer. On the actuator bus you own the compute side; your peer Actuator Firmware engineer owns the other end.
Systematize bring-up: First power-on of new boards with the EE team, bring-up checklists that become manufacturing tests, and closing the gap between "works on my bench" and working on mass-produced units.
3+ years of experience developing embedded software: bare-metal, RTOS, and/or Linux-based platforms, ideally for robotics or other complex electromechanical systems.
Driver development experience: Extensive experience taking a new sensor, actuator, or peripheral from datasheet to a robust software interface, including initialization, configuration, error handling, diagnostics, and recovery.
Hardware-level debugging skill: Experience bringing up custom electronics and root-causing issues across hardware, firmware, and drivers using schematics, datasheets, oscilloscopes, logic analyzers, debuggers, and protocol traces.
Experience building true real-time systems: you have a deep understanding of techniques to ensure real-time responsiveness and throughput in adversarial scenarios.
C and modern C++ fluency, with enough Python for tooling.
Bootloader and secure-boot experience.
Production test tooling you built for a factory floor.
Time-sensitive sensors: hardware triggering, timestamping, or clock synchronization (PTP) for cameras, IMUs, or encoders.
Experience with Rust.
Similar Jobs
What you need to know about the San Francisco Tech Scene
Key Facts About San Francisco Tech
- Number of Tech Workers: 365,500; 13.9% of overall workforce (2024 CompTIA survey)
- Major Tech Employers: Google, Apple, Salesforce, Meta
- Key Industries: Artificial intelligence, cloud computing, fintech, consumer technology, software
- Funding Landscape: $50.5 billion in venture capital funding in 2024 (Pitchbook)
- Notable Investors: Sequoia Capital, Andreessen Horowitz, Bessemer Venture Partners, Greylock Partners, Khosla Ventures, Kleiner Perkins
- Research Centers and Universities: Stanford University; University of California, Berkeley; University of San Francisco; Santa Clara University; Ames Research Center; Center for AI Safety; California Institute for Regenerative Medicine



