Apptronik
Robotics Test Engineer
About this role
Apptronik seeks a Robotics Test Engineer to develop and maintain automated integration tests for Apollo, a humanoid robot. You'll write pytest-based tests, investigate defects, expand regression coverage, and collaborate with senior engineers to ensure software quality at scale.
What you'll do
- Write automated integration and conformance tests in pytest aligned with software requirements and release gates
- Investigate CI failures and defects alongside senior engineers using debugging tools and log analysis
- Convert discovered defects into permanent regression tests to prevent future escapes
- Execute and maintain test suites on hardware-in-the-loop benches and report results
- Maintain test suite health by triaging flaky tests and updating fixtures as the stack evolves
- Engage with requirements documents and raise clarifying questions to Systems Engineering
What they're looking for
- Python programming with ability to write clean test code
- pytest or equivalent test framework (fixtures, parameterization, organization)
- Linux command line fluency and basic shell scripting
- Git fundamentals and pull request workflows
- Debugging and root-cause analysis
- Technical communication and documentation
- C++ code comprehension
- Learning agility in robotics and verification engineering
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.
Apptronik
Apptronik builds Apollo, a humanoid robot designed for manufacturing, logistics, and other industrial applications. The company is hiring firmware engineers, software engineers, controls specialists, and networking engineers to develop embedded systems, motor control, motion pipelines, and wireless connectivity that power the robot's dexterous manipulation and autonomous operation.
- Website
- apptronik.com
Likely interview questions
- Walk us through your experience writing automated tests in pytest. How have you approached designing test fixtures and parameterization to keep tests maintainable as requirements evolve?
- Tell us about a time you debugged a flaky or intermittent test failure. What tools and techniques did you use, and how did you determine whether the problem was in the test or the system under test?