Systems AdministratorNew Virginia

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We need to extract from posting. We have job title already shown, so we don't repeat it. We need sections: maybe "About the role" (Job Summary), "Responsibilities" (maybe from Required Skills? Actually responsibilities are tasks: maintain, upgrade, evolve Linux/K8s, act as advisor, etc.), "Requirements" (Required Skills), "Qualifications" (Education And Experience, Certifications and Credentials), "Skills" (Desired Skills maybe), "Benefits" (Total Compensation paragraph about benefits), "Pay" (salary range), "Schedule" (Work Model? Actually location type is Onsite, but schedule not given; we have Work Model describing onsite expectation; but schedule not explicit. Might not include Schedule if no specific schedule like full-time hours. The posting says Job Type: Full-Time Exempt. That's schedule info: full-time. Could include Schedule section with "Full-Time". But we need to avoid filler like "not specified". Full-Time is specific. So we can include Schedule. We must not include boilerplate like EEO, AI usage policy, etc. Remove those. We must preserve all substantive info. So we need to include details: company summary maybe part of About the role? Could be separate "About the company" but not in allowed headings. Allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We can put company summary under About the role? Or maybe we can include a brief paragraph about the role under About the role, and include company summary maybe as part of About the role? The instruction: use

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

for section headings (e.g. ...). Likely we should only use those headings. So we need to fit content into those sections. Thus: - About the role: include Job Summary and maybe company summary? The job summary is about role. Could also include company summary as context but maybe better to put under About the role as a brief description of the company? The heading is About the role, not company. But we can include both role summary and maybe mention company mission? Might be okay. - Responsibilities: list duties: maintain, upgrade, evolve Linux and Kubernetes platforms; act as technical advisor and liaison to lab leadership and project teams; help bridge gap; maintain hardware/software across hybrid environment; troubleshoot; manage data flows; patch management, security scanning, STIG compliance; infrastructure automation; version control; scripting; communication; organizational skills; professionalism; self-starter; desire to learn. But many of those are also skills. However responsibilities are tasks. We'll list bullet points. - Requirements: Required Skills list (the bullet list). Could be under Requirements. - Qualifications: Education And Experience, Certifications and Credentials. - Skills: Desired Skills list. - Benefits: paragraph about total compensation package: medical, dental, vision premiums 100% employer-paid, HSA contributions, 401(k), PTO, professional development stipend, etc. - Pay: salary range $85,000 - $105,000, plus note about additional compensation. - Schedule: Full-Time Exempt (job type). Could also mention Onsite location type but schedule is about time. We'll put Full-Time. We must not repeat job title as heading. Also not include Job ID etc. We must not include boilerplate like EEO, AI usage, etc. We must output only HTML fragment, no /, no markdown fences. Let's craft. We need to ensure we use

