Senior System Administator - TS/SCI Clearance

We need to output only HTML fragment, using

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where posting has real specific content. No filler like "commensurate with experience". Must preserve all substantive info, no invented. Remove boilerplate like EEO, navigation, legal, etc. Also remove application instructions. The posting includes: description of role, responsibilities (What You Will Do), expectations (What We Expect Of You), plus Pay range, Benefits overview link, maybe schedule not mentioned. Also includes "About Us" and AI stuff, but those are boilerplate? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Us" and AI forward statements might be considered boilerplate? Not exactly EEO but could be considered company description; maybe we keep? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The "About Us" and AI forward are substantive? They are generic marketing but maybe considered boilerplate? The instruction only mentions removing cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we can keep "About Us" and AI forward if they are not those categories. However they might be considered fluff but not prohibited. However we need to decide sections: we have responsibilities (What You Will Do) -> Responsibilities section. Expectations (What We Expect Of You) -> could be Requirements or Qualifications. The posting lists many expectations: clearance, citizenship, experience, skills, certifications, etc. Those could go under Requirements or Qualifications. We need to decide which headings to use. The allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can combine some. For clarity: About the role could be a brief summary of the role (first paragraph). Responsibilities: the bullet list of duties. Requirements: maybe the mandatory requirements (clearance, citizenship, years experience, etc). Qualifications: maybe the preferred qualifications (certifications, plus experience with virtualization, etc). Skills: maybe technical skills list. Benefits: we have benefits overview link. Pay: we have pay range. Schedule: not mentioned, so omit. We must not repeat job title as heading. No Job ID. We must output only HTML fragment, no markdown fences. We need to use

for each section heading, then content:

for prose,

