Network Engineer, Senior

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 as heading. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove Identity Statement, Candidate AI Usage Policy, Work Model, Commitment to Non-Discrimination? Those are boilerplate/legal; we should remove them. Also remove "Clearance: Applicants selected will be subject to a security investigation..." maybe part of Requirements? It's about clearance requirement; we can include under Requirements or Qualifications. The posting includes "Secret clearance" under You Have. Also "HS diploma or GED". Also "Nice If You Have:" list. We need to parse content: Job posting: Job Number: R0243400 Network Engineer, Senior The Opportunity: (this is like About the role) - maintain responsibility for completing site surveys and creating structured designs for the customer’s network in support of voice, data, security, and audio and visual systems. Design engineered drawings, specifications, reports, and other technical documents. Work closely with other IT and facilities team members, project teams, clients, architects, engineers, subcontractors, vendors, material suppliers, and other technical resources with analyzing business and technical requirements to develop system designs, estimates, implementation plans, and management and customer reports, and coordinate the structured cabling design with other design disciplines. Implement final network solutions to support on-prem and cloud environments. Manage the production of network devices and network architecture design, and develop all supporting documentation required for implementation in a global network. You Have: (Requirements/Qualifications) list: - 5+ years of experience designing, deploying, and supporting network and security architectures within DoD hybrid environments, including implementing Zero Trust principles or advanced routing designs - 3+ years of experience deploying, upgrading, and troubleshooting multivendor network and security equipment and solutions, including Palo Alto, Cisco, Juniper, Dell, HPE, or VMware - 2+ years of experience documenting complex network and security architectures, procedures, and troubleshooting workflows, including Zero Trust Network Access (ZTNA) implementations or detailed documentation of BGP policy behavior, NGFW IDS or IPS configurations, or NAT or SNAT translation flows - 2+ years of experience with security, routing, and switching protocols, including BGP, IS-IS, OSPF, MPLS, LDP, RSVP, VPLS, STP, or L3VPNs - Secret clearance - HS diploma or GED Nice If You Have: (Preferred qualifications/Skills) - Experience with DoD networks - Experience deploying and configuring Software Defined Wide Area Networks (SD-WAN) solutions - Experience with F5 - Experience operating, deploying, or administering Linux and Unix systems - Experience applying STIGs to systems or security hardening of systems - Experience operating, deploying, or administering Windows systems and services - Experience with commercial or DoD Cloud networks - CCNA, CCNP, VMWare, JNCIA, or JNCP Certification Compensation section: includes benefits description and salary range. Compensation At Booz Allen... includes health, life, disability, financial, retirement benefits, paid leave, professional development, tuition assistance, work-life programs, dependent care. Recognition awards program. 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. Salary at Booz Allen is determined by various factors... The projected compensation range for this position is $77,500.00 to $176,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. This posting will close within 90 days from the Posting Date. We need to extract Benefits and Pay sections. Benefits: health, life, disability, financial, retirement benefits, paid leave, professional development, tuition assistance, work-life programs, dependent care, recognition awards program. Also mention eligibility criteria (full-time/part-time >=20 hrs). That's benefits info. Pay: salary range $77,500 to $176,000 annualized USD. Schedule: Not explicitly given. There's no mention of schedule (full-time/part-time?). It mentions full-time and part-time employees working at least 20 hours a week are eligible for benefits. That implies schedule could be full-time or part-time, but not a specific schedule. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. For Schedule, we don't have explicit schedule like "Monday-Friday 9-5" etc. So we should not create a Schedule section. However we could include schedule info under Benefits? Probably not. Better to omit Schedule section. We need sections: About the role (The Opportunity), Responsibilities (maybe same as Opportunity? The Opportunity includes responsibilities. Could treat as About the role. Responsibilities could be derived from the Opportunity bullet points. But we must not create thin sections. We could combine About the role and Responsibilities? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only when posting has real specific content. The Opportunity is basically description of role; we can put that under About the role. Responsibilities could be the list of duties from Opportunity; but that may duplicate. However we could treat Opportunity as About the role and then Responsibilities as the list of duties (maybe same). To avoid duplication, we could put the detailed duties under Responsibilities and keep About the role brief summary. But we must preserve all substantive information; we can't lose details. So we need to include the duties somewhere. We could put them under Responsibilities as a list. And About the role could be a short paragraph summarizing the role (maybe from first sentence). But we need to ensure we don't lose any detail. If we put summary in About the role and then list duties under Responsibilities, we preserve all. That's acceptable. Thus:

About the role

Maintain responsibility for completing site surveys and creating structured designs for the customer’s network in support of voice, data, security, and audio and visual systems. Design engineered drawings, specifications, reports, and other technical documents. Work closely with other IT and facilities team members, project teams, clients, architects, engineers, subcontractors, vendors, material suppliers, and other technical resources with analyzing business and technical requirements to develop system designs, estimates, implementation plans, and management and customer reports, and coordinate the structured cabling design with other design disciplines. Implement final network solutions to support on-prem and cloud environments. Manage the production of network devices and network architecture design, and develop all supporting documentation required for implementation in a global network.

That's basically the Opportunity paragraph; we can keep as About the role. Then Responsibilities: maybe we can break into bullet list of duties. But the Opportunity paragraph already covers duties; we could just not have Responsibilities section to avoid duplication. However the instruction says prefer a few substantive sections over many thin ones. Having both About the role and Responsibilities with similar content may be thin. Better to have only About the role and treat that as responsibilities. But we need to follow the heading list: they gave examples but not mandatory to use all. We can choose which sections to include based on content. So we can include About the role (the description) and then Requirements, Qualifications, Skills, Benefits, Pay. We could combine Requirements and Qualifications? They are separate headings. The posting has "You Have:" which includes both required experience and education/clearance. Could treat as Requirements. "Nice If You Have:" could be Skills or Qualifications. Usually Qualifications are required, Skills are preferred. We'll map: - Requirements: the "You Have:" list (5+ years, 3+ years, 2+ years, 2+ years, Secret clearance, HS diploma or GED). That's required. - Qualifications: maybe we could treat as same as Requirements? But we need to avoid thin sections. Could combine Requirements and Qualifications into one section? But headings are distinct; we could put all under Requirements and skip Qualifications if no distinct content. However the instruction: include a section ONLY when the posting has real, specific content for it. If we put all under Requirements, we still have content for Requirements. Qualifications would have no specific content (if we don't separate). So we should omit Qualifications. - Skills: from "Nice If You Have:" list. That's specific content, so we include Skills. - Benefits: from Compensation paragraph describing benefits. - Pay: salary range. Thus sections: About the role, Requirements, Skills, Benefits, Pay. We must not include Schedule. Now format: Use

