Posting record
Open 11+ days
- Destinusgroup's site dates the posting
- Ghostless first sees this listing
- Last checked: still up
How we know
It hasn't been reposted, listed twice, or left up unusually long, and the posting doesn't say it's a talent pool.
Ghostless records the day it first sees a posting, so a repost can't reset its age. This one was already up when Ghostless started tracking Destinusgroup, so its true age is longer.
Last checked Nov 4, 2026.
How well do you match?
See how much of this posting your resume shows, and what it's missing.
Upload your resumeWhat the posting discloses
Not stated: Pay, real vacancy, AI screening.
Why these three
Ontario requires postings from employers with 25 or more staff to state the pay, whether the vacancy exists, and whether AI screens applicants.
Some employers add pay only on their own site. Check the original posting before you rule it out.
Skills mentioned
About the role
The Destinus engineering team is seeking a Systems Engineer to lead the system-level definition and technical development of our effector programmes. This role sits at the centre of the development effort – bridging operational requirements and technical execution across propulsion, structures, avionics, and seeker.
The ideal candidate brings a defence systems background and understands the full development lifecycle of a guided effector – from ConOps and requirements through subsystem design, integration, and qualification. They are technically credible across multiple domains, rigorous in their systems thinking, and effective at driving alignment across disciplinary teams.
What You’ll Do
· Define and own system-level requirements for effector programmes – capturing operational needs, translating them into technical requirements, and maintaining traceability from ConOps through to subsystem specifications
· Develop and maintain ConOps and operational scenario definitions; work with the customer and programme stakeholders to ensure operational intent is correctly reflected in the system design
· Define and manage technical interfaces between subsystems (propulsion, warhead/pyrotechnics, structures, avionics, guidance, and GSE); own the ICD and IRS documentation
· Lead trade studies and make-or-buy analyses to identify the best technical and commercial solutions at system and subsystem level
· Identify and track critical components and subsystems; define mitigation strategies for technical risk and drive resolution through the engineering team
· Lead or support system design reviews (SRR, PDR, CDR) and prepare the associated technical baseline documentation
· Coordinate system integration activities across propulsion, structures, avionics, and external teams; ensure interfaces are closed and integration milestones are met
· Support verification and validation planning; define the V&V approach at system level and ensure it flows down to subsystem test plans
Requirements
What You’ll Need
· Bachelor’s or Master’s degree in Aerospace, Systems, Mechanical, or Electrical Engineering, or a related technical field
· 5–8 years of systems engineering experience on defence or weapons system programmes – rockets, missiles, or guided weapons are a strong advantage; a background in aerospace or space launcher development is also suitable
· Proven experience defining and managing system requirements and interfaces across multi-disciplinary teams in a defence acquisition or development environment
· Hands-on experience with ConOps development, trade studies, and make-or-buy decision frameworks
· Familiarity with system design review processes (SRR, PDR, CDR) and the associated technical documentation
· Experience with V&V planning and requirements traceability; exposure to relevant standards (e.g. ARP4754, DEF STAN, MIL-STD, or equivalent) is an advantage
· Solid understanding of at least one key effector subsystem domain – propulsion, structures, avionics, or guidance – with the breadth to work credibly across all of them
· Structured, rigorous, and delivery-focused – able to drive technical decisions without getting lost in analysis
· Fluent in English; German is an advantage
Something wrong with this posting?