System Security Engineer Cyber-Supply Chain Risk Management

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (EEO, etc). Must not invent or summarize away detail. Must not include placeholder text like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting does not mention pay, schedule, benefits explicitly. So we should not include those sections. We can include About the role (maybe a brief description). Responsibilities: list of duties. Requirements: maybe qualifications? Actually we have Qualifications section in posting: Required Skills/Experience, Education Requirements, Desired Skills, etc. Also there is an Overview about PeopleTec (company description) maybe could be About the role? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose which sections to include based on content. We have: - About the role: could be the introductory paragraph: "Opportunity PeopleTec is currently seeking a System Security Engineer Cyber-Supply Chain Risk Management (C-SCRM) to support our Huntsville, AL location. The candidate will serve as a System Security Engineer Cyber-Supply Chain Risk Management (C-SCRM) within a Project Management Office (PMO) within PAE Fires and will be responsible for providing technical support to the program's Chief Engineer and the Technical Chief." That's about the role. - Responsibilities: list of duties (the bullet list after "Duties"). - Requirements: maybe the qualifications? But we also have a Qualifications section. The posting has "Qualifications Required Skills/Experience:" etc. Also "Education Requirements". Also "Desired Skills". Also "Travel: 25% Must be a U.S. Citizen An active DoD Secret clearance is required". Those are requirements. - Skills: maybe we could separate skills from qualifications? But we can combine. However we need to avoid thin sections. Could have Qualifications section covering required skills/experience, education, desired skills, clearance, travel, citizenship. Skills section maybe not needed if we put skills in Qualifications. But we could still have Skills section listing specific technical skills: SPDX/CycloneDX, SCA, SAST/DAST, VEX, FIPS 140-3 validation, etc. However those are already in qualifications. Might be okay to have Skills section. But we must not create sections with filler. If we include Skills, we need actual content. We have specific skills: knowledge of SPDX/CycloneDX, SCA, SAST/DAST, VEX, FIPS 140-3 validation; strong knowledge of industry standards and defense requirements; excellent communication and presentation skills; ability to lead and work within multidisciplinary team; previous experience working in a U.S. Government Program Office (required). Those are skills. We could have Skills section listing those. We must not include Benefits, Pay, Schedule as they are not stated. We must not include duplicated lines. We must remove cookie/navigation/legal/EEO etc. So we strip the EEO statement and overview about PeopleTec? The overview about PeopleTec is not boilerplate but could be considered company description; maybe we can include as About the role? But the instruction says "About the role" heading for section headings. Could include a brief description of the role and maybe company overview? However we should preserve all substantive information. The overview about PeopleTec is substantive but not about the role; it's about the company. Could we include it under About the role? Might be okay. Or we could create a separate section like "About PeopleTec" but not allowed headings list only those given. So we could incorporate into About the role. We must not repeat the job title as a heading. So no heading with the title. We must not put Job ID/requisition numbers as headings. We must output only HTML fragment. Let's extract content. Introductory paragraph: "Opportunity PeopleTec is currently seeking a System Security Engineer Cyber-Supply Chain Risk Management (C-SCRM) to support our Huntsville, AL location. The candidate will serve as a System Security Engineer Cyber-Supply Chain Risk Management (C-SCRM) within a Project Management Office (PMO) within PAE Fires and will be responsible for providing technical support to the program's Chief Engineer and the Technical Chief." That's about the role. Duties list: - Provide technical support and security engineering in C-SCRM across the system lifecycle (design, development, acquisition, integration, testing, fielding, and sustainment). - Mandate and manage Software Bills of Materials (SBOMs) for all procured and open-source software. - Perform deep-dive vulnerability analysis and code provenance checks on third-party libraries. - Establish Software Composition Analysis (SCA) and Static Analysis (SAST) requirements within vendor onboarding. - Develop and maintain the Consolidated Program Software Bill of Materials (SBOM), Third-Party Software Vulnerability Reports, and Supplier Secure Software Attestation Forms. - Ensure compliance with defense and industry standards by managing C-SCRM processes effectively. - Interface with internal teams and external organizations to coordinate C-SCRM objectives and strategies. - Prepare and present C-SCRM findings, reports, and improvement plans to senior management and stakeholders. - Conduct strategic planning and coordination to support program objectives. - Provide technical expertise to support peer engineers within the Technology Security, Program Protection, Cyber Security, and Technical Management teams. - Use digital tools and methodologies to analyze supply chain risks, manufacturer/supplier relationships, and foreign ownership and controlling influence. - Perform other tasks as assigned by the Chief Engineer and/or Technical Chief. Qualifications/Requirements: - Required Skills/Experience: 5+ years of relevant experience. Additional education may be substituted for years of experience. - Demonstrated experience in C-SCRM, particularly within defense or aerospace industries. - Knowledge of SPDX/CycloneDX, Software Composition Analysis (SCA), SAST/DAST, VEX, and FIPS 140-3 validation. - Must meet minimum DoDI 8140.03 Defense Cyber Workforce qualification requirements in one of the following work roles: 622 (Secure Software Assessor) at the "Intermediate" level, or 652 (Security Architect) at the "Intermediate" level. - Strong knowledge of industry standards and defense requirements. - Excellent communication and presentation skills. - Ability to lead and work within a multidisciplinary team. - Previous experience working in a U.S. Government Program Office (required). - Travel: 25% - Must be a U.S. Citizen - An active DoD Secret clearance is required to perform this work. Candidates are required to have an active Secret clearance upon hire, and the ability to maintain this level of clearance during their employment. - Education Requirements: Bachelor's degree in Computer Science, Engineering, or a related technical discipline - Desired Skills: Top Secret clearance preferred; DoDI 8140.03 qualification at the "Advanced" level for work role 622 (Secure Software Assessor) or 652 (Security Architect) We could separate into Requirements (mandatory) and Qualifications (desired). But the instruction list includes both Requirements and Qualifications as possible headings. We could have Requirements for mandatory items, Qualifications for desired/education etc. Or we could combine. We need to avoid thin sections. Let's decide: - About the role: intro paragraph. - Responsibilities: duties list (as

