CISO Support SME

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule only if content present. The posting includes description, responsibilities, mandatory qualifications, preferred qualifications. No explicit Benefits, Pay, Schedule. So we should include sections: About the role (intro paragraph), Responsibilities (list), Requirements (maybe mandatory qualifications?), Qualifications (maybe education/experience?), Skills (technical expertise). We need to follow rules: use

for section headings. Use

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

  for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID/requisition numbers as headings — none present. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove boilerplate etc. The posting includes a lot of introductory narrative about DARPA, then description of role. We need to keep all substantive info. We'll need to parse. We need to decide sections: "About the role" could contain the introductory narrative about DARPA and the role description up to responsibilities? The responsibilities list is explicit. Then "Requirements" could contain mandatory qualifications (clearance, education, senior SETA experience, technical expertise). "Qualifications" could contain preferred qualifications. "Skills" could contain technical expertise list? But technical expertise already part of mandatory qualifications. Might be redundant. Perhaps better: "About the role" includes the narrative about DARPA and the role purpose. "Responsibilities" list. "Requirements" includes mandatory qualifications (clearance, education, senior SETA experience, technical expertise). "Preferred Qualifications" maybe as separate section? But we only have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put preferred qualifications under "Qualifications". Skills could be technical expertise? But we already have technical expertise in requirements. Might be okay to have Skills separate listing specific skills: cloud architecture, CDS, AI/ML, RMF, NIST, etc. However we must not invent or summarize away detail; we can list them as they appear. We need to preserve all substantive information. So we need to include everything from the posting except boilerplate (cookie/navigation/legal/EEO etc). There's none. We need to output only HTML fragment. Let's extract sections: Intro narrative (since 1958... up to "The primary function is to serve as a top-tier advisor, influencing the strategic direction of cybersecurity for the nation's next generation of breakthrough technologies.") That's about the role. Then "Responsibilities will include, but are not limited to the following:" followed by bullet points (each starting with bold heading). We'll need to convert each bullet to

