Systems Integration Engineer

Required Systems Integration Engineer
Why this role exists
On most aircraft programs, systems engineering keeps the weight, power, and safety budgets honest. There is a fourth budget - noise - and it is the one the company lives or dies by, flowed down through every interface, mount, harness, and duty cycle on the vehicle. This role exists because a roughly 4 acoustic advantage is an architecture claim until someone turns it into a closed set of vehicle-level requirements, traces every one to a subsystem owner, and walks the verification evidence onto the flight line.
What you'll own:
Own requirements flow-down from vehicle-level acoustic, performance, and safety targets to subsystem specifications under an ARP4754A-aligned development process.
Author and control interface definitions across structures, propulsion, avionics, and software - including the vibration, isolation, and acoustic constraints most ICDs never carry.
Build and maintain the vehicle requirements and verification database with full bidirectional traceability from stakeholder need to test evidence, and defend it in audits.
Plan and run integration campaigns on the systems bench and iron bird: power-on sequencing, interface checkout, fault injection, and end-to-end functional verification before anything flies.
Lead ground and flight test campaigns as the vehicle-level V&V owner - define test objectives, success criteria, and instrumentation requirements, then reconcile measured results against requirements line by line.
Chair cross-subsystem integration reviews and arbitrate trades where a decibel saved in one subsystem costs mass, power, or schedule in another.
Conduct safety assessment work - FHA, PSSA, FMEA, and fault trees per ARP4761 - jointly with subsystem leads, and track every derived requirement to closure.
Drive gated design reviews from SRR through test readiness with hard closure metrics: verification status, open interface items, and integration risk burn-down.