Operations Support (Security & Data Management)

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. Title: Operations Support (Security & Data Management) Operations Support_Security & Data Management Belong. Connect. Grow. with KBR! (some fluff). Then description: KBR’s National Security Solutions team provides high-end engineering... etc. Then "Why Join Us?" bullet points: Innovative Projects..., Collaborative Environment..., Impactful Work... This is a contingent position based upon contract award. Then: KBR is seeking an Operations Support and Security/Data Management Professional to support the Hemisphere Program for Space Systems Command (SSC), Space Domain Awareness and Combat Power (SZ). In this role, you will work in a fast-paced, mission-focused environment alongside Space Force personnel, contractors, and system developers. You will support day-to-day program operations with a strong emphasis on security, configuration/data management, and deliverables tracking, ensuring timely coordination, submission, and compliance across the program. Then "Responsibilities Include" list bullet points. Then "Required Qualifications" list bullet points. Then "Desired Qualifications" list bullet points. Then "Belong, Connect and Grow at KBR" paragraph about culture. Then "We Deliver – Together." maybe not needed. Then "KBR is an equal opportunity employer." boilerplate to remove. Then "R2124291" job ID to drop. We need to produce sections: About the role (maybe the initial description about role and why join us?), Responsibilities, Requirements (maybe combine Required Qualifications?), Qualifications (maybe Desired?), Skills (maybe list of skills from desired?), Benefits, Pay, Schedule. We need to include only sections with real specific content. The posting does not mention Benefits, Pay, Schedule. So we should NOT include those sections. We need to include About the role: we can combine the introductory paragraphs (KBR’s National Security Solutions team..., Why Join Us? bullet points, and the description of role). Should we separate "Why Join Us?" as part of About? Probably yes. Responsibilities: list from Responsibilities Include. Requirements: maybe Required Qualifications. Qualifications: Desired Qualifications. Skills: maybe we can extract skills from Desired Qualifications (CISSP, CISM, etc.) but those are qualifications. Could also include "Proficient in MS Office Suite..." etc. Those are skills. Could create a Skills section. But we need to avoid thin sections. Let's see what we have: - About the role: we have substantive content: KBR’s National Security Solutions team..., Why Join Us? bullet points, description of role. - Responsibilities: list of many items. - Required Qualifications: list. - Desired Qualifications: list. - Skills: maybe we can combine some of the desired qualifications that are skills (e.g., Effective written, oral, and interpersonal communication skills, Proficient in MS Office Suite..., Highly knowledgeable in navigating within shared cloud environments). Could be a Skills section. But we need to decide whether to split Required and Desired into Requirements and Qualifications sections. The instruction: use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map: - About the role: introductory text. - Responsibilities: the Responsibilities Include list. - Requirements: Required Qualifications. - Qualifications: Desired Qualifications (maybe treat as qualifications). - Skills: maybe we can extract skill-specific items from Desired Qualifications (like communication skills, MS Office proficiency, cloud environments). However the Desired Qualifications also includes education, years experience, certifications, etc. Those are qualifications not skills. Might be better to put Desired Qualifications under Qualifications, and then create a Skills section for things like communication, MS Office, cloud navigation. But we need to ensure we don't create thin sections. Let's see if we have enough for Skills: we have "Effective written, oral, and interpersonal communication skills", "Proficient in MS Office Suite Word, Excel, PowerPoint, and Visio", "Highly knowledgeable in navigating within shared cloud environments (Google Docs, Sheets, Sharepoint)". That's three items; could be a Skills section. We also have "Motivated individual who is a self-starter and works well in a dynamic team environment" - that's more of a trait, could be skill. Thus Skills section could have those. Now we need to ensure we don't repeat content. We'll need to parse the Desired Qualifications list and split into qualifications (education, years experience, certifications, CDSE Level 2) and skills (communication, MS Office, cloud). However the instruction says preserve ALL substantive information; do not invent or summarize away detail. So we must keep all info; we can just keep Desired Qualifications as a whole under Qualifications heading, and not create a Skills section if that would split content. But we can still create Skills section if we move some items there, but then we would be removing them from Qualifications, which would be losing detail unless we duplicate. Better to keep Desired Qualifications under Qualifications heading, and not create a separate Skills section unless we have additional skill-specific content not already covered. The posting does have skill-specific bullets in Desired Qualifications, but they are part of that list. If we put the entire Desired Qualifications under Qualifications, we still preserve all info. Then we don't need a Skills section. That's acceptable: we can have fewer sections. Thus sections: About the role, Responsibilities, Requirements, Qualifications. We must not include Benefits, Pay, Schedule as they are not present. Now we need to format: - Use

for section headings. - Use

