Senior Aerospace Cybersecurity Architect

We need to output HTML fragment with sections: h3 headings for sections present. Must not repeat job title. Must not include Job ID etc. Must include only sections with real content. Remove boilerplate: EEO, legal, navigation, cookie, application instructions. Also remove Physical Requirements? The instruction says include sections only when posting has real, specific content. Physical Requirements is present with details; we could include as a section? The allowed headings list includes: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Physical Requirements is not in list; we should not create a heading for it. We could fold that info into a paragraph maybe under Requirements? But the instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we can use those headings, but not required to use only those? It says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely we should only use those headings if content matches. Physical Requirements not in list, so we should not create a heading for it; maybe we can incorporate into a paragraph under Requirements or Qualifications? But it's not really a qualification. Could drop it? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we cannot drop Physical Requirements entirely. We need to include it somewhere. Perhaps we can include it as a

under a generic section? But we must use h3 for section headings; we could create a h3 with "Physical Requirements" even though not in the example list? The instruction says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive. However later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid other headings. So we could add a h3 for Physical Requirements. But the list of examples may be the intended set; but not explicitly prohibited. Safer to follow examples and only use those headings. Then we need to embed Physical Requirements info somewhere else, maybe under Responsibilities or Requirements? But that would be misrepresenting. However we could add a

