Skip to main content

Contoro

Robotics Engineer Intern - Test & Validation

Austin, TXfulltimeinternAdded today

About this role

Contoro Robotics seeks a Test & Validation Intern to execute structured test procedures on autonomous warehouse robots, record detailed results, and provide critical feedback to engineering teams. You'll work hands-on with real robots and test environments, ensuring product reliability before deployment to customer sites.

What you'll do

  • Execute predefined test procedures across multiple test levels, from unit to full simulated site conditions
  • Record and report test results with failure modes, timestamps, and environmental data
  • Set up and tear down test environments per documented runbooks, including conveyor and sensor configuration
  • Flag test failures and route them to feature owners with supporting logs, video, and metrics
  • Maintain test result dashboards for Systems, Automation, and Operations team visibility
  • Track regression by re-running tests after code or hardware changes, and document runbook gaps

What they're looking for

  • Test execution and quality assurance
  • Technical documentation and communication
  • Linux command line basics
  • Data logging and analysis
  • ROS or robotic systems experience (preferred)
  • Attention to detail and precision
  • Problem-solving and troubleshooting
Apply on the employer's site

Opens the official application on the employer’s site. No login required.

Contoro

Contoro builds autonomous warehouse automation robots that unload boxes from trailers and containers using computer vision, motion planning, and robotic manipulation. The company is hiring robotics engineers, software engineers, data engineers, and ML specialists to develop perception systems, autonomous control software, analytics infrastructure, and motion planning algorithms for production robot fleets.

View all jobs at Contoro

Likely interview questions

  • Describe a time when you had to follow detailed procedures precisely—what made you successful at it?
  • How would you handle discovering a test failure that you weren't sure how to categorize or report?