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.
Requirements: What you bring
B.Sc. or M.Sc. in aerospace, mechanical, electrical, or systems engineering, or equivalent demonstrated practice.
6+ years in systems engineering or integration on aircraft, UAV, spacecraft, or comparably complex electromechanical programs - including at least one carried from requirements through test.
Working command of ARP4754A development assurance and ARP4761 safety assessment - you have written FHAs and derived requirements, not just read about them.
Hands-on experience with requirements management tools such as DOORS, Jama, or Polarion, and a record of building traceability that survives external scrutiny.
Demonstrated ownership of interface control across mechanical, electrical, and software boundaries: ICDs, signal lists, connector-level definition, and disciplined change control.
Experience planning and executing ground or flight test campaigns - test plans, procedures, instrumentation requirements, and rigorous post-test reconciliation against requirements.
Enough fluency in structural dynamics, vibration, or acoustics to interrogate a noise requirement and recognize when a subsystem's verification evidence does not actually close it.
Clear written English - your requirements, interface documents, and verification reports are the program's backbone and, eventually, its certification record.
Even better if
Systems or integration experience on an eVTOL, UAM, or other novel VTOL aircraft program.
Direct exposure to certification with EASA, FAA, or military airworthiness authorities, including oversight of DO-178C/DO-254 software and hardware development.
Experience with MBSE methods and tools (SysML in Cameo or equivalent) for architecture and interface modeling.
Background integrating high-power electric systems, with the EMI/EMC and thermal discipline that comes with them.
Experience at an early-stage company where you wrote the first integration plan from a blank page and lived with its consequences.
This position is open to all candidates.