Mission Security Engineer
US$162,000 – US$198,000 / yr base salary
Posted 2 Oct 2026
BranchFactor Summary
The original posting with the fluff stripped out
- Expected experience
- 1+ yrs
- Management level
- Individual contributor
- Employment
- On-Site
- Contract
- Full-time
| Base salary | US$162,000 – US$198,000 / yr |
|---|
Field of studyAerospace, Computer Science, Cybersecurity, Systems Engineering (or related)
Study levelBachelor's or higher
Spacecraft represent the most pressing unmet need across the entire aerospace industry. As more launch vehicles come online and the cost to orbit decreases, more companies launching payloads to space continue to emerge.
For the first time in history, this influx of payload companies combined with reduced launch costs has resulted in a massive increase in need for commercial spacecraft platforms, known as satellite buses. These buses hold the payloads of our customers and are flown on launch vehicles.
Apex manufactures these satellite buses at scale using a combination of software, vertical integration, and hardware that is designed for manufacturing. Our spacecraft enable the future of society: ranging from earth observation to communications and more.
We’d love for you to join us on our mission of providing humankind access to the galaxy beyond our planet.
About the Role
In this position, you will own or contribute to the authorization posture of two systems: a space vehicle and a classified cloud mission operations environment. You will contribute to cyber engineering and produce RMF authorization documentation, build and sustain authorization packages, own the plan of action and milestones day to day, and run continuous monitoring. This is mission systems work throughout, not traditional enterprise IT security.
We are open to candidates from ISSE, SSE, ISSM, or ISSO backgrounds, and are hiring across levels: from new and recent graduates through senior engineering, officer, and manager experience.
**Responsibilities:
**May include any or all of the following:
Authorization Ownership
-
Build and sustain authorization packages for both boundaries: system description, boundary definition, categorization, control selection and tailoring rationale, implementation statements, assessment coordination, and the residual risk picture carried to the AO.
-
Get assessors engaged early on our evidence-generation approach so generated artifacts are trusted before a package depends on them.
-
Own the POA&M.
-
Maintain the authorization system of record (eMASS or equivalent).
Space Vehicle Segment
-
Own the authorization boundary determination for the flight segment and the rationale that survives assessor scrutiny.
-
Categorize under CNSSI 1253 and defend overlay selection, treating the Space Platform Overlay as the starting place it is rather than a finished answer — pushing back where our onboard security capability exceeds what the published tailoring assumes.