for each heading. Use

• for any list of duties/requirements/benefits. For Benefits we have a list; we can make
  . For Requirements we have list; we can make
  . For Skills we have list; we make
  . For About the role we have prose; use

  . For Pay we have a sentence; use

  . We need to preserve all substantive information. Ensure we don't lose any detail from the lists. Let's extract details precisely. About the role paragraph: We'll copy the Opportunity paragraph exactly as given (maybe minor punctuation). It is: "Maintain responsibility for completing site surveys and creating structured designs for the customer’s network in support of voice, data, security, and audio and visual systems. Design engineered drawings, specifications, reports, and other technical documents. Work closely with other IT and facilities team members, project teams, clients, architects, engineers, subcontractors, vendors, material suppliers, and other technical resources with analyzing business and technical requirements to develop system designs, estimates, implementation plans, and management and customer reports, and coordinate the structured cabling design with other design disciplines. Implement final network solutions to support on-prem and cloud environments. Manage the production of network devices and network architecture design, and develop all supporting documentation required for implementation in a global network." We'll keep that. Requirements list: - 5+ years of experience designing, deploying, and supporting network and security architectures within DoD hybrid environments, including implementing Zero Trust principles or advanced routing designs - 3+ years of experience deploying, upgrading, and troubleshooting multivendor network and security equipment and solutions, including Palo Alto, Cisco, Juniper, Dell, HPE, or VMware - 2+ years of experience documenting complex network and security architectures, procedures, and troubleshooting workflows, including Zero Trust Network Access (ZTNA) implementations or detailed documentation of BGP policy behavior, NGFW IDS or IPS configurations, or NAT or SNAT translation flows - 2+ years of experience with security, routing, and switching protocols, including BGP, IS-IS, OSPF, MPLS, LDP, RSVP, VPLS, STP, or L3VPNs - Secret clearance - HS diploma or GED We need to keep each as

  • . Skills list (Nice If You Have): - Experience with DoD networks - Experience deploying and configuring Software Defined Wide Area Networks (SD-WAN) solutions - Experience with F5 - Experience operating, deploying, or administering Linux and Unix systems - Experience applying STIGs to systems or security hardening of systems - Experience operating, deploying, or administering Windows systems and services - Experience with commercial or DoD Cloud networks - CCNA, CCNP, VMWare, JNCIA, or JNCP Certification Benefits list: from Compensation paragraph: "health, life, disability, financial