Torc Robotics
Quality Test Engineer, II
About this role
Torc is seeking a Quality Test Engineer II in Fort Worth to lead autonomous vehicle software testing and validation. You'll design and execute comprehensive test plans, perform root cause analysis, develop testing infrastructure, and contribute to full-stack software development using C++ and scripting languages in a Linux environment.
What you'll do
- Generate, execute, and analyze vehicle test plans to identify system limitations and collect performance data
- Perform root cause analysis on defects and performance issues, recommending solutions to engineering teams
- Design and deploy instrumentation and data capture infrastructure to support test requirements
- Maintain verification and validation reports tracking vehicle-level system performance against requirements
- Develop C++ and scripting-based software for testing automation, data acquisition, and CI/CD pipelines
- Conduct on-road testing in autonomous vehicles as observer/annotator, with up to 25% domestic and international travel
What they're looking for
- Vehicle software testing and test plan design
- C++ and scripting languages (Python, Bash, etc.)
- Linux development environment
- Data analysis and root cause analysis
- CI/CD pipeline development
- Autonomous vehicle systems knowledge
- Lean-Agile methodologies
- Technical reporting and documentation
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.
Torc Robotics
Torc Robotics develops autonomous driving software and systems for trucks. The company is hiring systems engineers, software engineers, and test automation specialists to build validation frameworks, integration environments, and web applications that ensure the reliability and quality of their autonomous vehicle technology.
- Website
- torcrobotics.com
Likely interview questions
- Describe your experience designing and executing comprehensive test plans for software systems. How do you approach identifying edge cases and failure modes?
- Tell us about a time you performed root cause analysis on a complex technical issue. What was your methodology and how did you communicate findings?