Similar Jobs
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 RoleOur robots run real-time control, GPU inference, SLAM, camera pipelines, teleoperation, and networking on a compute platform we design ourselves: custom carrier boards, MCUs, and the sensor architecture around them. As a Systems Software Engineer focused on the OS, you'll own the OS layer and the IPC layer that connects it all: the kernel and its real-time behavior, scheduling, memory management, user-space drivers, time synchronization, and the shared-memory transport that moves data between processes with minimal copies and bounded latency. You'll also own how the system operates unattended: boot, OTA updates with rollback, service supervision, crash capture, and health monitoring.
Your software is the layer every other team builds on, and it ships on every robot. When new hardware arrives, you'll bring it up alongside electrical, controls, and robotics engineers.
ResponsibilitiesSystem architecture: Design and implement the core systems that every robotics application depends on, including on-device and remote networking, IPC, scheduling, synchronization, and resource management.
Understand and optimize system performance: Profile, optimize, and understand the tradeoffs between CPU utilization, latency, throughput, memory usage, and scheduling behavior across the robotics software stack.
Design for reliability: Build diagnostics, health monitoring, and fault-handling systems that improve robot robustness and serviceability.
Debug across the stack: Investigate issues spanning hardware, firmware, and robotics software.
Deep Linux internals: 3+ years working at the OS level. Schedulers, memory, filesystems, and the kernel/userspace boundary.
Modern C++: Strong proficiency developing production-quality C++ software for embedded or real-time systems.
Systems programming: Strong understanding of Linux systems programming, including threading, synchronization, memory management, IPC, scheduling, and performance optimization, along with experience with the embedded Linux stack, including U-Boot, device trees, kernel configuration, DMA, and Buildroot or Yocto.
Hardware/software debugging: Comfortable reading schematics, probing hardware with oscilloscopes and logic analyzers, and debugging issues that span electrical, firmware, and software boundaries. Experience using tools like gdb, strace, ltrace and others to understand system behavior.
Experience with Embedded Linux platform work: U-Boot, device trees, kernel config, DMA and the like.
Experience with secure boot, firmware update systems, or OTA infrastructure.
Experience with microcontrollers, device drivers, peripherals, board support packages, and custom hardware bring-up.
Experience with Rust is a plus.
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



