Endpoint Engineer

We need to output HTML fragment with sections: About the role? Actually we have "About Us" but we should not repeat job title. Use headings for sections: About the role? The posting includes "About Us" which is about company. Could map to "About the role"? But we should follow instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections have content. We have: - About Us (company description) -> could be "About the role"? Actually "About the role" is more about the position. But we have "Job Overview". That could be "About the role". We'll use "About the role" heading and put the Job Overview content there. - Responsibilities: we have "Responsibilities Essential Job Duties:" and then list of duties. Also "Key Responsibilities:" list. We'll combine into a

• list. - Requirements: we have "Job Requirements Mandatory" list. Also "Preferred". Could be under Requirements or Qualifications. We'll use "Requirements" heading for mandatory, maybe also "Qualifications" for preferred? But instruction says prefer few substantive sections. Could combine mandatory and preferred under Requirements with subheadings? But we cannot add extra headings beyond h3? We could still use

  for prose and

  for list. Could separate mandatory and preferred as separate
  with headings in

  ? Probably better to have "Requirements" for mandatory and "Preferred Qualifications" maybe as another section? But we have "Qualifications" as possible heading. Use "Qualifications" for preferred? Let's decide: Use "Requirements" for mandatory, "Qualifications" for preferred. Also "Skills" maybe for technical skills list. But we have many skills listed within requirements. Could put them under Skills. However we need to avoid thin sections. Let's think: The posting includes many technical skills: MECM, Intune, PowerShell, Python, M365, etc. Could be under Skills. But we also have mandatory education/experience, certifications, passport, travel, etc. Those are more requirements. So we can have: - About the role (Job Overview) - Responsibilities (list) - Requirements (mandatory: degree, experience, certifications, passport, travel, OS/hardware understanding, M365 experience, MECM/Intune, scripting, network concepts, communication, etc.) - Qualifications (preferred: certifications, virtualization, networking equipment, Solarwinds, Fortigate, TeamDynamix, DevOps/Agile/PM) - Skills (maybe we could merge with Requirements/Qualifications). But we already have technical skills in both. Could instead have a single "Requirements" section that includes both mandatory and preferred, but we need to avoid too thin. However we have a lot of content; splitting into two sections is fine. We must not include Benefits, Pay, Schedule because not specified. We must remove boilerplate: EEO, disclosures, privacy policy, etc. We must not include navigation, cookie, etc. We must preserve all substantive information. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. About Us paragraph: "When you work at Chugach Government Solutions (CGS), you join a proud legacy of supporting missions while sustaining culture. The federal division of Chugach Alaska Corporation, CGS has been supporting critical missions as a government contractor for over 25 years. Our focus is to support facility maintenance, IT/technical services, construction and education. We are proud to have built, and continue to foster, an incredibly talented team spanning across the globe in hundreds of different fields – each team member proud to serve our country with first-class business services, while also making a difference for our Chugach shareholders. At CGS, empowering employees is a part of our core, and that focus is one of the ways we build and foster high-performing teams. We empower our employees through competitive compensation and benefits package, professional growth opportunities, truthful communication, and more! If you are looking for an opportunity to serve something bigger than yourself; if you want your day job to be one that creates meaningful value; if you are looking for an environment that highly values employees and respects individual differences – then Chugach Government Solutions may be the right fit for you!" But this is about company, not role. However we could still put under "About the role"? Might be odd but okay. The instruction says use headings like About the role, Responsibilities, etc. So we will put company description under About the role? Might be better to put under "About the role" the Job Overview (which describes role). The About Us could be considered company overview; but we could still include it as part of About the role? Might be mixing. However we must preserve all substantive information; we can include About Us content under About the role heading as well, but it's not about the role. Could we add another heading like "About the company"? Not in allowed list but we could still use h3 for any heading? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive. Likely we should stick to those headings; we can omit About Us if not fitting. But we must preserve all substantive information; if we omit About Us, we lose that info. However maybe it's considered boilerplate? It's not boilerplate; it's company description. Might be considered relevant. Could we put it under "About the role" as a preamble? Might be acceptable. Alternatively we could create a section "About the company" but not in examples; risk of being considered not following instruction. Safer to include it under About the role. Thus About the role will contain both company description and job overview. Now Responsibilities: We have list under "Essential Job Duties:" with many bullet-like paragraphs each starting with a bold heading. We need to convert each to

  . Also there is "Key Responsibilities:" list with short phrases. We'll combine. Let's extract each duty: Essential Job Duties: - Hardware Services Program Ownership Manage the end-to-end IT Asset Lifecycle, including procurement coordination, imaging, deployment, and disposal in partnership with the ITAD vendor Maintain SOPs and governance artifacts for lifecycle processes and vendor interactions - Endpoint Imaging & Configuration (Current State) Administer MECM (Configuration Manager) for OS deployment: task sequences, WIMs, driver packages, PXE workflows, and Distribution Point health Validate imaging success rates and content freshness; troubleshoot OSD failures and coordinate fixes with vendor teams - Modern Provisioning & Endpoint Management (Future State) Design and lead the transition to cloud-based provisioning (e.g., Autopilot or equivalent) and Intune/MEM for compliance, configuration, and application delivery Define modernization roadmap, pilot cohorts, rollback plans, and cutover criteria; retire legacy OSD components as milestones are met - Patch & Vulnerability Management Own monthly patch cycles for OS and applications; manage pilot rings, maintenance windows, and rollback strategies Monitor compliance SLAs and remediate non-compliant devices; integrate vulnerability signals into remediation plans - Security & Compliance Implement and support endpoint security controls including Microsoft Defender for Endpoint, EDR agents, configuration baselines, application control, and privilege management Collaborate with Cybersecurity on Conditional Access, device risk signals, and incident response playbooks - Technical Escalation & End-User Support Serve as escalation point for complex hardware, software, and network issues Diagnose and resolve advanced Incidents and Service Requests; participate in Problem Management, Change Advisory Board, and other ITSM processes Lead and participate in root cause analysis and document corrective actions - Contract & Site Support Lead or support solution design and technical execution for CGS P&L efforts at DoD contract locations across the U.S. and abroad Collaborate with cross-functional teams to meet contract requirements, perform hardware/software deployments, and ensure smooth transition of services from incumbent providers - Automation & Scripting Develop automation using tools like PowerShell, Python, and PowerApps for packaging, policy updates, reporting, and bulk operations Contribute reusable scripts and runbooks to improve program efficiency - Documentation & Training Author and maintain technical documentation, SOPs, runbooks, and Knowledge Base articles Deliver training and enablement sessions for staff and end-users Provide audit evidence and compliance documentation - Cross-Functional Collaboration Partner with Digital Solutions and other CGS teams and partners to deliver integrated solutions Participate in enterprise projects impacting endpoint management, security posture, and user experience Then "Key Responsibilities:" list: - Endpoint reliability and security - Patch & Vulnerability compliance - Endpoint imaging and provisioning success - Escalation resolution and knowledge capture - Lifecycle management accuracy - Vendor performance and governance - Software installation and maintenance - Project support and execution - User training and support resources We can combine these as additional

  items. Now Requirements (mandatory): - Bachelor’s degree in Computer Science, Information Technology, or related field OR equivalent work experience - 5+ years in Information Technology field - CompTIA Sec+ or similar DoD 8140 - (451) Intermediate certification or ability to attain one within 90 days of hire. - CompTIA A+ (or better) - Microsoft 365 Certified: Administrator Expert MS-102 - Valid US Passport within 6 Months of Hire - Ability to gain access to US DOD Sites & Facilities - 10-20% Travel - Strong understanding of Operating Systems (Windows) - Strong understanding of common hardware (Dell workstations & peripherals) - Experience with M365 (SharePoint, OneDrive, Exchange, etc.) - Experience with MECM & Intune - Experience with PowerShell, Python, or other common scripting languages/tools - Familiarity with network concepts - Conduct research on emergent technologies and identify solutions to technology challenges - Communicate clearly and concisely, both orally and in writing. - Establish and maintain professional working relationships with internal and external customers. Now Qualifications (preferred): - Microsoft Certified: Identity and Access Administrator SC-300 - Microsoft Certified: Azure Administrator AZ-104 - Experience with Virtualization technologies (VMWare/Hyper-V) - Experience with Juniper and Cisco networking equipment & platforms - Experience with Solarwinds, Fortigate platforms - Experience with TeamDynamix or other ITSM platforms - Experience with DevOps, Agile, or Project Management Now Skills: Could be redundant. But we could omit Skills section and include technical skills within Requirements/Qualifications. However we have many technical skills already listed. Might be okay to not have separate Skills. We must not include Benefits, Pay, Schedule. Now we need to output HTML fragment with

  headings and

  • for lists,

    for prose. We'll structure:

    About the role

    ... company description + job overview ...

    Responsibilities

    • ... each duty ...
    ...

    Requirements

    • ... each mandatory ...
    ...

    Qualifications

    • ... each preferred ...
    ...
    We need to ensure we preserve all substantive information. Let's craft the prose for About the role: combine About Us and Job Overview. About Us paragraph as is. Job Overview: "The Endpoint Engineer is accountable for the reliability, security, lifecycle, and support of end-user devices, systems, and services across the enterprise. This role owns the Hardware Services program, including current-state MECM imaging and OSD