Senior Cybersecurity Architect

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Castelion" then "Senior Cybersecurity Architect" title then description. We should not repeat job title as heading. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. We have content: About Castelion (company description) could be "About the role"? Actually "About Castelion" is company overview. Could map to "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those headings if content matches. We have: - About Castelion: description of company mission. Could be placed under "About the role"? Might be better as "About the role" includes role description. But we have a paragraph describing the role: "We are seeking a Senior Cybersecurity Architect to lead the design and implementation..." That's role overview. So we can put that under "About the role". The company description could be omitted? But we must preserve ALL substantive information; we cannot drop company description. However we could include it under "About the role" as part of role description? Or we could add a separate section like "About Castelion" but not in allowed headings. The instruction says use those headings for section headings; but does not forbid other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we need to fit all content into those sections. We can put company overview under "About the role" as introductory paragraph. Responsibilities: we have a list. Requirements: we have "Required Qualifications". Could map to "Requirements" or "Qualifications". The instruction lists both Requirements and Qualifications as possible headings. We need to decide. Usually "Requirements" for required qualifications, "Qualifications" for preferred qualifications. We'll do that. Skills: maybe we can include technical skills under Skills? But we already have them in Required Qualifications. Could combine. Benefits: we have "All employees receive access to comprehensive medical, vision, and dental insurance, and the company offers four weeks of paid time off per year." Also "All employees are granted long-term stock incentives as part of their employment." That's benefits. Pay: not specified; we should not create Pay section unless posting actually states them. No pay info, so omit. Schedule: not specified; omit. We also have ITAR Requirements and EEO statements; those are boilerplate to remove. Also "Employment with Castelion is governed..." is EEO boilerplate; remove. We also have "Based in our Torrance, CA HQ, you'll lead efforts..." that's part of role description. We need to preserve all substantive information: company mission, role overview, responsibilities, required qualifications, preferred qualifications, benefits (medical, vision, dental, PTO, stock incentives), location (Torrance, CA HQ, occasional travel 5-10% to TX/NM), maybe mention "hands-on role". Also mention "Senior Cybersecurity Architect" title? Not as heading but we can include in opening paragraph. We must not repeat job title as heading; we can include it in paragraph. We must not include cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So remove ITAR Requirements paragraph? It's not exactly EEO but it's a requirement for eligibility; it's substantive? It's a requirement for employment (citizenship etc). That is substantive; we should keep it. It's not boilerplate? It's a legal requirement but it's part of posting. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. ITAR requirement is legal but maybe considered boilerplate? It's a specific requirement for the role (citizenship). I'd keep it under Requirements or Qualifications as a bullet. Also "All employees are granted long-term stock incentives as part of their employment as Castelion." That's benefits. Now craft HTML. Structure:

About the role

Castelion is bringing a new approach to defense development and production...

plus role overview. Better to split: first paragraph about Castelion mission, second paragraph about role. Then

Responsibilities

