At Glydways, the Test Engineering team is responsible for proving that our integrated autonomous transit system is safe, reliable, and ready for real-world operation.
We work across autonomy, vehicle hardware, embedded software, systems engineering, safety, infrastructure, operations, quality, and deployment teams. Our work spans simulation, software-based test environments, Hardware-in-the-Loop (HIL) testing, lab testing, vehicle testing, test-track operations, and project-site commissioning.
This role focuses on Hardware-in-the-Loop (HIL) testing and the test environments that allow Glydways to exercise real controllers, software, networks, interfaces, and failure modes before they reach vehicles, the test track, or customer sites.
We are seeking a System Test Engineer who can build, operate, and improve Hardware-in-the-Loop (HIL) test capabilities for a complex autonomous transit system.
This role is ideal for someone who is comfortable at the boundary between test engineering, embedded systems, controls, software, hardware interfaces, automation, and data analysis. You will help ensure that system behavior, safety functions, regressions, and edge cases can be tested earlier, more often, and more repeatedly through high-quality HIL environments.
You will develop HIL test procedures, automate regression tests, manage test configurations and data, analyze results, and improve the benches, simulators, harnesses, dashboards, and workflows that make system testing more scalable.
We are open to candidates across a range of experience levels, from strong mid-level engineers through staff-level technical leaders. Scope and title will be calibrated based on experience. More senior candidates will be expected to own larger HIL capabilities, improve test architecture and process, mentor others, and represent test evidence in readiness and release discussions.
This role will include hands-on work with test benches, controllers, networks, lab equipment, vehicles, and Glydways test facilities. Some travel or on-site presence should be expected for integration campaigns, test environment bring-up, and major release demonstrations.