Linux Systems Administrator

We need to output HTML fragment with sections: headings

for sections present: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. The posting includes: "The Opportunity" (maybe About the role). Then "Responsibilities". Then "Required" (maybe Requirements/Qualifications). Then "Desired" (maybe Skills). Then "What You Can Expect" (maybe Benefits? Actually it's culture description). Then "Pay Range" and salary range. No explicit schedule. So we need sections: About the role (from The Opportunity), Responsibilities, Requirements (maybe combine Required and Desired? But we have separate sections: Requirements, Qualifications, Skills. We need to decide which to use. The posting has "Required" and "Desired". Could map Required to Requirements, Desired to Skills or Qualifications. We'll include Requirements (

Requirements

) with the Required bullet list. Then Skills (

Skills

) with Desired bullet list. Or Qualifications could be used for Required. But we need to avoid thin sections. We'll include Requirements and Skills. Benefits: The "What You Can Expect" includes culture, flexible time off, learning resources. That's benefits-ish but not explicit benefits like healthcare. However they mention "broad and competitive mix of benefits options" and list healthcare, wellness, financial, retirement, family support, continuing education, time off benefits. That's in Pay Range paragraph. So we can include Benefits section with that list. Pay: we have salary range. Schedule: not present, so omit. We must not repeat job title as heading. No Job ID etc. We need to use

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

  for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: EEO etc. Remove duplicated lines. Remove application instructions (none). Remove cookie/navigation/legal etc. We need to include all substantive info: The Opportunity paragraph, Responsibilities list, Required list, Desired list, What You Can Expect paragraph (culture, trust, growth), Pay Range paragraph (including factors and salary range), Benefits list (healthcare, wellness, financial, retirement, family support, continuing education, time off benefits). Also mention "competitive compensation, benefits and learning and development opportunities." Might be part of Benefits. We must not include placeholders like "commensurate with experience". Not present. We need to ensure we don't create sections with filler. So we will have sections: About the role (

  About the role

  ) with the Opportunity paragraph. Responsibilities (

  Responsibilities

  ) with ul list. Requirements (

  Requirements

  ) with ul list of Required items. Skills (

  Skills

  ) with ul list of Desired items. Benefits (

  Benefits

  ) with ul list of benefits. Pay (

  Pay

  ) with p containing the Pay Range paragraph and salary range. We must not include Schedule. Check that we didn't miss any substantive info: The Opportunity paragraph includes details about role: hands-on Linux Systems Administrator III, Infrastructure Team supporting EW systems, support end-to-end Linux environment, etc. We'll keep that. Responsibilities list: we need to capture each bullet. The responsibilities are a paragraph with sentences separated by periods. We need to turn into list items. The text: "Build, configure, maintain, patch, and upgrade Linux bare-metal servers and virtual machines, primarily running Red Hat Enterprise Linux (RHEL) and Ubuntu. Independently troubleshoot complex issues across Linux workstations, servers, virtual machines, infrastructure appliances, storage, authentication, and network connectivity. Administer and troubleshoot virtualization platforms including Proxmox and VMware vSphere. Develop and maintain automation and configuration management solutions using Ansible and Puppet. Configure, optimize, troubleshoot, and maintain Linux networking and supporting infrastructure services. Implement and maintain system monitoring, logging, and dashboards to proactively identify performance and availability issues. Design and implement infrastructure improvements to increase reliability, fault tolerance, scalability, and performance. Deploy, administer, and troubleshoot containerized workloads using Docker and Podman, and support Kubernetes environments. Review Nessus and other vulnerability scan results and remediate identified vulnerabilities through patching, configuration changes, and system hardening. Coordinate and perform recurring system updates, upgrades, and patching across development, test, and production environments." We'll split each sentence into