• for any list of duties/requirements/benefits. - Use

  for prose. We need to ensure we don't repeat job title as heading. We need to drop minor metadata like Job ID. We need to remove boilerplate: equal opportunity employer, etc. We need to keep all substantive info. Let's extract About the role prose: From the posting: "KBR’s National Security Solutions team provides high-end engineering and advanced technology solutions to our customers in the intelligence and national security communities. In this position, your work will have a profound impact on the country’s most critical role – protecting our national security. Why Join Us? Innovative Projects: KBR’s work is at the forefront of engineering, logistics, operations, science, program management, mission IT and cybersecurity solutions.Collaborative Environment: Be part of a dynamic team that thrives on collaboration and innovation, fostering a supportive and intellectually stimulating workplace.Impactful Work: Your contributions will be pivotal in designing and optimizing defense systems that ensure national security and shape the future of space defense. This is a contingent position based upon contract award KBR is seeking an Operations Support and Security/Data Management Professional to support the Hemisphere Program for Space Systems Command (SSC), Space Domain Awareness and Combat Power (SZ). In this role, you will work in a fast-paced, mission-focused environment alongside Space Force personnel, contractors, and system developers. You will support day-to-day program operations with a strong emphasis on security, configuration/data management, and deliverables tracking, ensuring timely coordination, submission, and compliance across the program." We need to turn that into prose paragraphs. Could split into a couple paragraphs. We should preserve the bullet points under "Why Join Us?" as list? The instruction: Use

  • for any list of duties/requirements/benefits. The "Why Join Us?" bullet points are a list of benefits/attributes. So we could make a
    for those. However the heading "About the role" could contain prose and then a list. Thus About the role section:

    About the role

    then maybe a

    with the first sentences, then a

    for Why Join Us bullet points, then a

    for the rest. But we need to ensure we don't create a separate section for Benefits; we can include Why Join Us as part of About. Now Responsibilities: list from Responsibilities Include. We need to capture each bullet point. Let's list them: - Assist the Government in execution of routine business operations, especially security, configuration & data management - Support Hemisphere Security and Configuration Management (CM) teams in all aspects of program, personnel, and processes to deliver exceptional quality products to the Government - Assist and streamline preparation of security plans, reviewing applicable guidelines, and established procedures for all areas of security to include Information Security, Physical/Technical Security, Classification Management, Communication Security (COMSEC), and Program Security - Prepare, submit, and maintain personnel security packages for Special Access Programs (SAPs) - Support facility and network security actions, inspections and daily activities - Swiftly execute corrective measures to address security concerns raised by the Government or team members - Update and collaborate with Hemisphere leadership on Security action items and activities - Work with configuration manager (CM) manager to develop a numbering/identification (ID) scheme for classified deliverables - Prepare weekly program briefings and present at program staff meetings for all security matters - Actively support CM team on data management and sharing in platforms (i.e. Confluence, Sharepoint, Jira) - Coordinate and collaborate with CM team to track and manage the Government’s written acceptance, comments, and/or change requests against classified deliverables - Develops, documents, modifies, transitions, and maintains standard functional databases to support organizations in meeting mission requirements Note: some bullet points start with verb, some with "Develops". Keep as is. Now Required Qualifications: - Active TS/SCI clearance - BS degree in a related science or engineering field (information technology, information security, security management, cybersecurity, computer engineering) - CompTIA+ certification - 10+ years of relevant work experience - Experience in supporting Sensitive Compartment Information and/or Special Access Acquisition Programs within the DoD - Expert in Defense Information Security Services (DISS) and JADE database or the legacy Joint Personnel Adjudication System (JPAS) Now Desired Qualifications (we'll put under Qualifications): - Master’s degree in a related science or engineering field (systems engineering, cybersecurity, security management) - 12 years of experience supporting DoD acquisition programs - Skilled in navigating through physical and personnel security processes - CISSP, CISM certifications - CDSE Level 2 - Motivated individual who is a self-starter and works well in a dynamic team environment - Effective written, oral, and interpersonal communication skills - Proficient in MS Office Suite Word, Excel, PowerPoint, and Visio - Highly knowledgeable in navigating within shared cloud environments (Google Docs, Sheets, Sharepoint) Now we need to output HTML fragment. We must not include any markdown code fences. We'll produce:

    About the role

    KBR’s National Security Solutions team provides high-end engineering and advanced technology solutions to our customers in the intelligence and national security communities. In this position, your work will have a profound impact on the country’s most critical role – protecting our national security.

    • Innovative Projects: KBR’s work is at the forefront of engineering, logistics, operations, science, program management, mission IT and cybersecurity solutions.
    • Collaborative Environment: Be part of a dynamic team that thrives on collaboration and innovation, fostering a supportive and intellectually stimulating workplace.
    • Impactful Work: Your contributions will be pivotal in designing and optimizing defense systems that ensure national security and shape the future of space defense.

    This is a contingent position based upon contract award. KBR is seeking an Operations Support and Security/Data Management Professional to support the Hemisphere Program for Space Systems Command (SSC), Space Domain Awareness and Combat Power (SZ). In this role, you will work in a fast-paced, mission-focused environment alongside Space Force personnel, contractors, and system developers. You will support day-to-day program operations with a strong emphasis on security, configuration/data management, and deliver