• . The bullet points have headings like "Strategic Advisory & Leadership:" then description. We'll keep the heading as part of li text. Then "Mandatory Qualifications" list: Security Clearance, Education, Senior SETA Experience, Technical Expertise (with subpoints). We'll need to list each as li. Then "Preferred Qualifications" list: Experience, Strategic Vision (with subpoints). We'll list as li. We might also include "Skills" maybe from technical expertise subpoints: Authoritative expertise in architecting, securing, and assessing complex hybrid cloud and/or multi-cloud environments (AWS, Azure) within secure government contexts. At least 5 years of technical experience in a Major Acquisition Program Office in the DoW. Extensive and deep practical experience with the architecture, approval process (e.g., UCDSMO), and operational management of Cross Domain Solutions (CDS). Profound understanding of the security challenges and opportunities presented by emerging technologies, particularly AI/ML. Mastery of DoD cybersecurity policies, the Risk Management Framework (RMF), and NIST security standards. We could put those under Skills section as list. But we must not duplicate content. If we put them under Requirements (mandatory qualifications) we already have them. The instructions: "Use
  • for any list of duties/requirements/benefits". So we can put the mandatory qualifications list under Requirements. The preferred qualifications could be under Qualifications. The technical expertise details could be under Skills (maybe separate). However the mandatory qualifications already include technical expertise as a bullet with subpoints; we could keep that as part of Requirements list, and not duplicate in Skills. But we need to include all substantive info; if we put technical expertise under Requirements, that's fine. Then Skills section could be omitted if no separate skills beyond that. But we need to decide if we should include Skills section at all. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine technical expertise into Requirements and not have a separate Skills section. Then we have About the role, Responsibilities, Requirements, Qualifications (preferred). That's four sections. We must ensure we don't create sections with filler like "not specified". We have content for each. Now we need to format. We'll output:

    About the role

    ... (intro narrative)

    Responsibilities

    • Strategic Advisory & Leadership: Provide principal-level cybersecurity expertise and strategic counsel to DARPA senior leadership. Lead critical assessments and shape the agency's long-term security roadmap for cloud and emerging technologies.
    • Cloud & CDS Architecture Authority: Serve as a leading authority on the evaluation of secure cloud architectures and Cross Domain Solutions. Provide definitive recommendations on designs for multi-level, hybrid cloud, and highly sensitive environments, ensuring they are resilient, compliant, and mission capable.
    • Emerging Technology Threat & Opportunity Analysis: Drive analysis of the strategic security implications of nascent and future technologies. Develop and champion novel security frameworks and threat models for AI, quantum computing, and other areas of strategic interest to DARPA.
    • Portfolio-Level Cybersecurity Strategy: Guide Program Managers in the development of robust, portfolio-wide cybersecurity strategies. Mentor performers and government staff on the integration of advanced security principles from program inception through technology transition.
    • Independent Technical Validation: Lead independent technical assessments and validations of performer-developed technologies. Provide clear, unbiased, and impactful recommendations to senior government leaders on the viability, security, and risk posture of proposed solutions.
    • Senior-Level Liaison and Influence: Act as a key liaison between the CISO’s office, program offices, and the broader national security R&D community. Leverage deep professional relationships to foster collaboration and influence cybersecurity best practices.

    Requirements

    • Security Clearance: Must possess an active Top Secret (TS) security clearance with eligibility for Sensitive Compartmented Information (SCI). Eligibility for SAP access and a counterintelligence scope polygraph may be required.
    • Education: Master’s degree or Ph.D. in a relevant technical field (e.g., Computer Science, Engineering, Cybersecurity, or a related discipline).
    • Senior SETA Experience: A minimum of 15 years of progressive experience, with at least 6 years operating in a senior SETA, principal advisor, or chief architect capacity supporting DoD or Intelligence Community agencies.
    • Technical Expertise:
      • Authoritative expertise in architecting, securing, and assessing complex hybrid cloud and/or multi-cloud environments (AWS, Azure) within secure government contexts.
      • At least 5 years of technical experience in a Major Acquisition Program Office in the DoW.
      • Extensive and deep practical experience with the architecture, approval process (e.g., UCDSMO), and operational management of Cross Domain Solutions (CDS).
      • Profound understanding of the security challenges and opportunities presented by emerging technologies, particularly AI/ML.
      • Mastery of DoD cybersecurity policies, the Risk Management Framework (RMF), and NIST security standards.
    But note: we have nested
    inside
    • . That's allowed but maybe better to keep as separate list items under Requirements without nesting? The instruction: Use
      • for any list of duties/requirements/benefits. It didn't forbid nested lists. Could be okay. However we could flatten: list each subpoint as separate li under Requirements, but then we lose grouping under Technical Expertise. Could keep as separate li with description including subpoints. Simpler: keep as one li with semicolon separated subpoints. But we need to preserve all detail; we can include subpoints as separate sentences inside the li. That's fine. Thus:
      • Technical Expertise: Authoritative expertise in architecting, securing, and assessing complex hybrid cloud and/or multi-cloud environments (AWS, Azure) within secure government contexts; at least 5 years of technical experience in a Major Acquisition Program Office in the DoW; extensive and deep practical experience with the architecture, approval process (e.g., UCDSMO), and operational management of Cross Domain Solutions (CDS); profound understanding of the security challenges and opportunities presented by emerging technologies, particularly AI/ML; mastery of DoD cybersecurity policies, the Risk Management Framework (RMF), and NIST security standards.
      That preserves all. Now Preferred Qualifications under Qualifications:

      Qualifications

      • Experience: Extensive experience providing direct SETA support to DARPA or a similar high-paced R&D organization.
      • Recognized as a subject matter expert in cloud security, CDS, or AI security within the DoD or Intelligence Community.
      • Extensive experience briefing and advising Flag Officers, Senior Executive Service (SES) members, and other senior government leaders.
      • Strategic Vision: Demonstrated ability to anticipate future technology and threat trends and develop long-range strategic plans to address them.
      Now we need to include the intro narrative. Let's copy it exactly but remove any boilerplate. The intro: "Since 1958, DARPA has made pivotal investments in breakthrough technologies for national security. As the world changes dramatically – and even the pace of change itself increases – the agency seeks to engage the best minds and best ideas across specialties, communities, and disciplines to solve the greatest national security challenges on the horizon. DARPA brings together scientists, engineers, and tinkerers across the innovation ecosystem to push the bounds of technological possibility. The work we do is challenging by nature, but working with DARPA doesn’t have to be. To make it happen, DARPA's program managers need highly skilled support contractors, broadly referred to as SETAs (Scientific Engineering and Technical Assistance) within DARPA. Often spanning programs, portfolios, and even offices in their impact, the SETAs help program managers chart and navigate the path toward groundbreaking discoveries. For the fortunate few who become part of the DARPA legacy, a time bound journey with the organization represents a unique and singular opportunity to alter the future. At DARPA, every day is a chance to make history. A chance to explore, discover, and invent. A chance to collaborate with pioneers in science and engineering contributing to an enduring mission. The CISO SME provides principal-level advisory and thought leadership to senior DARPA executives, including the Chief Information Security Officer (CISO) and senior ITD Staff. As a Senior Senior Scientific, Engineering, and Technical Assistance (SETA), this position is a key strategic resource that helps shape the agency's approach to cybersecurity across its most advanced and sensitive technology portfolios. Requires a distinguished expert with extensive, deep experience in secure multi-level cloud architectures, Cross Domain Solutions (CDS), and the complex security landscape of paradigm-shifting technologies like Artificial Intelligence (AI). Will operate with a high degree of autonomy to provide strategic foresight, critical technical analysis, and authoritative guidance, ensuring that security is an enabler of innovation for DARPA's high-risk, high-reward programs. The primary function is to serve as a top-tier advisor, influencing the strategic direction of cybersecurity for the nation's next generation of breakthrough technologies." We need to ensure we keep all that. Note there is a typo