• . Required list: "Bachelor's degree in Computer Science, Cybersecurity, Engineering, Information Technology, or a related field, or equivalent experience. 5+ years of hands-on Linux systems administration experience. Strong experience administering and troubleshooting Red Hat Enterprise Linux (RHEL) or similar enterprise Linux environments. Experience with Linux installation, configuration, patching, system hardening, and performance troubleshooting. Experience with virtualization platforms such as Proxmox and/or VMware vSphere. Experience with automation and configuration management tools such as Ansible and Puppet. Experience with container technologies including Docker and/or Podman. Strong working knowledge of Linux networking, DNS, storage, authentication, and system services. Ability to independently troubleshoot complex infrastructure issues across physical and virtual environments. Ability to obtain and maintain a Top Secret security clearance." We'll split each sentence. Desired list: "Active Top Secret security clearance. Security+ certification. Hands-on experience administering or supporting Kubernetes or another container orchestration platform. Experience with infrastructure monitoring, centralized logging, CI/CD, or automated deployment environments. Experience supporting Linux infrastructure in classified, disconnected, or restricted-network environments." We'll split each sentence. Benefits list: The text: "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." Also earlier: "We offer competitive compensation, benefits and learning and development opportunities." Also "unique flexible time off benefit". Also "robust learning resources". Also "A culture of integrity... An environment of trust... A focus on continuous growth." Those are more cultural; maybe they belong in Benefits? But we already have a Benefits section for tangible benefits. The "What You Can Expect" paragraph includes culture, trust, growth, flexible time off, learning resources. That could be considered Benefits but it's more about culture. However we need to include all substantive info. We could put that in a section like "About the role" or maybe a separate section "What You Can Expect". But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put the culture description under About the role? But About the role already has the Opportunity paragraph. We could extend About the role to include that paragraph. However the instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., not limited to? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only use those headings. We cannot create a heading like "What You Can Expect". So we must fit that content into one of the allowed headings. Where does it fit best? Possibly Benefits (since it's about benefits and culture). Or About the role (since it's about what you can expect). But About the role is supposed to be about the role; but we could incorporate the culture description there as part of the role description. However we already have the Opportunity paragraph describing the role. Adding the culture description might be okay as it's still about the role/what you can expect. But we must not invent or summarize away detail; we can include it as a paragraph under About the role. Thus About the role will contain two paragraphs: the Opportunity paragraph and the What You Can Expect paragraph (culture, trust, growth, flexible time off, learning resources). That preserves all. Benefits section will contain the list of benefits: healthcare, wellness, financial, retirement, family support, continuing education, time off benefits. Also maybe mention "competitive compensation, benefits and learning and development opportunities." But that's somewhat redundant. We'll include the list. Pay section will contain the paragraph about factors influencing salary and the salary range. Now ensure we don't include boilerplate: Remove EEO statement at end. Also remove "CACI is an Equal Opportunity Employer..." line. Also remove any duplicated lines: none. Now produce HTML fragment. We must not include or . Just the fragment. Let's craft. About the role:

  About the role

  The Opportunity paragraph...

  What You Can Expect paragraph...

  But we need to ensure we preserve all substantive info from What You Can Expect: "A culture of integrity. At CACI, we place character and innovation at the center of everything we do. As a valued team member, you’ll be part of a high-performing group dedicated to our customer’s missions and driven by a higher purpose – to ensure the safety of our nation. An environment of trust. CACI values the unique contributions that every employee brings to our company and our customers - every day. You’ll have the autonomy to take the time you need through a unique flexible time off benefit and have access to robust learning resources to make your ambitions a reality. A focus on continuous growth. Together, we will advance our nation's most critical missions, build on our lengthy track record of business success, and find opportunities to break new ground — in your career and in our legacy." We'll keep that as a paragraph. Responsibilities:

  Responsibilities

  • ...
  ...
  Requirements:

  Requirements

  ...
  Skills:

  Skills

  ...
  Benefits:

  Benefits

  • healthcare
  • wellness
  • financial
  • retirement
  • family support
  • continuing education
  • time off benefits
  Maybe also include "competitive compensation, benefits and learning and development opportunities." but that's not a list item; could be a p. But we already have list; we could add a p before list:

  We offer competitive compensation, benefits and learning and development opportunities.

  Then the ul. Pay:

  Pay

  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. 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. The Proposed Salary Range For This Position Is $86,600 - $181,800

  But note we already used benefits list; we might duplicate benefits description. However we need to preserve all substantive info; the Pay paragraph includes benefits description again. It's okay to repeat? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep that paragraph as is, even if it repeats benefits. However we already have a Benefits section with list. If we repeat the same sentences in Pay section, it's duplication but it's from original text. We could keep it; but we might want to avoid duplication? The instruction says remove duplicated lines. That refers to duplicated lines in the posting. The Pay paragraph includes benefits description that also appears elsewhere