• ... each responsibility. Then

  Requirements

  • ... required qualifications. Then

    Qualifications

    • ... preferred qualifications. Then

      Benefits

      • ... medical, vision, dental insurance; four weeks PTO; long-term stock incentives. We might also include location and travel under About the role or Responsibilities? Could add a paragraph after responsibilities: "Based in our Torrance, CA HQ, you'll lead efforts..." but that's more about role. Could include in About the role paragraph. Let's extract specifics: About Castelion paragraph: "Castelion is bringing a new approach to defense development and production: one that focuses on short, iterative design cycles, rapid testing in development, and modern commercial manufacturing strategies for production at scale. We're designing, building, and testing next generation long range strike weapons systems to give America and its Allies a definitive edge and deter future conflicts." Role overview: "We are seeking a Senior Cybersecurity Architect to lead the design and implementation of secure, resilient information security systems, monitoring, red/blue team activities, and more in support of regulated, compliance-heavy environments. This hands-on role is responsible for translating mission, system, and regulatory requirements into end-to-end cybersecurity solutions. These complete solutions should benefit from the candidate's experienced and thoughtful implementation of company policy, automation and enforcement of workflows/processes, and technical security measures. Based in our Torrance, CA HQ, you'll lead efforts to build, maintain, and continuously improve our security and compliance posture across both local and remote sites. You'll collaborate with cross-functional teams—including IT, software development, operations, engineering, manufacturing, and legal—to ensure our security controls meet both technical and regulatory standards." That's good. Responsibilities list: bullet points from "Define and implement security architectures aligned with Zero Trust principles, defense-in-depth, and least-privilege models" through "Serve as on-site cybersecurity expert for Torrance HQ and occasionally travel (5–10%) to other locations (TX/NM)." Actually the last bullet about travel is part of responsibilities list? It appears after the list? In the posting, after responsibilities list there is "Serve as on-site cybersecurity expert for Torrance HQ and occasionally travel (5–10%) to other locations (TX/NM)." That seems like a responsibility bullet. We'll include it. Let's list responsibilities: - Define and implement security architectures aligned with Zero Trust principles, defense-in-depth, and least-privilege models - Develop security reference architectures, patterns, and standards for enterprise and program-level systems - Ensure cybersecurity is embedded across the full system lifecycle (requirements, design, development, test, deployment, sustainment) - Design, implement, and maintain cybersecurity tools and systems, including firewalls, EDR, IDS/IPS, SIEM, and vulnerability scanners. - Conduct threat modeling, security risk assessments, and vulnerability analyses. Proactively monitor security events, investigate suspicious activity, and respond to incidents with urgency and precision. - Develop and maintain System Security Plans (SSPs), POA&Ms, and supporting documentation for audits and assessments. - Partner with IT, engineering, DevSecOps, and Program Security to integrate security into infrastructure and application design. - Manage security patching cycles and lead remediation efforts based on risk assessments. - Support audit, compliance, and risk management activities (e.g., NIST, CMMC, & others) and manage supply chain cybersecurity concerns. - Conduct regular internal audits and readiness checks in preparation for external audits or DoD reviews. - Serve as on-site cybersecurity expert for Torrance HQ and occasionally travel (5–10%) to other locations (TX/NM). Now Required Qualifications list: - 7-10+ years of hands-on experience in cybersecurity engineering, infrastructure security, or related fields. - Strong technical background in network security, endpoint protection, access control, and vulnerability management. - Proficiency with modern security tools (e.g., CrowdStrike, Palo Alto, Nessus, Splunk, Snort, etc.). - Experience with incident response, malware analysis, and penetration testing. - Demonstrated experience with cloud security (AWS, Azure, or GCP). - Deep understanding of security principles, threats, and frameworks (e.g., cyber kill chain, MITRE ATT&CK, NIST, CIS Controls). - Strong documentation, troubleshooting, and communication skills. - Ability to thrive in fast-paced, high-pressure environments with competing priorities. - Ability to pivot between analyst, threat hunter, and implementer roles with ease. - Eligibility for U.S. security clearance. Also ITAR requirement: "To conform to U.S. Government export regulations, applicant must be a (i) U.S. citizen or national, (ii) U.S. lawful, permanent resident (aka green card holder), (iii) Refugee under 8 U.S.C.1157, or (iv) Asylee under 8 U.S.C.1158, or be eligible to obtain the required authorizations from the U.S. Department of State." We can include that as a bullet under Requirements. Preferred Qualifications list: - Experience in regulated environments (DoD, aerospace, SCIFs). - Active Security+, CISSP, CISM, CEH, or similar senior-level certification(s). - Relevant experience with NIST 800-171, CMMC, DFARS, or other in relation to cybersecurity audit readiness. - Experience with incident response, malware analysis, or penetration testing is a plus. - Experience in SOC operations. Also "What We're Looking For" and "Leadership Qualities" etc. Those are more like desired attributes; could be included under Qualifications or maybe under Skills? But we have Skills section optional. Could create a Skills section for those leadership qualities. However instruction says prefer few substantive sections over many thin ones. We could incorporate those into Qualifications (preferred) as bullets. But we already have Preferred Qualifications; we can add those leadership bullets there. Let's extract "What We're Looking For" bullets: - A proactive security professional who sees audits and compliance as opportunities to build better systems—not just check boxes. - A disciplined thinker who can balance security, business needs, and regulatory constraints. - A calm, solutions-oriented team member who leads by example during assessments, incidents, or high-pressure reviews. - A clear communicator who knows how to educate non-technical stakeholders without watering things down. Leadership Qualities: - Bias to Action and Creative Problem Solving. - Desire and experience questioning assumptions in ways that lead to break through ideas that are ultimately implemented. - Successfully bring in applicable processes/concepts/materials from other industries to achieve efficiency gains. - Ability to personally resolve minor issues in development without requiring significant support. - High Commitment, High Initiative. A successful candidate will have a genuine passion for Castelion's mission and consistently look for ways to contribute to the company's technical goals and prevent hardware blockers. - Ability to work in a fast paced, autonomously driven, and demanding atmosphere. - Strong sense of accountability and integrity. - Clear Communicator. Proactively communicates blockers. Trusted in previous roles to be voice of company with regulators, suppliers, gate keepers and customers. Capable of tactfully managing relationships with stakeholders to achieve company-desired outcomes without compromising relationships. Emails, IMs and verbal interactions are logical, drive clarity, and detailed enough to eliminate ambiguity. We could merge these into Preferred Qualifications or maybe a separate Skills section. Since we already have Qualifications (preferred