Senior Network Systems Administrator

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (or Skills and Qualifications), Benefits, maybe Pay/Schedule only if present. The posting includes location, shift, company, but we should not repeat job title as heading. We can include location and shift in a short paragraph maybe under a heading? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have sections: About the role, Responsibilities, Skills and Qualifications (or Requirements), Benefits. Also maybe "Location and Shift" not required; we can embed in a paragraph under About the role or separate? The instruction says include a section ONLY when posting has real, specific content for it. Location and shift are present, but not listed as a standard heading; we could put them in a

before sections. Not required to have a heading for them. We must remove boilerplate like EEO, etc. There's none. We need to preserve all substantive information. Let's extract: About The Role: Provides technical maintenance and recovery support to the firm’s information technology systems, Active Directory, Microsoft Exchange, Privileged Access Management (PAM), Identity and Access Management (IAM). Uses a variety of testing tools and techniques to troubleshoot and resolve complex technical problems associated with the system’s hardware and software. Interfaces with vendors and maintenance providers to service and maintain the system, implement necessary measures to limit the system’s downtime, provide technical support to optimize system performance. Job Duties And Responsibilities: list items: - Provide planning reports for audits, governance risk compliance, Sr management, access, changes made, performance, and capacity. - Provides technical maintenance and recovery support to the firm’s local or wide area networks and technology systems. - Perform support and administration for network related systems. - Test and troubleshoot to resolve complex technical problems associated with the system’s hardware and software. - Complete work orders as assigned. - Provide assistance to department management and train/mentor Systems Administrators. - Direct and monitor tasks assigned to Systems Administrators. - Facilitate and coordinate projects. Report progress to management. - Serve as department representative on committees and tasks forces, as assigned. - Participate in on-call support rotations and provide after-hours support as required. Skills And Qualifications: list items (some are sentences). We'll need to put them in

