HIL Engineer

TYTAN Technologies

The PACE is fast. The expectations are high. The contribution matters. Working at TYTAN is more than a job, this is a mission. We push boundaries, think big, and hold ourselves to the highest standard. Our mission and values guide everything we do, and we're looking for people who are driven by ownership, embrace challenges, and are energized by meaningful work. If you're motivated by impact and thrive in dynamic environments, you'll fit right in.

At TYTAN, we aim to set a global standard in autonomous air defense with AI-driven, cost-efficient systems that counter unmanned aerial threats at scale. We protect people. We protect critical infrastructure. We protect European sovereignty.

We are seeking an experienced and hands-on HIL Engineer to join our Platform Team. Every software change at TYTAN should be proven on real hardware before it flies. In this role you build closed-loop hardware-in-the-loop testing: real flight hardware flying simulated missions in real time, on a rig fleet that our autonomy, perception and systems teams use on every change, on their own.

Your roadmap to make an impact

• Closed-loop HIL: Run physics, sensor and target simulation in real time against real flight hardware. Inject simulated IMU, GNSS, camera and other sensor data at the interface the hardware expects, close the loop on actuator commands, and keep latency, jitter and time synchronisation within budget, so a simulated flight on the rig behaves like a real one

• Fault injection: Sensor failures, GNSS denial and spoofing, link loss, bus errors and power faults, reproducible on demand

• Rig fleet: Rigs provisioned as code, automated deployment of firmware and software builds to the hardware under test, remote power and reset control, health monitoring and self-recovery

• Orchestration: Reservation and scheduling of rigs, queuing across CI pipelines and parallel execution across heterogeneous rigs and hardware revisions

• Test framework: Fixtures for devices, instruments and simulators, so that a domain engineer writes a HIL test as easily as a unit test, and the same scenario runs in SIL and HIL

• CI/CD: Merge-gating regression suites, nightly and long-running mission suites, flaky test detection and quarantine

• Results: Structured result storage, dashboards and trend analysis across software versions, hardware revisions and scenarios, traceable to requirements

• HIL as a product: Your users are the engineers who validate their code on it. Availability and time to result are your metrics; you build the systems, they write their scenarios

• Triage: Separate infrastructure faults from product bugs and route them to the owning team, also in restricted and air-gapped lab networks