Systems Administrator, Windows

We need to output only HTML fragment, using

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No job title heading. No Job ID etc. Remove boilerplate (EEO, etc). Must preserve all substantive info. We need to parse the posting. First paragraph: "Bering-Alaka'ina Holdings (BAH) is looking for a Systems Administrator (Windows). The position will support our government customer located in Kekaha, Hawai'i. Provides Windows system administration for all Clients and Servers connected to the Pacific Missile Range Facility (PMRF) classified and unclassified networks. Deploys Cyber Security mandated system upgrades, system patches, and system security lockdown requirements. Performs system wide troubleshooting and problem resolution in a live mission environment." That's description; could be About the role. Then "DESCRIPTION OF RESPONSIBILITIES:" then list of responsibilities bullet-like sentences. We'll put under

Responsibilities

with

• each. Then "Additional Responsibilities:" then bullet list: General office environment with site visits as well as periodic "at sea" duty to support the PMRF's Mobile at Sea Sensor system (MATSS) Candidate must be capable of working in a team environment and participate in technical and system administrative activities throughout project life cycles. Physical Elements: Lifting/Pulling/Pushing: Over 50 lbs. (two-men assist) Positions: walking or standing, crawling, kneeling, cramped, and work requiring repeated stooping, sitting, and/or frequent stair climbing. Environmental: Customer Contact, Extended Workday, Confined Work Area, Office Laboratory, Field Assignment, Inclement Weather These are also responsibilities or maybe "Physical Requirements". But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put physical elements under Responsibilities or maybe Requirements? Probably Responsibilities includes duties; physical elements could be part of Requirements? But we have no separate heading for Physical Requirements. We could include them under Responsibilities as additional responsibilities. That seems okay. Then "REQUIRED DEGREE/EDUCATION/CERTIFICATION:" then details. That's Qualifications (or Requirements). We have both Requirements and Qualifications headings. We need to decide what goes where. Typically Requirements could be education/experience/certifications; Qualifications could be skills? But we also have Skills heading. Let's map: - About the role: overview paragraph. - Responsibilities: list of duties (including additional responsibilities). - Requirements: maybe education, certification, clearance? Or we could put education/experience/certifications under Requirements. - Qualifications: maybe desired skills? But we also have Skills heading. Let's think: The posting has "REQUIRED DEGREE/EDUCATION/CERTIFICATION:" then "REQUIRED SKILLS & EXPERIENCE:" then "DESIRED SKILLS AND EXPERIENCE:" then "REQUIRED CITIZENSHIP AND CLEARANCE:" then benefits paragraph. Thus we could map: - Requirements: education, certification, citizenship/clearance? Or maybe Requirements = required degree/education/certification + required citizenship and clearance. - Qualifications: maybe not needed; but we have to include only if real content. Could combine required skills & experience under Skills? Actually we have Skills heading. So we could put required skills & experience under Skills, and desired skills & experience also under Skills (maybe separate sub-sections? but we just need
  • ). Could separate required vs desired but not required. - Benefits: paragraph about competitive salaries, 401K, medical, etc. - Pay: not specified (no salary). So we should NOT include Pay section because no specific pay. - Schedule: not specified (no schedule). So omit. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits. Check if any content for Qualifications: maybe we could treat required degree/education/certification as Qualifications, and required skills & experience as Skills. But we have both Requirements and Qualifications headings allowed. We need to decide which to use. The instruction: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not strict mapping. We can choose whichever fits content. We need to avoid empty sections. So we need to assign each piece of content to a heading. We have: - About the role: overview paragraph. - Responsibilities: duties list. - Requirements: maybe education/experience/certifications + citizenship/clearance. - Skills: required skills & experience + desired skills & experience. - Benefits: benefits paragraph. We could also include Qualifications if we want to split education/experience vs skills, but we already have Skills. Could treat Requirements as education/experience/certifications, Qualifications as skills? But then we would have both Skills and Qualifications overlapping. Better to follow typical pattern: Requirements = education/experience/certifications; Qualifications = skills; Benefits = benefits. But we also have Skills heading as example; maybe they expect Skills for skills, Qualifications for qualifications like certifications? Hmm. Let's see typical job posting: Often they have "Requirements" (education, experience), "Qualifications" (skills, abilities), "Benefits". But they also gave Skills as example. Could be they want to separate skills from qualifications. However we have both Required Skills & Experience and Desired Skills & Experience. That's clearly skills. So we could put those under Skills. Then what about Qualifications? Could put education/experience/certifications there. Then Requirements could be something else like citizenship/clearance? But we don't have a separate heading for clearance; maybe we put under Requirements as well. But we need to avoid empty sections. Let's decide: - About the role: overview. - Responsibilities: duties. - Requirements: education, experience, certifications, citizenship/clearance (maybe combine). - Qualifications: maybe not needed if we put all under Requirements. But we could put required skills & experience under Qualifications, and desired skills & experience under Skills? That seems odd. Better: Use Requirements for education/experience/certifications; Use Skills for required & desired skills; Use Benefits for benefits; Omit Qualifications because we don't have distinct qualifications beyond skills. But we must only include sections when posting has real specific content for it. If we omit Qualifications, that's fine. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits. Now we need to extract content precisely, preserving all substantive info, not inventing or summarizing away detail. Let's extract About the role paragraph: "Bering-Alaka'ina Holdings (BAH) is looking for a Systems Administrator (Windows). The position will support our government customer located in Kekaha, Hawai'i. Provides Windows system administration for all Clients and Servers connected to the Pacific Missile Range Facility (PMRF) classified and unclassified networks. Deploys Cyber Security mandated system upgrades, system patches, and system security lockdown requirements. Performs system wide troubleshooting and problem resolution in a live mission environment." We'll put that in

    . Responsibilities: list items from "DESCRIPTION OF RESPONSIBILITIES:" and "Additional Responsibilities:" plus maybe the bullet list after that. Let's list each responsibility sentence: From DESCRIPTION OF RESPONSIBILITIES: - Administer and maintain Microsoft Windows Server environments in classified and unclassified environments across Navy networks. - Manage Active Directory, DNS, DHCP, and Group Policy Objects across multiple domains and enclaves. - Implement and maintain RMF security controls and ensure systems are compliant with DISA STIGs and DoW cybersecurity policies. - Apply and manage patches and updates across all Microsoft systems in accordance with DoW and Navy patch management policies. - Manage automated installation methods and system imaging (e.g. SCCM, VMare, Nutanix) (note typo VMare but keep as given) - Perform system hardening, patching, and vulnerability remediation using tools such as ACAS, ESS, and SCAP. - Develop and maintain PowerShell scripts for automation of administrative tasks and system configuration. - Support virtualization platforms (VMware, Hyper-V) and manage virtual infrastructure lifecycle. - Collaborate with cybersecurity teams to support ATO packages, POA&Ms, and audit readiness. - Maintain system documentation, configuration baselines, and standard operating procedures (SOPs). - Participate in Change Control Boards (CCBs) and Configuration Management Boards (CMBs). - Assist with incident response, forensic analysis, and system recovery efforts. - Support backup and disaster recovery strategies using enterprise tools (e.g.,Veeam, Commvault). Additional Responsibilities: - General office environment with site visits as well as periodic "at sea" duty to support the PMRF's Mobile at Sea Sensor system (MATSS) - Candidate must be capable of working in a team environment and participate in technical and system administrative activities throughout project life cycles. - Physical Elements: Lifting/Pulling/Pushing: Over 50 lbs. (two-men assist) - Positions: walking or standing, crawling, kneeling, cramped, and work requiring repeated stooping, sitting, and/or frequent stair climbing. - Environmental: Customer Contact, Extended Workday, Confined Work Area, Office Laboratory, Field Assignment, Inclement Weather We could treat each bullet as separate

    . For the physical elements etc, we could keep as one

    each. Now Requirements: includes REQUIRED DEGREE/EDUCATION/CERTIFICATION and REQUIRED CITIZENSHIP AND CLEARANCE. Let's extract: REQUIRED DEGREE/EDUCATION/CERTIFICATION: - Associates degree or HS diploma/GED and at least four (4) years of System Administration/IT experience. (Advance certifications may be substituted for a degree or experience.) (Years of directly related work experience may be substituted for a degree.) - DOD 8570.1M IAT Level II (subject to change based on industry, DoD, or local policy requirements) - One of the following OS Certifications required prior to start (subject to change based on industry, DoD or local policy requirements) - Azure Administrator Associate (AZ-104 exam) - Windows Server Hybrid Administrator Associate (AZ-800 & AZ-801 exams) We need to preserve all detail, not invent. We'll put as

    • each bullet. Note: The parentheses about substitution are part of the content; keep them. REQUIRED CITIZENSHIP AND CLEARANCE: - Must be a U.S. Citizen - Secret security clearance is required with T5 or equivalent (SSBI) investigation level. (Applicants selected either must currently possess a Secret clearance or will be subject to a government security investigation and must meet eligibility requirements to obtain clearance prior to commencement of employment and maintain a security clearance for access to classified information or Closed/Restricted Areas throughout duration of employment.) We'll put as
    • each. Now Skills: includes REQUIRED SKILLS & EXPERIENCE and DESIRED SKILLS AND EXPERIENCE. Extract REQUIRED SKILLS & EXPERIENCE: - Knowledge of IT systems and advance IT infrastructure concepts - Must be proficient in operating personal computers, computer software and standard office equipment. - Must have basic keyboarding skills and aptitude for neatness and accuracy in sorting. - Experience in automated installation methods and system imaging (e.g., SCCM, VMware) - Critical thinking - Proven problem solver DESIRED SKILLS AND EXPERIENCE: - Advance knowledge and certification in both Windows Server and RHEL is considered highly desired - Knowledge/Administration of Trellix, LogRhythm, and MDE - Proficiency in automation tools and scripting (e.g. PowerShell, Bash, Python) - VMare/Nutanix certification (note typo) - Experience with MECM - Knowledge in Cyber Security Methods and Techniques - Knowledge of DoW IT systems to include Windows, RHEL, and