• . List: - Experience coordinating large complex technical projects. - Prior experience communicating with multiple departments at a technical level. - Technical expertise building, configuring and maintaining various systems within a data center environment. - Experience working with technical platforms and installing related operating systems, updates and platform hardening. - Effective communication skills to inform others when action is required to respond to technology system issues. - Attention to detail and ability to identify when IT systems are not operating optimally. - Able to adjust to new conditions, challenges, or changes with flexibility and a positive attitude. - Manages time, tasks, and resources efficiently to maintain structure, meet deadlines, and achieve goals. - High school diploma or equivalent is required; associate or bachelor’s degree in information technology, Computer Science, Cybersecurity, or a related field and 3-5 years of IT experience preferred. - 3-5 years of experience administering enterprise Microsoft infrastructure, including Active Directory and Exchange Environments. - 3-5 years of experience supporting Identity and Access Management (IAM) solutions. - Experience with Privileged Access Management (PAM), privileged account governance, and security administration strongly preferred. - Minimum of 7 years previous work experience of installation, configuration, troubleshooting, repair, supporting, administering, design and planning in LAN/WAN environment. - Cisco CCNA, Cisco CCNE, or Microsoft MCSE certification preferred or any additional industry recognized certifications. - Advanced knowledge of Microsoft Active Directory Domain Services, Group Policy, DNS, DHCP, and enterprise identity management. - Previous experience with Microsoft network operating systems, Novell, Unix, Linux, and TCP/IP, IPX/SPX, and related network protocols also preferred. - 3-5 years’ working experience while holding a MSCA, and/or MCSE certification, and/or CCNA, and/or CCNP certifications, preferred. - Working knowledge of Microsoft Entra ID (Azure AD), Conditional Access, Multi-Factor Authentication (MFA), and Single Sign-On (SSO). - Experience with PowerShell automation and scripting for administration, reporting, and operational efficiency. Benefits: list: - Full medical benefits when working 20+ hours per week - Traditional and High-Deductible health plan options available - FREE dental and vision coverage - Generous Paid Time Off plans - 401(k) – dollar-for-dollar match up to 5% of total compensation - Special discounts and offers for events at the Denny Sanford PREMIER Center - PREMIER Wellness Program - Paid Community Volunteer Hours – PREMIER averages 30,000 hours per year - Fun Employee Parties Also culture description maybe not needed as separate section; but could be included in About the role? The posting includes culture earlier but we can maybe include a short paragraph about culture under About the role or separate? The instruction: "Prefer a few substantive sections over many thin ones." Could combine culture into About the role? But About the role already defined. Could add a section "Our Culture" if we want, but not required. The posting includes culture description: "At First PREMIER Bank and PREMIER Bankcard, we’ve created a culture that emphasizes personal success, respect, health, and wellness, fun and giving back. This is an environment where you will be rewarded, valued, and celebrated for your hard work. We offer a robust and expanded package of health benefits, incentives, paid time off and growth and career advancement opportunities. We celebrate our employees and show our appreciation with private concerts, outdoor bashes, cash and car giveaways and more! See some of our epic celebrations and employee recognitions. Considered one of the nation’s strongest financial organizations, we’ve achieved our success by embodying the views and values of The PREMIER Way. From our CEOs to the newest hires, we all follow these shared views and values to guide us on how to treat our customers, co-workers and communities. The PREMIER Way also serves as a roadmap on how to be successful inside and outside of the workplace. We believe in investing in our employees, their families and our communities." That's substantive; we could make a section "About the Company" or "Culture". But the allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Not "Culture". However we could incorporate that content into About the role or Benefits? Probably better to add a section "About the Company" but not in allowed list; but instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not exclusive. So we could add other headings if needed, but better to stick to those. The culture description is somewhat overlapping with Benefits (they mention benefits, incentives, PTO, growth, celebrations). Could merge into Benefits section? But Benefits already list specific benefits; culture description is more about values. Could add a section "Our Culture" as a heading; it's not prohibited. The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, just gives examples. So we can add a section for Culture if we want. However they say "Prefer a few substantive sections over many thin ones." Adding a Culture section may be okay. But we also have location and shift: "Location: Sioux Falls, SD Shift: Monday - Friday 8:00 AM to 5:00 PM Company: PREMIER Bankcard". Could put that in a paragraph before sections. We must not repeat job title as heading. No job title given explicitly; we can ignore. We must not include Job ID/requisition numbers. We must remove duplicated lines: there may be duplicated sentences like "Provides technical maintenance and recovery support to the firm’s information technology systems..." appears both in About The Role and in Job Duties. We need to preserve all substantive information; but we should not duplicate content. We should deduplicate. So we need to combine and avoid repeating same sentence. Let's craft:

  Location: Sioux Falls, SD. Shift: Monday - Friday, 8:00 AM to 5:00 PM. Company: PREMIER Bankcard.

  Then

  About the Role

  with paragraph summarizing the role (unique content). We'll combine the About The Role description (first paragraph) and maybe mention that it includes technical maintenance and recovery support etc. We'll not repeat the duty that appears later. Then

  Responsibilities

  with
  • list of duties (unique). We'll need to ensure we don't repeat the About the Role sentence. Then

    Skills and Qualifications

    with
    • list. Then

      Benefits

      with
      • list. Optionally

        Our Culture

        with paragraph. But we need to avoid filler like "commensurate with experience". Not present. Let's produce HTML. Check for any duplicated content: The About The Role sentence: "Provides technical maintenance and recovery support to the firm’s information technology systems, Active Directory, Microsoft Exchange, Privileged Access Management (PAM), Identity and Access Management (IAM). Uses a variety of testing tools and techniques to troubleshoot and resolve complex technical problems associated with the system’s hardware and software. Interfaces with vendors and maintenance providers to service and maintain the system, implement necessary measures to limit the system’s downtime, provide technical support to optimize system performance." In Responsibilities list we have: "Provides technical maintenance and recovery support to the firm’s local or wide area networks and technology systems." That's similar but not identical (local/wide area networks vs information technology systems). It's a bit different; we can keep both. But there is also "Test and troubleshoot to resolve complex technical problems associated with the system’s hardware and software." which duplicates the "Uses a variety of testing tools and techniques to troubleshoot and resolve complex technical problems associated with the system’s hardware and software." Slightly different phrasing but same meaning. Might be considered duplicate. We should avoid near-duplicate. Perhaps we can keep one version. Since the instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we remove one, we might lose detail? The detail is essentially same: testing/troubleshooting. Could keep one. I'd keep the more detailed from About the Role? Actually About the Role says "Uses a variety of testing tools and techniques to troubleshoot and resolve complex technical problems associated with the system’s hardware and software." Responsibilities list says "Test and troubleshoot to resolve complex technical problems associated with the system’s hardware and software." The former adds "Uses a variety of testing tools and techniques". That's extra detail. So we can keep the About the Role sentence and drop the simpler one from responsibilities. Similarly, "Provide planning reports for audits, governance risk compliance, Sr management, access, changes made, performance, and capacity." is unique. "Perform support and administration for network related systems." unique. "Complete work orders as assigned." unique. "Provide assistance to department management and train/mentor Systems Administrators." unique. "Direct and monitor tasks assigned to Systems Administrators." unique. "Facilitate and coordinate projects. Report progress to management." unique. "Serve as department representative on committees and tasks forces, as assigned." unique. "Participate in on-call support rotations and provide after-hours support as required." unique. Now Benefits list: ensure no duplicates. Now Skills list: need to ensure no duplicates. There's some overlapping like "Experience coordinating large complex technical projects." and "Prior experience communicating with multiple departments