NC3 Enterprise and Nuclear Systems Integration Engineer

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 need to parse the job posting. Job title: NC3 Enterprise and Nuclear Systems Integration Engineer (already shown, not repeat). We need sections: - About the role: maybe from "The Opportunity:" paragraph. That's description of role. - Responsibilities: from "What You’ll Work On:" bullet list. - Requirements: from "You Have:" bullet list. - Qualifications: maybe from "Nice If You Have:"? Actually qualifications could be required vs nice-to-have. Could treat "You Have:" as Requirements, "Nice If You Have:" as Qualifications or Skills. But we need to follow headings: Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Benefits: described in "Compensation At Booz Allen..." paragraph about benefits. Pay: salary range $86,900 to $198,000. Schedule: Not explicitly mentioned; maybe work model? There's "Work Model" section describing remote/hybrid/onsite expectations. That could be considered Schedule? But schedule usually refers to full-time/part-time, hours. The posting mentions "Full-time and part-time employees working at least 20 hours a week..." but not specific schedule for this role. Could infer full-time? Not explicit. Better to omit Schedule if no specific content. Skills: Could be from technical skills list: MBSE tools, DevSecOps, etc. Could be under Skills. Qualifications: maybe education and clearance: Bachelor’s degree, Secret clearance, etc. Also "Nice If You Have:" includes TS/SCI clearance, degree in Engineering, Physics, CS, certifications. We need to avoid filler like "commensurate with experience". Not present. We must not include boilerplate like EEO, legal, etc. Remove Identity Statement, Candidate AI Usage Policy, Work Model? Work Model maybe not needed as schedule; but could be considered under Schedule? However schedule is about hours, not work model. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." So we need to see if posting states Schedule. It does not explicitly state schedule (like full-time, part-time, shift). It mentions "Full-time and part-time employees working at least 20 hours a week..." but that's generic benefits eligibility, not schedule for role. I'd consider that not specific schedule for this role, so omit Schedule section. Benefits: yes, there is a paragraph about benefits. So include Benefits. Pay: yes, salary range. Now we need to format. Use

for section headings. Use

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

  for prose. We must preserve all substantive information; do not invent or summarize away detail. We need to include all substantive info from sections we include. Let's extract. About the role: The Opportunity paragraph: "You understand the critical role NC3 plays in U.S. strategic deterrence and national security. You recognize the complexity and absolute precision required when engineering systems tied to nuclear weapon operations, survivable communications, force direction, and time critical decision support. We’re seeking a systems engineer with hands-on NC3 experience to help modernize, integrate, and secure the next generation of nuclear enterprise systems. You will shape resilient architectures, ensure compliance with nuclear surety and certification requirements, support nuclear weapon system interfaces, and drive the modernization of strategic command, control, and communication capabilities across the DoD. You will also ensure systems meet EMP or HEMP survivability requirements and operate within secure, accredited facilities. Join our team and help deliver the future of survivable, secure, and interoperable NC3 capabilities." We'll put that in

  . Responsibilities: bullet list under "What You’ll Work On:" each line starts with a verb. We'll capture each as

