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 Firmware team owns the embedded software layer that powers every hardware subsystem of our humanoid robot from distributed communication bus architecture and power management to actuator and motor drive control. We sit at the intersection of hardware and software, and our work is directly on the critical path to every product milestone: without reliable firmware, the robot cannot move, charge, or operate safely. If you want to build the foundational software for a new category of physical AI, this is where that work happens.

Your Charter

Own the firmware layer across one or more of the robot’s core hardware subsystems—ensuring embedded software that is robust, safe, and maintainable across prototype and production platforms. As one of the first companies building general-purpose humanoid robots at scale, firmware quality is non-negotiable: it determines whether the robot operates safely in uncontrolled environments, whether hardware brings up on schedule, and whether the team can move fast as the system grows to 20+ distributed embedded nodes.

Key Outcomes

• Develop and maintain charger firmware controlling AC-DC power conversion stages,
  including power factor correction and isolated DC-DC conversion topologies

• Implement charge profile management for multi-series lithium-ion packs: constant-
  current, constant-voltage, and taper phases with cell-chemistry-appropriate voltage and
  current limits

• Architect the charger-to-BMS communication interface over CAN or similar embedded bus, coordinating charge current requests, pack voltage feedback, temperature limits, and fault signaling between the two subsystems