Skip to main content

1X

Test Engineer

San Carlos, CA$119.8k–$179.6kfulltimemidAdded 1 month ago

About this role

1X is seeking a Test Engineer to build validation infrastructure and automation frameworks for NEO, their humanoid home robot. You'll develop test systems across hardware, firmware, and software to ensure the robot performs safely and reliably in real-world conditions.

What you'll do

  • Develop and maintain automated test frameworks to improve validation coverage across hardware, firmware, and software
  • Build hardware-in-the-loop and system-level validation environments that simulate real-world operating conditions
  • Identify, reproduce, and help resolve complex multidisciplinary failures before product deployment
  • Maintain traceability between product requirements, test execution, and validation results
  • Generate performance, reliability, and characterization data to inform engineering decisions
  • Debug and perform root-cause analysis on complex system failures

What they're looking for

  • Python and/or C++ programming
  • Embedded systems and microcontroller experience
  • Communication protocols (CAN, SPI, I2C, UART)
  • Laboratory equipment operation (oscilloscopes, logic analyzers, multimeters)
  • Git and version control systems
  • Systems-level thinking across hardware and software
  • Linux and real-time operating systems
  • Hardware-in-the-loop testing
Apply with Autofill

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 1X

Likely interview questions

  • Describe a complex multidisciplinary failure you debugged across hardware, firmware, and software. How did you identify root cause and what data did you use to validate your fix?
  • Walk us through how you've built or maintained an automated test framework. What languages did you use, and how did you handle the challenge of testing across different system layers?
Unlock all 7 questions free — and practice them live →