Linux System Administrator

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate etc. We need to parse the description and extract relevant content. Let's identify sections: - About the role: The introductory paragraph(s) describing mission, role purpose. Could be: "Looking for an opportunity to make an impact? At Leidos, we deliver innovative solutions...". Also "Leidos is seeking a System Administrator to support a large enterprise IT contract for the DOD." etc. We'll put that in

About the role

with

paragraphs. - Responsibilities: The list of duties: "Primary Tasks" bullet list. Also earlier description: "This role requires...", "This individual should be detail oriented...", "This role is responsible for interacting with other administrators...", etc. We'll extract duties. - Requirements: Basic Qualifications list. - Qualifications: Preferred Qualifications list. - Skills: maybe combine technical skills? Could be separate but we can include Skills section if there is content like "Strong oral and written communications skills", "Time management skills", etc. Might be part of Requirements. But we can create Skills section for soft skills. - Benefits: The posting mentions "Pay and benefits are fundamental..." and then lists "Employment benefits include competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement." Also earlier "Pay Range $92,300.00 - $166,850.00". So we have Pay and Benefits sections. - Schedule: Not explicitly mentioned except "Support customer requirements in a 24/7/365 environment and be able to provide on-call support during outages occurring after hours." That's schedule info. So we can include Schedule section with that. We must not include sections with filler like "commensurate with experience". We have actual content. We must not repeat job title. We must not include metadata like Job ID, requisition numbers. We must not include boilerplate like EEO, scam warning, etc. Remove those. We must preserve all substantive info; do not invent or summarize away detail. So we need to keep details like specific technologies, certifications, etc. We need to output only HTML fragment, no /, no markdown fences. Let's craft. First, About the role: combine the introductory paragraphs up to "Leidos is seeking a System Administrator to support a large enterprise IT contract for the DOD." Also maybe the mission statement. We'll produce:

About the role

Looking for an opportunity to make an impact? At Leidos, we deliver innovative solutions through the efforts of our diverse and talented people who are dedicated to our customers’ success. We empower our teams, contribute to our communities, and operate sustainable. Everything we do is built on a commitment to do the right thing for our customers, our people, and our community. Our Mission, Vision, and Values guide the way we do business. If this sounds like a mission you want to be a part of, keep reading! Leidos is seeking a System Administrator to support a large enterprise IT contract for the DOD.

That seems fine. Responsibilities: We'll list duties from "Primary Tasks" and earlier role description. Let's extract duties: - Experience with interacting with customers to handle service inquiries and problems. - Provide technical support, administration, and monitoring of Linux, Microsoft, and Mac systems within a VMware virtual environment. - Provide support for the implementation, troubleshooting and maintenance of IT systems. - Rapidly distinguish isolated user problems from enterprise-wide application/system problems. - Coordinate with customers and stakeholders to collect data, conduct analysis, develop, and implement solutions associated with incident tickets and requirements. - Develop solutions to complex technical issues. - Provide follow-up reports (technical findings, feedback, resolution steps taken) for Root Cause analysis, engineering technical assessment and process improvement initiatives. - Support customer requirements in a 24/7/365 environment and be able to provide on-call support during outages occurring after hours. - Update operations and monitoring documentation for 24/7/365 Operations Watch personnel. - This role requires an individual that has technical experience with administering Linux and Windows servers within a VMware virtual environment. - This individual should be detail oriented in order to capture customer inquiries appropriately. - This role is responsible for interacting with other administrators to handle service inquiries and problems. - Duties include examining customer problems and suggesting and implementing appropriate corrective action to initiate a repair or return to service. - This role analyzes recurring problems and initiates solutions for preventing reoccurrence and analyzes existing infrastructure for tuning/performance enhancements. - The individual will provide systems and software operations and maintenance support in a large, multi-enclave enterprise environment. - This individual will work in a team environment to ensure mission needs are met and ensure functionality of capabilities of customers. - Individuals in this role may be required to perform technical software configuration, rebooting, and other remedial actions on customer servers. We need to avoid duplication. We'll consolidate unique items. Let's create a