• . List: - Lead engineering, integration, and analysis across NC3 system of systems environments, including force direction, decision support, survivable communications, and nuclear weapon system interfaces. - Support full lifecycle systems engineering, including requirements development, architecture design, integration planning, verification or validation, fielding, and sustainment. - Develop and maintain enterprise, functional, and solution architectures aligned with NC3 guidance, Joint Staff requirements, and the DoDAF. - Apply MBSE to model operational and technical mission threads, nuclear timelines, survivability requirements, and system interactions within nuclear command and control (C2) environments. - Use MBSE tools such as SysML, Cameo, and MagicDraw. - Support integration with nuclear weapon systems, including data links, message formats, timing requirements, and safety or surety-related constraints. - Participate in DevSecOps pipelines supporting NC3 modernization, including secure development practices, automated testing, and cyber resilient deployment architectures. - Conduct cybersecurity, survivability, and resilience assessments across contested, degraded, or nuclear effects environments. - Ensure compliance with RMF, ATO/IATT, eMASS, and relevant cybersecurity standards. - Support RMF, cross domain solution accreditation, nuclear surety compliance, and eMASS documentation for NC3 and nuclear-related systems. - Perform systems analysis of nuclear enterprise data flows, authoritative data sources, and interoperability requirements across strategic forces. - Contribute to configuration management, engineering review boards, technical baseline management, and NC3 modernization decision forums. - Support EMP or HEMP hardening and testing per MIL-STD-188-125 and MIL-STD-4023. - Document system designs, interfaces, and technical data using MBSE models, engineering drawings, and technical manuals. That's all. Requirements: "You Have:" bullet list: - Experience supporting NC3 systems, nuclear weapon system interfaces, or strategic deterrence mission sets - Experience engineering complex, highly secure, and highly-regulated systems in cloud, hybrid, or specialized enclave environments - Experience with nuclear C2 operations, force direction messaging, timing requirements, and survivability considerations - Experience with DevSecOps, CI/CD, automated testing, and Infrastructure-as-Code in secure environments - Experience with EMP or HEMP hardening, secure facility operations, and compliance with MIL-STD-188-125, MIL-STD-4023, ICD-705, and NISPOM - Ability to support RMF, cybersecurity engineering, cross domain solutions, and nuclear certification or surety processes - Secret clearance - Bachelor’s degree Qualifications: maybe "Nice If You Have:" bullet list: - Experience supporting Air Force, STRATCOM, or NC3 modernization programs - Experience with nuclear weapon system messaging formats, PAL considerations, SAASM or Type 1 crypto, or specialized NC3 communication types - Experience with mobile power generation, HVAC, water purification, secure communications, and CSfC solutions - Experience with C3BM, ABMS, or DAF Battle Network concepts to ensure NC3 alignment with broader enterprise C2 architectures and mission‑thread integration - Knowledge of Zero Trust architectures and identity management in nuclear or special access environments - TS/SCI clearance - Bachelor’s degree in Engineering, Physics, CS, or a related field - Systems Engineering, Cybersecurity, Cloud, or MBSE Certifications such as INCOSE, Security+, CISSP, AWS, Azure, SAFe, SysML, Cameo, or MagicDraw Certification We could treat these as Qualifications. Skills: maybe we could extract specific technical skills from responsibilities and requirements? But we already have many. Could create a Skills section summarizing tools: MBSE (SysML, Cameo, MagicDraw), DevSecOps, CI/CD, IaC, RMF, ATO/IATT, eMASS, MIL-STD-188-125, MIL-STD-4023, ICD-705, NISPOM, Zero Trust, etc. However we risk duplication. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we can combine Skills into Qualifications or Requirements. But we need to follow headings; we can include Skills if we have specific content. We could list skills like: MBSE, SysML, Cameo, MagicDraw, DevSecOps, CI/CD, IaC, RMF, ATO/IATT, eMASS, MIL-STD-188-125, MIL-STD-4023, ICD-705, NISPOM, Zero Trust, etc. That seems substantive. But we already have many of those in Requirements and Qualifications. To avoid duplication, maybe we omit Skills section and keep Requirements and Qualifications. Benefits: paragraph: "Our offerings include health, life, disability, financial, and retirement benefits, as well as paid leave, professional development, tuition assistance, work-life programs, and dependent care. Our recognition awards program acknowledges employees for exceptional performance and superior demonstration of our values. Full-time and part-time employees working at least 20 hours a week on a regular basis are eligible to participate in Booz Allen’s benefit programs. Individuals that do not meet the threshold are only eligible for select offerings, not inclusive of health benefits. We encourage you to learn more about our total benefits by visiting the Resource page on our Careers site and reviewing Our Employee Benefits page." We'll put that in

  under Benefits. Pay: "The projected compensation range for this position is $86,900.00 to $198,000.00 (annualized USD). The estimate displayed represents the typical salary range for this position and is just one component of Booz Allen’s total compensation package for employees." We'll put that in

  under Pay. Schedule: none. Now produce HTML fragment. We need to ensure we don't include any markdown fences. Let's craft:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Qualifications

  • ...
  ...

  Benefits

  ...

  Pay

  ...

  Check for any repeated lines: ensure we didn't include boilerplate like "Join us. The world can’t wait." That's part of Opportunity? Actually after responsibilities there is "Join us. The world can’t wait." That's a tagline; could be considered part of About the role? It's after responsibilities but before "You Have:" It's a short motivational line. Should we include? It's substantive? It's not really detail about role; but it's part of posting. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should include it. Where does it belong? Could be part of About the role paragraph. We'll append to that paragraph. Thus About the role paragraph: include the Opportunity paragraph plus "Join us. The world can’t wait." Now check for any other substantive info: "Clearance: Applicants selected will be subject to a security investigation and may need to meet eligibility requirements for access to classified information; Secret clearance is required." That's already covered in Requirements (Secret clearance). Could add note but it's redundant. Might be okay to include but we already have Secret clearance. Could add a line about security investigation. But it's basically same. Might be considered boilerplate? It's specific to clearance. Could add as a separate line in Requirements? But we already have Secret clearance. The extra sentence about security investigation is extra detail. We should preserve it. So add a bullet: "Applicants selected will be subject to a security investigation and may need to meet eligibility requirements for access to classified information." But note that the Requirements bullet list already includes Secret clearance. We'll add another bullet. Now also note: "Certification Clearance: Applicants selected will be subject to a security investigation and may need to meet eligibility requirements for access to classified information; Secret clearance is required."