1X
Software Engineer - Cloud and Infrastructure
About this role
1X is seeking a senior software engineer to lead the cloud and infrastructure systems that connect humanoid robots to global operations. You'll design and scale backend systems, customer-facing applications, and internal platforms that enable 1X to deploy and manage thousands of robots worldwide.
What you'll do
- Design and ship scalable backend systems for real-time robot control, data pipelines, and fleet monitoring
- Develop customer-facing applications for robot control, monitoring, and management
- Build internal platforms supporting logistics, manufacturing, and service operations
- Set technical direction and establish reliability and performance standards for the team
- Lead architecture decisions and mentor engineers through code review and technical guidance
- Own end-to-end systems from hardware-software integration to production deployment
What they're looking for
- Distributed systems and cloud architecture (AWS or GCP)
- Python, Go, or C++
- Real-time data pipelines and APIs
- Systems design for scalability and performance
- Team leadership and technical mentorship
- Robotics, IoT, or real-time control systems (preferred)
- Fleet management and OTA deployment (preferred)
- Hardware-software integration experience
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
1X
1X builds humanoid robots for home use, with its NEO robot requiring sophisticated hardware, firmware, and cloud systems. The company is hiring across compliance testing, audio systems, embedded firmware, cloud platform development, and supplier engineering to bring its robots to production and scale.
View all jobs at 1XLikely interview questions
- Walk us through a distributed system you've designed that scaled from hundreds to tens of thousands of users or devices—what were the critical failure modes you anticipated, and how did you simplify the architecture as it grew?
- Describe your experience designing real-time backends or data pipelines. What were the latency and consistency trade-offs you had to make, and how did you validate your choices?