after the sections without a heading? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose." It does not say we cannot have stray paragraphs without heading. It says use h3 for section headings. It doesn't forbid having paragraphs outside headings. But likely they expect sections with headings. However we could add a h3 "Physical Requirements" as it's a section with real content. I'd do that. Also need to include Pay Range And Compensation Package: we have salary range and benefits. So we need a Pay section (maybe also Benefits). The posting includes "Other benefits include health coverage, flexible PTO, a friendly work environment, plus extra fun perks!" So we can have Benefits section with that list. Pay section with salary range. Also need About the role? The role description paragraph at start could be About the role. Responsibilities: we have a big list. Requirements: we have Required Qualifications and Preferred Qualifications. Could split into Requirements (maybe required) and Qualifications (preferred). But we have both Required and Preferred. Could make Requirements section for required qualifications, and Qualifications section for preferred. Or combine. The instruction: prefer few substantive sections over many thin ones. Could combine Required and Preferred into Qualifications? But we have separate headings in examples: Requirements, Qualifications. We'll make Requirements for required qualifications, Qualifications for preferred. Skills: not explicitly listed; we could omit. Benefits: we have benefits. Pay: salary range. Schedule: not mentioned; omit. Also need to include maybe "About the role" from the introductory paragraph. Now we need to strip boilerplate: EEO Statement, Physical Requirements? we keep as section. Also remove "Physical Requirements" maybe we keep as section. Also remove "EEO Statement". Also remove navigation etc. Now produce HTML. Structure:

  About the role

  ...

  Responsibilities

  • ... each responsibility as li

  Requirements

  • ... required qualifications

  Qualifications

  • ... preferred qualifications

  Benefits

  • ... benefits

  Pay

  ... salary range

  Physical Requirements

  ... physical requirements text

  We must ensure we preserve all substantive information. Let's extract. About the role: The paragraph starting "At ICEYE, we design..." up to "As a trusted mission partner..." plus "Role Description The Aerospace Cybersecurity Architect is responsible..." Actually the role description includes responsibilities. But we can put About the role as the introductory paragraph before Responsibilities. Let's capture: "At ICEYE, we design, build and operate the largest fleet of Synthetic Aperture Radar (SAR) satellites in the world. Using advanced technology, our constellation collects topographical data about any location on Earth, day or night, through any weather conditions. Headquartered in Southern California, our customers are society’s heroes – intelligence professionals, warfighters, first responders, and scientific researchers. As a trusted mission partner, the United States and its allies depend on us for critical information when it matters most. Role Description The Aerospace Cybersecurity Architect is responsible for defining and advancing the security architecture for ICEYE US satellites, ground infrastructure, mission systems, communications, and supporting technologies throughout their lifecycle. This role serves as the primary cybersecurity architecture partner to aerospace software architecture, satellite operations, mission architecture, and engineering teams, ensuring cybersecurity requirements and security-by-design principles are incorporated into system and mission design from inception through operations. The Aerospace Cybersecurity Architect evaluates cyber risk across space, ground, communications, embedded, cloud, and operational technology environments and develops scalable, risk-informed architecture solutions to mitigate identified threats and vulnerabilities. The role provides technical cybersecurity guidance for system interfaces, trust boundaries, data flows, communications pathways, and mission-critical components while ensuring alignment with applicable customer, contractual, regulatory, and cybersecurity requirements. This position is critical to protecting ICEYE US mission capabilities and establishing resilient security architectures capable of supporting evolving operational and national security requirements." That's a lot; we can keep as About the role. Responsibilities: list bullet points from "Define, design, and maintain..." through "Support cybersecurity incident investigations..." We'll extract each sentence as li. Let's list responsibilities from the text: - Define, design, and maintain cybersecurity architectures for satellites, ground stations, mission systems, communications infrastructure, and supporting aerospace technologies. - Establish cybersecurity architecture principles, security patterns, technical requirements, and design standards for aerospace and mission environments. - Integrate cybersecurity requirements and security-by-design principles into system architecture, software development, DevSecOps, satellite operations, and mission design processes. - Perform architecture-level cybersecurity risk assessments, threat modeling, attack-surface analysis, and security design reviews for aerospace and mission systems. - Analyze system trust boundaries, interfaces, data flows, communications pathways, authentication mechanisms, and dependencies to identify cybersecurity risks and architecture weaknesses. - Identify and assess vulnerabilities affecting embedded systems, operational technology (OT), communications systems, ground infrastructure, mission applications, and supporting cloud environments. - Develop architecture-level security controls and mitigation strategies for new aerospace technologies, systems, interfaces, communications pathways, and mission capabilities. - Conduct and support technical security assessments, vulnerability assessments, penetration testing, architecture validation, and security testing of aerospace and mission systems. - Serve as the cybersecurity architecture partner to software architecture, satellite operations, IT, DevOps, engineering, and cybersecurity teams throughout system design and implementation. - Evaluate cybersecurity risks associated with APIs, external interconnections, third-party integrations, supply chain components, hardware, software, and supporting technologies. - Define and review security requirements for identity, authentication, authorization, encryption, key management, network segmentation, secure communications, logging, monitoring, and system resiliency. - Support implementation and technical validation of cybersecurity controls required by NIST, CMMC, RMF, customer security requirements, and applicable contractual obligations. - Develop and maintain security architecture documentation, system diagrams, trust-boundary diagrams, data-flow diagrams, threat models, technical risk assessments, and security design decisions. - Provide architecture-level recommendations for remediation of identified security deficiencies and ensure corrective actions align with the broader system and mission architecture. - Support cybersecurity incident investigations involving corporate, aerospace, mission, ground, or supporting systems and incorporate lessons learned into future architecture and security design improvements. That's all. Requirements (required qualifications): - Bachelor's degree in Cybersecurity, Computer Science, Computer Engineering, Electrical Engineering, Aerospace Engineering, Systems Engineering, or a related technical discipline, or equivalent relevant professional experience. - 5+ years of professional experience supporting aerospace, satellite, spacecraft, mission, or other complex aerospace engineering systems. - 4+ years of experience in cybersecurity architecture, security engineering, systems security engineering, or a related technical cybersecurity discipline. - Experience developing or reviewing security architectures for complex distributed systems, embedded platforms, cloud environments, operational technology, or mission-critical systems. - Experience performing cybersecurity risk assessments, threat modeling, architecture reviews, vulnerability assessments, or security testing of technical systems. - Working knowledge of cybersecurity frameworks and requirements such as NIST SP 800-171, NIST SP 800-53, NIST Risk Management Framework (RMF), CMMC, or comparable security requirements. - Experience integrating cybersecurity requirements into system architecture, software development, cloud environments, DevSecOps, embedded systems, infrastructure, or engineering lifecycle processes. - Ability to analyze complex technical architectures, interfaces, trust boundaries, data flows, communications pathways, and security controls and translate identified risks into actionable architecture and engineering requirements. - Ability to communicate technical cybersecurity risk and architecture recommendations to engineering, cybersecurity, program, and mission stakeholders. - Current U.S. Government security clearance or eligibility to obtain and maintain the level of clearance required for the position. Qualifications (preferred): - Experience designing or securing satellite, spacecraft, ground station, ground-segment, command-and-control, or mission-critical aerospace systems. - Knowledge of satellite communications, spacecraft command and control, telemetry, tracking and control, ground-segment architecture, or space-to-ground communications. - Experience with embedded systems, real-time operating systems, operational technology (OT), hardware security, or specialized aerospace engineering platforms. - Experience developing threat models for distributed, mission-critical, embedded, or cyber-physical systems. - Experience conducting or supporting penetration testing and security assessments of embedded systems, hardware, wireless technologies, RF communications, or mission systems. - Familiarity with secure systems engineering methodologies, systems engineering lifecycle processes, secure-by-design principles, and systems development lifecycle methodologies. - Experience supporting U.S. Government, Department of Defense, Intelligence Community, National Reconnaissance Office, or other national security programs. - Experience designing and evaluating cloud security architectures within AWS or Microsoft Azure environments. - Familiarity with Zero Trust architecture, identity-centric security, network segmentation, cryptographic protections, secure communications, key management, and resilient system design. - Familiarity with secure software development, CI/CD, infrastructure-as-code, containers, APIs, microservices, and DevSecOps practices. - Experience evaluating cybersecurity implications of third-party technologies, software supply chains, hardware components, APIs, and external system interconnections. - Relevant cybersecurity or security architecture certification such as CISSP, ISSAP, CCSP, CSSLP, SABSA, Security+, OSCP, or equivalent. Benefits