• for lists. We need to preserve all substantive information: include details like TS/SCI clearance required, US citizenship, 8+ years experience, etc. Also include the list of responsibilities exactly as given (but we can format as list). Must not invent or summarize away detail. So we need to include each responsibility item as a list item. Similarly for expectations: list each expectation. We must not include boilerplate like "CDW is an equal opportunity employer." That's EEO boilerplate, must remove. Also remove the "About Us" and AI forward? Those are not EEO but maybe considered company description; but they might be considered fluff but not prohibited. However they are not part of role specifics; they are generic marketing. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The "About Us" and AI forward are substantive? They are about the company, not the job. Might be considered boilerplate but not explicitly listed for removal. However typical job postings include such sections; but the instruction didn't say to remove company description. It only listed cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we can keep them. However they might be considered duplicated lines? Not really. But we need to decide sections: About the role could include the first paragraph describing the role. Could also include the "About Us" and AI forward? Probably not; better to keep About the role as the role description. The "About Us" and AI forward could be omitted as they are not directly about the role; but they are not prohibited. However to keep output concise and focused, we might omit them. The instruction says preserve ALL substantive information; if we omit them, we are removing substantive info (about company). But is that considered substantive? It's about the company, not the job. The instruction didn't explicitly require to keep company description. It said preserve ALL substantive information; do NOT invent or summarize away detail. If we omit company description, we are summarizing away detail (removing). So we should keep it. However we could place it under a section like "About the role"? That might be misfit. Perhaps we can add a section "About CDW" but not allowed headings. Only allowed headings are those listed. So we cannot add a custom heading. We could incorporate it into "About the role" section, but that would mix role description with company description. Might be okay. Alternatively we could omit it and risk violating "preserve ALL substantive information". But maybe the evaluator expects we remove generic marketing fluff as boilerplate. The instruction only mentions specific boilerplate types; company description not listed. So safer to keep it. Thus we will include a section "About the role" containing the initial paragraph: "The Senior System Administrator will support the administration, maintenance, security, and optimization of mission-critical Windows-based infrastructure in a secure federal environment. This role requires an experienced administrator with strong technical troubleshooting skills, a proactive approach to system performance and reliability, and the ability to operate effectively in environments requiring an active Top Secret/Sensitive Compartmented Information (TS/SCI) clearance." Then Responsibilities: list from "What You Will Do". We'll convert each sentence into list items. Then Requirements: mandatory items: Active TS/SCI clearance required at time of hire; U.S. citizenship required; 8+ years relevant experience; Strong hands-on experience administering Microsoft Windows Server and Windows workstation environments; Experience with Active Directory, Group Policy, DNS, DHCP, domain services, user permissions, enterprise authentication; Experience with patching, vulnerability remediation, system hardening, applying secure configuration baselines; Ability to troubleshoot complex hardware, software, OS, authentication, network-related issues; Experience supporting secure or classified environments, including adherence to change management and documentation requirements; Strong written and verbal communication skills, ability to document procedures and brief technical status to stakeholders. Then Qualifications: preferred qualifications (plus): DoD 8570/8140 IAT Level II certification, such as Security+ CE, or ability to obtain/maintain required compliance certification; Experience with VMware, Hyper-V, Nutanix, or other enterprise virtualization platforms; Experience with Microsoft Endpoint Configuration Manager, SCCM, MECM, PDQ Deploy, or similar software deployment tools; Familiarity with ACAS/Nessus vulnerability findings, HBSS/ESS tools, STIG Viewer, and remediation tracking; Experience creating or maintaining Windows images, deployment packages, automated build processes; Working knowledge of backup and recovery processes, disaster recovery planning, continuity of operations support; Experience supporting IIS, file services, print services, certificate services, or other Microsoft enterprise services. Then Skills: maybe we can list technical skills: PowerShell or other scripting tools to automate routine administration, reporting, software deployment, maintenance tasks; etc. But we already covered many skills in requirements/qualifications. Could combine. But we need to avoid duplication. Perhaps we can put technical skills under Skills: PowerShell scripting, etc. However the posting mentions "Use PowerShell or other scripting tools to automate routine administration, reporting, software deployment, and maintenance tasks." That's a responsibility, not a skill. Could be placed under Responsibilities. Better to follow the posting: Responsibilities list includes that item. So we don't need separate Skills. Thus we may omit Skills section if no specific skills list beyond those already covered. But we could still include a Skills section summarizing technical skills: Windows Server, AD, GPO, DNS, DHCP, PowerShell, etc. However that would be summarizing, potentially losing detail. The instruction says preserve ALL substantive information; we can keep details in Responsibilities and Requirements/Qualifications. So we may not need Skills. Benefits: we have "Benefits overview: https://cdw.benefit-info.com/" plus maybe mention "Salary ranges may be subject to geographic differentials". Also "Pay range: $175,000 - $220,000 depending on experience and skill set". So we need Benefits and Pay sections. Schedule: not mentioned, omit. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. We need to ensure we don't include filler like "commensurate with experience". Not present. Now format. We'll use

  About the role

  then

  ...

  . Responsibilities:

  Responsibilities

  then
  • ... each item. We need to split the responsibilities into items. Let's list them from the posting: - Administer, maintain, and troubleshoot Windows Server and Windows desktop environments across classified or secure enterprise networks. - Manage Active Directory, Group Policy Objects, DNS, DHCP, user accounts, security groups, organizational units, and domain controller operations. - Perform system monitoring, performance tuning, capacity planning, patch management, vulnerability remediation, and root cause analysis. - Install, configure, upgrade, and support operating systems, enterprise applications, server hardware, and virtualized infrastructure. - Develop, maintain, and execute standard operating procedures for system builds, configuration baselines, software deployments, and maintenance activities. - Support compliance with applicable security standards, including DISA STIGs, vulnerability scan remediation, change control, and configuration management requirements. - Provide Tier II/III support for escalated incidents involving servers, workstations, applications, authentication, permissions, and enterprise services. - Use PowerShell or other scripting tools to automate routine administration, reporting, software deployment, and maintenance tasks. - Coordinate with cybersecurity, network, engineering, and help desk teams to support secure and reliable system operations. - Mentor junior administrators and provide technical guidance on troubleshooting, documentation, and operational best practices. That's 10 items. Now Requirements (mandatory): - Active TS/SCI clearance is required at the time of hire. - U.S. citizenship is required due to federal contract and clearance requirements. - 8+ years of relevant experience in systems administration, infrastructure operations, or enterprise IT support. - Strong hands-on experience administering Microsoft Windows Server and Windows workstation environments. - Experience with Active Directory, Group Policy, DNS, DHCP, domain services, user permissions, and enterprise authentication. - Experience with patching, vulnerability remediation, system hardening, and applying secure configuration baselines. - Ability to troubleshoot complex hardware, software, operating system, authentication, and network-related issues. - Experience supporting secure or classified environments, including adherence to change management and documentation requirements. - Strong written and verbal communication skills, with the ability to document procedures and brief technical status to stakeholders. That's 9 items. Now Qualifications (preferred/plus): - DoD 8570/8140 IAT Level II certification, such as Security+ CE, or the ability to obtain/maintain required compliance certification, is a plus. - Experience with VMware, Hyper-V, Nutanix, or other enterprise virtualization platforms, is a plus. - Experience with Microsoft Endpoint Configuration Manager, SCCM, MECM, PDQ Deploy, or similar software deployment tools, is a plus. - Familiarity with ACAS/Nessus vulnerability findings, HBSS/ESS tools, STIG Viewer, and remediation tracking, is a plus. - Experience creating or maintaining Windows images, deployment packages, and automated build processes, is a plus. - Working knowledge of backup and recovery processes, disaster recovery planning, and continuity of operations support, is a plus. - Experience supporting IIS, file services, print services, certificate services, or other Microsoft enterprise services, is a plus. That's 7 items. Now Benefits: - Benefits overview: https://cdw.benefit-info.com/ - Salary ranges may be subject to geographic differentials We could also include