• for any list of duties/requirements/benefits. For prose use

  . We'll have sections:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Qualifications

  • ...
  ...

  Skills

  • ...
  ...

  Benefits

  ...

  Pay

  ...

  Schedule

  Full-Time Exempt

  We need to ensure we preserve all substantive info. Let's extract details. Company summary: "Rampant Technologies is an independently owned defense contractor delivering specialized support to the most sensitive national security missions across the Department of Defense and the Intelligence Community. Guided by our philosophy of Securing, Enabling, and Executing our customers' critical missions, we bring together elite, cleared teams to solve the hardest technical challenges in intelligence analysis, signals processing, full-spectrum cyber operations, AI/ML and analytics, software engineering, and enterprise IT. We hire mission and technical specialists, prioritizing people over processes and quality over quantity, so that every engagement advances the mission and shapes the future of national security." Job Summary: "We are seeking a skilled Systems Administrator to support and advance our IT infrastructure, with a primary focus on hybrid cloud and on-prem environments running RHEL-based Linux systems and Kubernetes-based containerization. This role supports a dynamic R&D lab environment that integrates closely with the broader enterprise. The Systems Administrator will be responsible for maintaining, upgrading, and evolving both Linux and Kubernetes platforms, along with related infrastructure. You will also act as a technical advisor and liaison to lab leadership and project teams, helping bridge the gap between technical execution and strategic goals. Strong communication skills—both verbal and written—are essential for effectively engaging with both technical and non-technical stakeholders. Employment for this position is contingent upon contract award to Rampant Technologies. Final selection, start date, and offer of employment are subject to contract terms and client approval." We could incorporate company summary into About the role? Might be okay. Responsibilities: from Job Summary and Required Skills? Let's list: - Maintain, upgrade, and evolve Linux (RHEL) and Kubernetes platforms and related infrastructure in a hybrid on-prem/cloud environment. - Assist and support day-to-day operations and maintenance of hardware and software across hybrid on-prem and cloud environment. - Troubleshoot and manage data flows across systems. - Apply cybersecurity practices: patch management, security scanning, STIG compliance. - Use infrastructure automation tools (Ansible/Puppet) for automation. - Use version control systems (Git/GitLab). - Write scripts in Bash and/or Python for automation. - Act as technical advisor and liaison to lab leadership and project teams, bridging technical execution and strategic goals. - Communicate technical and business needs to stakeholders at all levels. - Produce clear, concise, actionable documentation (recommendations, technical assessments, integration plans). - Manage multiple projects, adapt to changing priorities. - Demonstrate professionalism, patience, diplomacy. - Show initiative as a self-starter. - Pursue technical and professional growth. We need to ensure we don't duplicate content from Required Skills as responsibilities; but it's okay if overlapping. Requirements: Required Skills list (the bullet list). Let's extract each line: - Assist and support day-to-day operations and maintenance of hardware and software across a hybrid on-prem and cloud environment - Strong expertise in installing, configuring, securing, and troubleshooting Red Hat Enterprise Linux (RHEL) systems - Possess foundational knowledge of Kubernetes and maintaining containerized environments - Advanced troubleshooting skills across Linux, networking, and storage technologies - Troubleshoots and manages data flows across systems - Strong understanding of cybersecurity practices to include patch management, security scanning, and STIG compliance - Proficient with infrastructure automation tools such as Ansible or Puppet - Experience using version control systems, particularly Git and GitLab - Proficient in scripting with Bash and/or Python for automation - Strong verbal communication skills, with the ability to clearly convey technical and business needs to audiences at all levels of a contract or project team - Strong written communication skills, with the ability to produce clear, concise, and actionable documentation, including recommendations, technical assessments, and integration plans - Strong organizational skills, with the ability to manage multiple projects and adapt to changing priorities - Demonstrates professionalism, patience, and diplomacy in interactions with colleagues, customers, and partners - Self-starter who shows initiative without waiting to be directed - Strong desire to learn and grow both technically and professionally We'll list each as
• . Qualifications: Education And Experience, Certifications and Credentials. Education And Experience: "Bachelor's degree in Computer Science or a technical discipline is desired, with at least two (2) years of relevant experience. Five (5) years of relevant experience may be substituted for a bachelor's degree." Certifications and Credentials: "Active TS/SCI w/ Poly required. IA certification required; i.e. Security+ CE or greater. Red Hat or Linux certifications are a plus. Kubernetes and/or CNCF certifications are a plus." We'll list as bullet points. Skills: Desired Skills list: - Experience in managing Cross-Domain Solutions (CDS) - Familiarity with AI/ML concepts and tooling, and/or experience supporting infrastructure that hosts AI/ML workloads - Experience with VMware administration - Experience configuring, presenting, and maintaining enterprise-class storage solutions (i.e. HPE, Dell, IBM) - General understanding of IP networking, including switching, subnets, and VLANs - Basic knowledge of hardware infrastructure, including servers, blade chassis, fiber channel, and SANs We'll list as bullet. Benefits: paragraph from Total Compensation: "We are an employee-centric company that knows our mission success depends on our people feeling valued and supported. To back that up, Rampant offers a competitive, total compensation package designed for your total well-being which includes 100% employer-paid medical*, dental, and vision premiums, company HSA contributions**, a generous non-contributory 401(k) plan, flexible paid time off (PTO), yearly professional development stipend, and more. For certain HDHP medical plans; enhanced plans will be subject to employee cost sharing. If enrolled in an HSA-eligible plan." We need to preserve the footnote markers? Probably keep as is. Pay: "Total Compensation The salary range for this role is $85,000 - $105,000, depending on education and experience. The salary range listed is a general guideline for this position. Final compensation will be based on factors such as role scope, experience, education, certifications, skills, geographic location, customer needs, contract requirements, and business considerations. Depending on the role and contract, employees may be eligible for additional compensation, including overtime, shift differentials, incentive pay, or discretionary bonuses. For multi-location roles, the posted salary range may reflect a national or role-based range and may vary by location and contract requirements." We'll include that. Schedule: "Job Type: Full-Time Exempt" and location type Onsite but schedule is Full-Time. We'll output "Full-Time Exempt". Now ensure we don't include any boilerplate like EEO, AI usage, Work Model details beyond schedule? The Work Model section includes details about remote/hybrid/onsite expectations. That might be considered schedule? But we already have schedule. Could include a note about Onsite expectation under Schedule? But schedule heading is for time, not location. However we could include location info under About the role? But we already have location given earlier: VA Location Type: Onsite. Might be worth including in About the role or maybe as a separate section? Not allowed headings. Could incorporate into About the role: mention that the role is onsite in VA. We'll add location info in