• ). - Requirements: mandatory items: 5+ years experience, demonstrated experience in C-SCRM defense/aerospace, knowledge of SPDX/CycloneDX etc, DoDI 8140.03 Intermediate level for 622 or 652, strong knowledge of industry standards, excellent communication, ability to lead multidisciplinary team, previous US Govt Program Office experience, travel 25%, US Citizen, active Secret clearance, ability to maintain clearance. - Qualifications: education (Bachelor's degree), desired skills (Top Secret clearance preferred, DoDI 8140.03 Advanced level for 622/652). Could also include "Additional education may be substituted for years of experience" maybe under Requirements. - Skills: maybe we could list specific technical skills: SPDX/CycloneDX, SCA, SAST/DAST, VEX, FIPS 140-3 validation, digital tools for supply chain risk analysis, etc. But those are already in Requirements. Could still have Skills section but might duplicate. Better to not create Skills if it's thin. However we have a decent list of skills: knowledge of SPDX/CycloneDX, SCA, SAST/DAST, VEX, FIPS 140-3 validation; ability to use digital tools to analyze supply chain risks, manufacturer/supplier relationships, foreign ownership; etc. That could be a Skills section. But we must not create sections with filler. If we include Skills, we need to ensure we have substantive content not already covered elsewhere. It's okay to have some overlap? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication, but better to avoid redundancy. However we could keep Skills separate for clarity. Given the headings list includes Skills, we could include it. But we need to decide which sections to include to avoid too many thin ones. Let's see content volume: - About the role: ~2 sentences. - Responsibilities: ~12 bullet points. - Requirements: many bullet points (maybe 10). - Qualifications: education + desired skills (2 bullet points). - Skills: maybe 5 bullet points. That's okay. We must not include Benefits, Pay, Schedule. Now we need to format as HTML fragment: use

  for each section heading, then content:

  for prose,

  • for lists. We must not include any extra text outside HTML. Let's craft. First, About the role: we can put the introductory paragraph as

    . Second, Responsibilities:

    Responsibilities

    then
    with each duty. Third, Requirements:

    Requirements

    then
    with each requirement. Fourth, Qualifications:

    Qualifications

    then
    with education and desired skills. Fifth, Skills:

    Skills

    then
    with specific technical skills. Check for any boilerplate: we must remove EEO statement, overview about PeopleTec (maybe we included some in About the role? Actually we didn't include overview about PeopleTec; we only used the intro paragraph. The overview about PeopleTec is separate paragraph: "People First. Technology Always. PeopleTec, Inc. is an employee-owned small business founded in Huntsville, AL that provides exceptional customer support by employing and retaining a highly skilled workforce. Culture: ..." That's company overview. Should we preserve it? It's substantive information about the company. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should include that somewhere. Where could we put it? Could be part of About the role? Or we could have a separate section like "About PeopleTec" but not allowed headings. Could we incorporate into About the role? The About the role heading is for role description, but we could also include company overview there as it's still relevant to the opportunity. The instruction didn't forbid adding extra content under a heading as long as it's substantive. So we can add the company overview after the intro paragraph under About the role. Thus About the role will have two paragraphs: intro and company overview. Now we must ensure we didn't include any boilerplate like EEO statement, navigation, etc. We'll omit the EEO statement and the application instructions, the "#cjpost #dpost" etc. Now let's list the content precisely. About the role paragraph 1: "Opportunity