About the role
About 1X We’re building humanoid robots that work in home - doing the chores, handling the tasks, and giving people their time back. Simple, but it’s not. To do this right, we have to solve robotics, AI, manufacturing - at the same time, at scale, in a form factor that has to be safe enough to live with your family. If you’re inspired by this, you’ll thrive here. We’ve been at this since 2014 and we’re at the point where the hard problems are behind us and the hard work is in front of us. NEO is our flagship - a home robot designed to move, learn, and operate in the real world alongside real people. We’re not demoing it - we’re shipping it. We’re excited to meet you, if this excites you. If you’ve spent your career working on problems that matter and want to see them actually reach the world - this is that moment. We’re scaling, we’re hiring with intention, and we need people who want to build something that will genuinely change how humans spend their time - safely creating abundance for all.
About
the Team The Foundations team builds and owns the core C++ infrastructure that NEO’s entire stack runs on—sensor pipelines, motor control interfaces, inter-process communication, and the foundational libraries that ship on every robot. Our code executes thousands of times per second on hardware moving through the real world, and its correctness and performance directly determines what every other team can build and ship. If you want to work on the systems layer that makes physical AI possible at scale, this is that team. Your Charter Own the foundational C++ infrastructure that NEO’s brain and nervous system depend on ensuring it is fast, deterministic, and reliable as we scale from prototypes to thousands of robots in homes and warehouses. This is critical-path work: the latency, correctness, and maintainability of sensor pipelines, motor control loops, and IPC layers directly determines what the perception, planning, and controls teams can ship. Every clean interface introduced, every regression caught, and every millisecond saved here multiplies across every robot we deploy. Key Outcomes Own and continuously improve real-time C++ infrastructure: sensor pipelines, motor control interfaces, deterministic scheduling such that dependent teams can build on it without hitting foundational performance or reliability blockers Establish performance as a measurable standard: deliver benchmarking, flamegraph tooling, and regression tracking that catches latency or throughput drift before it reaches production Build the IPC and serialization layer connecting perception, planning, and actuation: lock-free queues, memory pools, shared-memory buffers with clean interfaces that other engineers trust and build on Ship foundational libraries that run reliably on thousands of robots in homes and warehouses, not just prototypes in the lab Key Competencies Thinks in cycles, cache lines, and budgets designing systems around latency, memory, and bandwidth constraints and can explain exactly where time and memory go under load Deep Linux and systems fluency debugging across toolchain, ABI, kernel interfaces, and cross-compilation; uses profiling, tracing, and assembly inspection as everyday tools, not last resorts Interface-first thinker writing code with clear contracts, minimal dependencies, and obvious correctness that other engineers reach for when building higher-level systems Reliability-oriented under pressure shipping real-time systems where failure has physical consequences, and treats deterministic behavior and clean failure modes as engineering
