How to apply for Senior Security Engineer

About Muon Space

Muon Space builds Earth-sensing satellite technology aimed at climate action. The company operates at the intersection of aerospace and cybersecurity, which means security work directly affects satellites, ground systems, and mission networks. This is a chance to work on security problems that are rare outside the space industry.

About the role

This senior security engineer role owns security across satellites, ground systems, mission networks, and cloud infrastructure. You will secure flight software, embedded systems, command-and-control interfaces, and communication links, while supporting NIST 800-171 and ITAR/EAR compliance. The work is hands-on and independent, with direct impact on how Muon protects its missions.

A typical day

A typical day could include reviewing code or architecture for a flight software component, tuning firewall or IDS rules for a mission network, and investigating a security alert tied to ground systems. You would also work with aerospace, software, and compliance teams to keep missions aligned with NIST 800-171 and ITAR/EAR requirements. Because the role is independent, you would set much of your own priorities across satellite, network, and cloud security tasks.

Who Muon Space is looking for

• Has deep experience securing embedded systems, flight software, or satellite command-and-control interfaces, not just enterprise IT.
• Can design and implement security controls for ground systems, communication links, and mission networks, including firewall management, IDS/IPS tuning, and network segmentation.
• Is comfortable with threat modeling, code reviews, vulnerability management, and security testing for mission systems.
• Has worked in regulated environments such as NIST 800-171, ITAR, or EAR, and can operate independently across multiple security domains.

Tips for this application

• Highlight any direct experience with satellite, aerospace, or embedded systems security. If you lack satellite experience, describe comparable work on OT, ICS, or other constrained systems.
• Name specific frameworks and standards you have implemented, especially NIST 800-171, ITAR, or EAR. Vague compliance claims will not help.
• Describe concrete examples of securing command-and-control interfaces, communication links, or ground systems. Use technical detail, not summaries.
• Show you can work independently. The role says the ideal candidate can operate independently, so give examples of projects you owned end to end.
• Address the work location clearly. The job allows on-site, hybrid, or remote from an approved U.S. location, so state your location and preference in your application.

What to cover in your cover letter

Explain why aerospace security is the core of your interest, not a side topic. Describe a specific project where you secured embedded, flight, or mission systems. Show how you have handled NIST 800-171, ITAR, or EAR requirements in practice. State your ability to work independently across satellite, ground, network, and cloud security domains.

Research before applying

• Review Muon Space's satellite programs and Earth-sensing technology to understand what systems you would be securing.
• Read the public details of NIST 800-171 and ITAR/EAR to prepare for compliance questions. Know the difference between them.
• Look up common security challenges in aerospace, such as ground segment security, telemetry links, and supply chain risks for flight software.
• Check whether Muon has published any security or engineering blog posts, talks, or documentation about their mission architecture.

Likely interview topics

Based on the job description, expect questions about:

• How you would design cybersecurity controls for a satellite's command-and-control interface and its communication links.
• Your approach to threat modeling and code review for flight software or other embedded systems.
• A time you detected and responded to a threat on a mission network or similarly constrained network.
• How you have implemented or supported NIST 800-171, ITAR, or EAR compliance in a previous role.
• How you manage firewall rules, IDS/IPS tuning, and network segmentation across operational technology and cloud environments.

Common mistakes to avoid

• Treating this as a standard IT security role. The job is aerospace security first, so generic enterprise security experience alone is not enough.
• Claiming compliance experience without naming the framework, the controls you implemented, or your specific role in audits.
• Ignoring the satellite and embedded systems side of the role and focusing only on cloud or network security.