Skip to main content

Regent

Autonomy Test & Integration Engineer

North Kingstown, Rhode Island, USAfulltimemidAdded today

About this role

Join REGENT as an Autonomy Test & Integration Engineer to build and operate the test infrastructure for a cutting-edge maritime perception system. You'll split time between field deployments on water—setting up sensors and collecting real-world data—and shore-based work developing replay systems, calibration tools, and integration pipelines that enable rapid iteration on autonomous vessel detection.

What you'll do

  • Plan and execute field perception tests on water, including sensor setup, calibration, and data collection against live vessel traffic
  • Integrate software changes onto real vehicle hardware and troubleshoot deployment issues across multiple platforms
  • Develop and maintain hardware-in-the-loop and data-replay infrastructure for bench testing
  • Design test scenarios for autonomy algorithms and oversee their validation
  • Review and approve software changes through the full pipeline from development to vehicle deployment
  • Monitor and maintain perception system reliability across all supported platforms

What they're looking for

  • Robotics and autonomy system development
  • Hardware-in-the-loop and data-replay testing
  • Field sensor deployment and calibration
  • C/C++ for embedded/real-time systems
  • Python scripting
  • Linux system administration
  • Software integration and testing
  • ITAR compliance (U.S. person requirement)
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.

Regent

Regent develops innovative Seaglider vehicles designed for sustainable coastal transit. The company is hiring embedded systems software engineers and chief engineers to support vehicle development, integration, and certification efforts.

View all jobs at Regent

Likely interview questions

  • Describe your most complex field deployment experience—what went wrong, and how did you adapt in real time?
  • Walk us through your process for testing software changes before they go onto real hardware. How do you decide when something is ready?