Sr Wireless Network Engineer

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements (or Qualifications), Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We have: - About The Role: paragraph(s). Should be

About the role

then

content. - Responsibilities: list of duties. Use

• . - Qualifications: includes Required: Clearance, Education, Expertise, Experience, Certifications, Skills, Desired Project Management. Could be separate sections? The instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Qualifications heading, maybe also Skills heading separate if content distinct. But we have Skills listed under Qualifications. Could combine? Better to have Qualifications heading covering required qualifications, and maybe Skills heading for skills? However we have Skills listed under Qualifications and also Desired Project Management. Might be okay to have Qualifications and Skills separate if we have content. But we must not create thin sections. Let's see content: Under Qualifications Required: includes Clearance, Education, Expertise, Experience, Certifications, Skills (Proficient with MS Office Suite). Desired Project Management: Minimum of 3 years experience managing telecommunications and/or data center projects. Thus we could have:

  Qualifications

  with
  • items covering clearance, education, expertise, experience, certifications, skills, desired project management. Alternatively split Skills: but skills are just MS Office Suite; could be under Qualifications. We also have Benefits: description of benefits: "Our broad and competitive mix of benefits options is designed to support and protect employees and their families. At CACI, you will receive comprehensive benefits such as; healthcare, wellness, financial, retirement, family support, continuing education, and time off benefits." That's specific enough for Benefits section. Pay: The posting includes "The Proposed Salary Range For This Position Is $105,100-$231,100". Also earlier mentions Pay Range paragraph. So we have Pay section. Schedule: Not mentioned explicitly; only "Full time" and "Percentage of Travel Required: Up to 50%". No schedule details like shift, hours. So we should not create Schedule section. We also have "Why Join Us?" and "What You Can Expect" sections but those are not in allowed headings list; we should not create headings for them unless they map to Benefits etc. The "Why Join Us?" is more like benefits/culture; but we already have Benefits. Could incorporate into Benefits or maybe ignore as not required headings. The instruction: Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use

    for section headings (e.g. ...)". Likely they expect only those headings. Safer to stick to those. Thus we will output:

    About the role

    ... (the paragraph(s) from About The Role)

    Responsibilities

    • ... each responsibility

    Qualifications

    • ... each qualification item

    Benefits

    ... benefits paragraph

    Pay

    The Proposed Salary Range For This Position Is $105,100-$231,100

    We need to preserve all substantive information; not invent or summarize away detail. Must not repeat job title as heading. Must not put Job ID etc. We need to extract About The Role paragraph: "CACI’s Enterprise IT (EIT) Sector is seeking a Senior Wireless Engineer to support an Air Force Modernization program. In this role, you will play a crucial part in the infrastructure modernization of unclassified and classified base area networks, focusing on wireless solutions. Need someone to work onsite at Northern VA or High Point, NC and 50% travel involved." We should keep that as is. Responsibilities list: bullet points from responsibilities: - Network Design & Engineering: Contribute to the creation of network architectures, topology diagrams, and data flow artifacts (Visio) for wireless solutions, ensuring high availability and performance. - Project Leadership & Strategy: Support site surveys and the Engineering team in designing modernized network architecture, ensuring compliance with Air Force standards and security protocols. - Cybersecurity Compliance: Design, implement, and document secure network architectures, including STIG checklists, port/protocol/service documentation, and Plan of Actions and Milestones (POA&M) in compliance with DAF and DoD RMF standards. - Implementation: Oversee the installation of wireless network equipment, including access points, controllers, and related hardware. - Operational Transition & Maintenance: Perform, troubleshoot, and resolve network issues. Provide Tier 3 support to Operations & Maintenance (O&M) teams. - Quality & Safety Assurance: Ensure all installations meet industry safety standards and operational cleanliness, restoring sites to original or better condition. We need to preserve each as
  • . Qualifications: list items: - Clearance: Must currently hold U.S. Government Secret Security Clearance. - Education: University Degree (BA/BS) or equivalent experience and 7+ years of related work experience. Alternatively, a High School diploma or associate degree with 10+ years performing as a Manager in DoD supporting large, complex networks. - Expertise: In-depth knowledge of wireless networking technologies, protocols, and standards (e.g., Wi-Fi 6, WPA3). - Experience: Experience with wireless network design tools and software. - Certifications: DoD 8140 IAT II Baseline Certification (CompTIA Security+ CE or CCNA-SEC); CCNP or CCDP or equivalent. CWNP Certifications (e.g., CWNA, CWSP, CWDP). - Skills: Proficient with MS Office Suite (Word, Excel, PowerPoint). - Desired Project Management: Minimum of 3 years of experience managing telecommunications and/or data center projects. We could combine some but keep as separate
  • . Benefits: paragraph: "Our broad and competitive mix of benefits options is designed to support and protect employees and their families. At CACI, you will receive comprehensive benefits such as; healthcare, wellness, financial, retirement, family support, continuing education, and time off benefits." Pay: paragraph: "The Proposed Salary Range For This Position Is $105,100-$231,100" We should not include extra fluff like "Since this position can be worked in more than one location, the range shown is the national average for the position." That is also substantive; we should include it? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should include that sentence as part of Pay section maybe. The Pay section currently has the range; we can add the explanatory sentence. Thus Pay

    could contain both sentences. Also there is earlier paragraph about Pay Range factors; that is also substantive. Should we include? It says: "Pay Range There are a host of factors that can influence final salary including, but not limited to, geographic location, Federal Government contract labor categories and contract wage rates, relevant prior work experience, specific skills and competencies, education, and certifications. Our employees value the flexibility at CACI that allows them to balance quality work and their personal lives. We offer competitive compensation, benefits and learning and development opportunities." That's also substantive about pay. Should we include? It is about pay and benefits. Since we have a Pay section, we could include that paragraph as well. However we must avoid boilerplate? It's not boilerplate; it's specific to pay. So include. Thus Pay section could have multiple

    elements? The instruction: Use

    for prose. So we can have multiple

    inside the section. Thus:

    Pay

    Pay Range There are a host of factors that can influence final salary including, but not limited to, geographic location, Federal Government contract labor categories and contract wage rates, relevant prior work experience, specific skills and competencies, education, and certifications. Our employees value the flexibility at CACI that allows them to balance quality work and their personal lives. We offer competitive compensation, benefits and learning and development opportunities.

    The Proposed Salary Range For This Position Is $105,100-$231,100. Since this position can be worked in more than one location, the range shown is the national average for the position.

    But we need to ensure we don't duplicate content. The earlier paragraph also mentions "Our broad and competitive mix of benefits options..." which is benefits, not pay. So we keep benefits separate. Now Benefits section: we have the paragraph about benefits. Could also include "Our broad and competitive mix of benefits options is designed to support and protect employees and their families. At CACI, you will receive comprehensive benefits such as; healthcare, wellness, financial, retirement, family support, continuing education, and time off benefits." That's it. Now we need to output only HTML fragment, no markdown fences. Let's craft. Check for any other sections: "Why Join Us?" and "What You Can Expect" contain culture statements; not in allowed headings; we could ignore as they are not required headings but they are substantive. However instruction: "Prefer a few substantive sections over many thin ones." It doesn't forbid adding other headings, but says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings for those topics; other headings maybe not needed. The culture statements could be considered part of Benefits or maybe we could add a "Culture" heading but not in list. Safer to omit them, as they are not explicitly required. However we might be losing substantive info. But the instruction says "Preserve ALL substantive information". If we omit them, we lose info. But maybe they consider that as boilerplate? It's not boilerplate; it's about culture. However the allowed headings list includes Benefits, Pay, etc. Could we put culture under Benefits? Not really. Could we add a section "About the company" but not in list. The instruction says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. So we could add other headings if needed. But they also say "Prefer a few substantive sections over many thin ones." So we could add a section for "Why Join Us?" or "What You Can Expect" as a combined "Company Culture" heading. But we need to decide. Given the instruction to preserve ALL substantive information, I think we should include that info. We could create a heading

    About CACI

    or

    Why Join Us?

    . But the examples didn't include that. However they said "e.g." meaning for example. So it's okay to add other headings as long as they are

    . But we must not repeat job title as heading. So we can add a heading for "Why Join Us?" and "What You Can Expect". However they might be considered fluff? But they are substantive. Better to include them under a heading like "Why Join Us?" as it's a section in the posting. Let's do that. Thus sections: - About the role - Responsibilities - Qualifications - Why Join Us? (or "Why Join CACI?") - What You Can Expect (maybe combine) - Benefits - Pay But we must avoid many thin sections. Could combine Why Join Us and What You Expect into one section "Why Join Us?" containing both paragraphs. Let's extract: Why Join Us? paragraph: