1X
Software Engineer - Simulation
About this role
1X is hiring a Software Engineer to build and maintain simulation environments that accelerate robot learning for NEO, their humanoid home robot. You'll create physically realistic virtual worlds, scale synthetic data production, and close the sim-to-real gap so policies trained in simulation transfer reliably to hardware.
What you'll do
- Design and maintain diverse, physically realistic simulation environments for NEO robot learning and policy development
- Reduce sim-to-real gap through domain randomization, calibration, and environment fidelity improvements
- Scale synthetic data production infrastructure to meet AI team training needs efficiently
- Enable hardware team to prototype and virtually test new robot designs before manufacturing
- Optimize physics and rendering pipelines for maximum simulation throughput
- Build tested, maintainable simulation infrastructure that other teams depend on
What they're looking for
- Python or C++ programming (4+ years)
- Robotics simulators (MuJoCo, PyBullet, Isaac Sim, or equivalent)
- Physics simulation and contact dynamics tuning
- OpenGL rendering pipeline optimization
- Sim-to-real transfer and domain randomization techniques
- Rigorous testing practices for simulation stacks
- Robotics calibration algorithms (extrinsic/intrinsic)
- Procedural environment generation
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 robotics simulator you've built or significantly improved. What physics phenomena were hardest to get right, and how did you validate correctness?
- Describe a time you had to balance simulation fidelity against computational performance. How did you decide what to optimize and what to sacrifice?