• list. Responsibilities section:

  Responsibilities

  • Interact with customers to handle service inquiries and problems.
  • Provide technical support, administration, and monitoring of Linux, Microsoft, and Mac systems within a VMware virtual environment.
  • Support implementation, troubleshooting, and maintenance of IT systems.
  • Rapidly distinguish isolated user problems from enterprise-wide application/system problems.
  • Coordinate with customers and stakeholders to collect data, conduct analysis, develop, and implement solutions associated with incident tickets and requirements.
  • Develop solutions to complex technical issues.
  • Provide follow‑up reports (technical findings, feedback, resolution steps) for root‑cause analysis, engineering technical assessment, and process‑improvement initiatives.
  • Support customer requirements in a 24/7/365 environment and provide on‑call support during after‑hours outages.
  • Update operations and monitoring documentation for 24/7/365 Operations Watch personnel.
  • Administer Linux and Windows servers in a VMware virtual environment.
  • Capture customer inquiries accurately with detail‑oriented attention.
  • Interact with other administrators to handle service inquiries and problems.
  • Examine customer problems, suggest and implement corrective actions to restore service.
  • Analyze recurring problems, initiate preventive solutions, and tune infrastructure for performance enhancements.
  • Provide systems and software operations and maintenance support in a large, multi‑enclave enterprise environment.
  • Work in a team environment to meet mission needs and ensure customer capability functionality.
  • Perform technical software configuration, rebooting, and other remedial actions on customer servers as required.
  That seems comprehensive. Requirements (Basic Qualifications): list. Basic Qualifications bullet list: - Foundational knowledge of AWS or Azure cloud services and the cloud ecosystem. - Familiarity with Hyper Converged Infrastructure (HCI) concepts and solutions such as Dell VXRail. - Experience with Tier 2 system administration of server operating systems such as Linux (CentOS, RHEL, or Ubuntu) and Microsoft Server (2012 R2/2016). - Familiarity with supporting virtual desktops running Linux, Microsoft Windows, and/or MacOS. - Experience with Scripting/Automation through Linux Shell scripts, PowerShell, PowerCLI, or other scripting languages. - Experience troubleshooting issues in a growing environment. - Experience with log reviews, incident analysis, and identification of issue trends. - Experience with server patch management methodologies. - Time management skills with the ability to work within an IT Service Management/ticketing system (ServiceNow) independently. - Ability to triage and properly classify incidents and prioritize work efforts accordingly. - Strong oral and written communications skills. - Track record of working effectively within a team, and support to peers toward improved processes and results. - Candidate must, at a minimum, meet DoD 8570.11- IAT Level II certification requirements (currently Security+ CE, CCNA-Security, GSEC, or SSCP). - Clearance: US Citizenship required; Current TS/SCI with the ability to obtain and maintain a polygraph. - Education/Experience: bachelor’s degree with 8 years of prior relevant experience or a master’s degree with 6 years of prior relevant experience, associate's with 10 years, or high school diploma with 12 years. We'll put these in
  . Qualifications (Preferred Qualifications): - Certification relating to VMware (VCA/VCP), Microsoft Server Administration (MCSA), Linux Administration (Linux+), or Mac Administration (ACSP) a plus. - Experience with Ansible, Satellite, Puppet, Chef, a plus. We'll list. Skills: Could include soft skills like strong oral/written communication, time management, teamwork, etc. But those are already in Requirements. However we can still create a Skills section for those if we want, but we must not duplicate content? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication, but better to avoid redundancy. However we can still include Skills section for things like "Strong oral and written communications skills", "Time management skills", "Ability to triage and prioritize", "Track record of working effectively within a team". But those are already in Requirements. Might be okay to keep them there and not have separate Skills. But we need to decide if we include Skills section. The instruction: "Prefer a few substantive sections over many thin ones." So we might combine skills into Requirements or Qualifications. Since we already have Requirements and Qualifications, we may omit Skills section to avoid thin section. However we have to include a section only when posting has real specific content for it. If we don't have distinct skills beyond those already captured, we could skip Skills. But we could also include Skills for things like "Scripting/Automation through Linux Shell scripts, PowerShell, PowerCLI, or other scripting languages" which is technical skill. But that's already in Requirements. So maybe we skip Skills. Benefits: We have content: "Pay and benefits are fundamental to any career decision. That's why we craft compensation packages that reflect the importance of the work we do for our customers. Employment benefits include competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement. More details are available at www.leidos.com/careers/pay-benefits." We should include that as Benefits section. Pay: We have Pay Range $92,300.00 - $166,850.00 and note about guideline. We'll include Pay section. Schedule: We have "Support customer requirements in a 24/7/365 environment and be able to provide on-call support during outages occurring after hours." Also maybe "Update operations and monitoring documentation for 24/7/365 Operations Watch personnel." That's schedule. We'll include Schedule section. We must not include boilerplate like "For U.S. Positions: While subject to change..." etc. That's about posting duration; we can drop as it's not substantive about job. Also "Original Posting September 16, 2026" etc. Drop. Also "About Leidos" etc. That's company description; could be considered About the role? Already we have some mission. But we could include a brief About Leidos paragraph? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." The "About Leidos" is not minor metadata; it's company info. Could be considered part of About the role? Might be okay to include in About the role section as