Engineering Roles

You’ll stand up the test infrastructure: automated frameworks in Python that exercise a system the way the mission will, regression suites wired into CI so a change that breaks a signal chain surfaces in an hour rather than at the range, and hardware-in-the-loop rigs that put real front-ends, processors, and timing into the loop while the rest of the world stays synthetic and repeatable. You’ll work in RF chambers, acoustic tanks, and on prototype hardware with oscilloscopes, spectrum analyzers, and protocol analyzers, and you’ll write the data-reduction pipelines that turn a few terabytes of instrumented runs into a defensible answer. Sometimes you’ll characterize the system against live signals you can’t discuss.
You’ll define the success criteria for a given capability and design experiments that stress the system under controlled adversity. When something behaves differently in the field than in the lab, you’ll lead the investigation, isolating whether the anomaly lives in the algorithm, the firmware, the integration, or the environment, and feeding that back into the next build. You’ll go to the range, to sea, and into the enclave where the system actually runs.