Client Systems Administrator II/III

We need to output HTML fragment with sections: About the role, Responsibilities (What You'll Do), Requirements (Ideal Candidate? Actually "Ideal Candidate" includes Working Knowledge Of and Skill In; maybe combine as Requirements/Qualifications), Qualifications (Minimum Qualifications), Benefits (they mention benefits but no details; they say "Details are available on the benefits tab". Since no specific benefits listed, we should NOT create Benefits section because no real specific content. Pay/Schedule also not specific. So we include sections that have real content: About the role, Responsibilities, Requirements (maybe combine Ideal Candidate), Qualifications (Minimum Qualifications), Certification & Licensing Requirements (maybe part of Qualifications? Could be separate but we can include as Requirements). Also Working Conditions/Physical Requirements maybe as a section? It's substantive. Could be "Working Conditions". Also "What To Know Before Applying" includes deadline etc but that's application instructions; we should remove application instructions per rule: remove application instructions. So we drop that. Also "Desired (but Not Required) Attributes" could be part of Requirements or Qualifications. We'll include as part of Requirements maybe. We must not repeat job title as heading. Use

for section headings. We need to preserve all substantive information, not invent or summarize away detail. So we need to include all details from sections we keep. Let's extract content: About The Role paragraph(s): - The City of Bend is accepting applications for one (1), full-time Client Systems Administrator II or III position. - This is a FLSA Exempt (overtime in-eligible) position, represented by the City of Bend Employee Association (COBEA). - The City may use this job posting to create an eligibility list for future hiring purposes. - Please review the entire job posting, including the application requirements at the end. (but we drop application instructions later; still we can keep the sentence about reviewing? Might be considered boilerplate? It's about application requirements; we should drop application instructions. Probably drop that sentence.) - The Client Systems Administrator II/III is responsible for managing the City of Bend’s endpoint management platform and ensuring Windows devices are securely configured, updated, and supported throughout their lifecycle. - This role is instrumental in delivering modern device management solutions that improve security, operational efficiency, and the end-user experience. - This role offers the opportunity to help shape the future of endpoint management by driving modernization efforts, adopting cloud-first technologies, and implementing best practices that enhance security, reliability, and operational efficiency. - The Client Systems Administrator II provides skilled technical services in support of installation, configuration, testing, integration, and ongoing support for City applications or infrastructure within specialized departments and enterprise wide, requiring in-depth knowledge and understanding of the City’s platforms and environment in support of meeting availability and performance goals. - The Client Systems Administrator III is a professional/highly technical position providing highly skilled services in support of installation, configuration, testing, integration, and ongoing support for City applications or infrastructure within specialized departments and enterprise wide, requiring in-depth knowledge and understanding of the City’s platforms and environment in support of meeting availability and performance goals. - Classification Framework Client Systems Administrator II Client Systems Administrator III We should keep classification framework as maybe part of About the role? Could be separate but we can embed. Now Responsibilities (What You'll Do): List bullet points: - Design, create, maintain, and update Windows operating system images for new computer deployment and hardware refreshes - Deploy, configure, and manage applications using Microsoft Configuration Manager (SCCM) - Manage operating system and third-party application patching to maintain security, compliance, and system stability - Develop, implement, and maintain Group Policy Objects (GPOs) to enforce security standards and streamline endpoint configuration - Configure and manage Windows Defender Firewall policies and endpoint security settings in collaboration with the Information Security Manager - Administer and maintain Microsoft Active Directory-related endpoint configurations - Manage enterprise DNS infrastructure, including DNS zones, records, troubleshooting, and ensuring reliable name resolution across all platforms - Monitor endpoint health, deployment success, and compliance using reporting and monitoring tools - Troubleshoot complex endpoint management issues, software deployment, patching failures, and policy conflict - Develop and maintain documentation, standards, and operational procedures related to endpoint management Now we need to keep all. Ideal Candidate section: Paragraph: "The ideal candidate for either the Client Systems Administrator II or III will be a technology professional with previous endpoint administration experience, who enjoys solving complex technical challenges. Ideal candidates will have experience administering Microsoft Configuration Manager (SCCM/MECM) and/or Microsoft Intune in an enterprise environment, along with a strong understanding of Windows operating systems, software deployment, patch management, operation system imaging, Group Policy, DNS, Active Directory, and endpoint security. If you are customer-focused, eager to learn, and excited to help share the future of endpoint management at the City of Bend, this may be a great opportunity for you!" Then "Working Knowledge Of" list: - Enterprise Management technologies, including Microsoft SCCM/MECM, MDT, and Intune - Endpoint security best practices - Operating system image creation and deployment - Software packaging and distribution - Patch Management - Device lifecycle management - Modern cloud-based solutions Then "Skill In" list: - Ability to troubleshoot complex technical issues - Managing multiple priorities - Ability to identify opportunities to improve processes through automation and innovation - Working collaboratively across IT teams to deliver reliable, secure, and customer-focused technology services Then "Candidates who meet the listed minimum qualifications, including an equivalent combination of education and experience will be considered for an interview. Please ensure your application includes information about your education, relevant paid and unpaid work experience, and applicable licenses and certifications. Avoid referencing your resume in the job duties section of the application." This is application instructions; we should drop. Now Minimum Qualifications: - Client Systems Administrator II: - Bachelor’s degree (B.A./B.S.) from four-year college or university or an equivalent combination of education and experience that provides the required knowledge, skills, and abilities of the position - 2 to 3 years’ experience in a similar position and/or performing similar tasks - Client Systems Administrator III: - Bachelor’s degree (B.A./B.S.) from four-year college or university or an equivalent combination of education and experience that provides the required knowledge, skills, and abilities of the position - 4 to 5 years’ experience in a similar position and/or performing similar tasks Certification & Licensing Requirements: - Level 4 CJIS certification required within first 3 months of employment - Current and valid Driver's license per City policies outlined in the Employee Handbook Desired (but Not Required) Attributes: - Microsoft certification: Endpoint Administrator Associate, Administrator Expert, or Azure Administrator Associate - ITIL Foundation Certification, CompTIA Security+, Network+ - Relevant PowerShell or automation certifications Working Conditions/Physical Requirements: - Communicate with others verbally and in writing, including by phone, e-mail, or in person - Understand, remember, communicate and apply complex oral and/or written instructions and factual information - Remain in a stationary position (sitting or standing) for extended periods of time, occasionally stand, walk, stoop or kneel for extended periods of time - Exert up to 20 pounds of force occasionally and/or up to 10 pounds of force frequently, to lift, carry, push, pull or otherwise move objects - Maintain sustained concentration on computer screens and use keyboards and a variety of peripherals - Work is generally performed in an office setting We should not include Benefits section because no specifics. Now we need to output HTML fragment with

headings for each section we include. Potential sections: - About the role - Responsibilities - Ideal Candidate (maybe rename to Requirements or Qualifications? But we have separate Qualifications for minimum qualifications. Could combine Ideal Candidate and Desired Attributes under Requirements. But we need to follow instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but we can use others if needed? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should stick to those headings where applicable. We have About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only those that have real content. We have About the role, Responsibilities, Requirements (maybe combine Ideal Candidate + Desired Attributes), Qualifications (minimum qualifications), Skills (maybe Skill In list), Working Conditions maybe not in list but could be under Requirements? Not sure. Could create a section "Working Conditions" but not in examples; maybe better to put under Requirements or Qualifications? The instruction says prefer a few substantive sections over many thin ones. So we could combine Working Conditions into Requirements or Qualifications? But it's not really a requirement; it's about physical demands. Could be part of Requirements. However we have a separate "Skills" heading for Skill In list. So we can have sections: About the role, Responsibilities, Requirements (includes Ideal Candidate paragraph + Working Knowledge Of + Desired Attributes), Qualifications (minimum qualifications + Certification & Licensing), Skills (Skill In list), Working Conditions (maybe as its own section but not in examples; maybe we can omit? But it's substantive. Could be part of Requirements? Might be okay to add a section "Working Conditions" even if not in examples; instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive list. So we can add other headings if needed. But to be safe, we could incorporate Working Conditions into Requirements or Qualifications. However it's not a qualification; it's about physical demands. Could be part of Requirements (job requirements). I'd put it under Requirements. Thus sections: - About the role - Responsibilities - Requirements (includes Ideal Candidate paragraph, Working Knowledge Of, Desired Attributes, Working Conditions/Physical Requirements) - Qualifications (includes Minimum Qualifications for II and III, Certification & Licensing Requirements) - Skills (Skill In list) Check that we haven't missed any substantive info: The "Classification Framework" lines maybe could be part of About the role. We'll include them there. Now we need to format lists with

• . For prose use

  . We must not include application instructions, EEO, etc. We removed those. Now craft HTML. Let's write:

  About the role

  The City of Bend is accepting applications for one (1), full-time Client Systems Administrator II or III position. This is a FLSA Exempt (overtime in‑eligible) position, represented by the City of Bend Employee Association (COBEA). The City may use this job posting to create an eligibility list for future hiring purposes. The Client Systems Administrator II/III is responsible for managing the City of Bend’s endpoint management platform and ensuring Windows devices are securely configured, updated, and supported throughout their lifecycle. This role is instrumental in delivering modern device management solutions that improve security, operational efficiency, and the end‑user experience. This role offers the opportunity to help shape the future of endpoint management by driving modernization efforts, adopting cloud‑first technologies, and implementing best practices that enhance security, reliability, and operational efficiency. The Client Systems Administrator II provides skilled technical services in support of installation, configuration, testing, integration, and ongoing support for City applications or infrastructure within specialized departments and enterprise wide, requiring in‑depth knowledge and understanding of the City’s platforms and environment in support of meeting availability and performance goals. The Client Systems Administrator III is a professional/highly technical position providing highly skilled services in support of installation, configuration, testing, integration, and ongoing support for City applications or infrastructure within specialized departments and enterprise wide, requiring in‑depth knowledge and understanding of the City’s platforms and environment in support of meeting availability and performance goals. Classification Framework: Client Systems Administrator II; Client Systems Administrator III.

  Responsibilities

  • Design, create, maintain, and update Windows operating system images for new computer deployment and hardware refreshes