Senior Server Administrator

We need to produce HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: - Intro: "Step into your future as a Senior Server Administrator! In this role, you will maintain and optimize our infrastructure, focusing on identity management, Microsoft 365 administration, virtualization, and security. You will support both customer and internal applications, collaborating with teams across multiple locations. We are seeking applicants with strong technical expertise, a proactive mindset, and a passion for process improvement." This could be About the role. - "What You Will Be Doing" list: many bullet points. That's Responsibilities. - "What You Will Likely Bring": list of experience/skills. That's Requirements/Qualifications/Skills. We need to decide mapping. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can include multiple of those if content exists. We need to avoid filler. We have content for Requirements (5+ years experience...), Qualifications (maybe same), Skills (PowerShell, etc). Could combine into Requirements and Skills. But we need to not repeat same content. Let's parse: "What You Will Likely Bring" includes: - 5+ years’ experience in server administration, with demonstrated success in identity management, authentication, single sign-on, multi-factor authentication, and Entra Active Directory. - Strong Microsoft 365 administration skills, including Teams, OneDrive, and Office suite. - Familiarity with virtualization technologies, such as VMware and Hyper-V. - Proficiency in PowerShell scripting. - Understanding of identity and access management concepts and best practices. - Demonstrated history of leading projects. - Subject matter expertise in several of the following technologies: (list many) That seems like Requirements and Skills combined. Could split: Requirements = years experience, Microsoft 365, virtualization, PowerShell, IAM concepts, leading projects. Skills = the list of technologies (RHEL, RH Satellite, backup solutions, SAN networking, TLS cert lifecycle, networking, data center hardware, multiple hypervisors). But the instruction says prefer a few substantive sections over many thin ones. Maybe we just have Requirements (including experience and skills) and Skills separate if needed. But we have also "What Could Set You Apart" which is additional nice-to-have. Could be Skills or Qualifications. We also have "About Epicor" which is company description; could be About the role? Actually About the role is about the role, not company. The intro is about role. The "About Epicor" is company overview; could be omitted as boilerplate? It's not exactly boilerplate but it's company description. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Epicor" is not those; it's company description. Could be included as a section? Not in the list of allowed headings. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not add a section for About Epicor. We could incorporate that into About the role? But About the role should be about the role, not company. However we could treat the intro as About the role and ignore the Epicor description (maybe it's considered boilerplate? It's not exactly boilerplate but it's generic company description; maybe we can drop it as not required). The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Dropping the Epicor description might lose substantive info about company. But the allowed headings don't have a company section; maybe we can include it as part of About the role (though it's not strictly about role). Could be okay. We also have "Competitive Pay & Benefits" with subpoints: Health and Wellness, Internal Mobility, Career Development, Inclusive Workplace, Work-Life Balance, Global Mobility. That's Benefits. Also Pay range: Range Minimum: $105,000 USD Maximum: $178,000 USD. That's Pay. Also note about salary range disclaimer; we should include the range but not the disclaimer? The disclaimer is substantive? It says "The salary range provided reflects the national average for this job title and does not represent compensation specific to Epicor Software Corporation. Actual compensation will vary based on experience, qualifications, and market factors relevant to the position." That's also substantive about pay. We could include it in Pay section. Schedule: The posting mentions "Participate in a 24x7 on-call rotation". That's schedule info. So we can have Schedule section with that detail. Now we need to output HTML fragment with headings

for each section, and

• for lists,

  for prose. We must not repeat job title as heading. No Job ID etc. We must not include sections with filler like "commensurate with experience". We have actual content. We must not include boilerplate like EEO etc. There's an "Equal Opportunities and Accommodations Statement" which is EEO boilerplate; we must remove that. Also "Recruiter Mouy Bun" maybe metadata; we can drop. Now structure:

  About the role

  Step into your future as a Senior Server Administrator! In this role, you will maintain and optimize our infrastructure, focusing on identity management, Microsoft 365 administration, virtualization, and security. You will support both customer and internal applications, collaborating with teams across multiple locations. We are seeking applicants with strong technical expertise, a proactive mindset, and a passion for process improvement.

  Maybe also include About Epicor? Could add after that as part of About the role? Might be stretching. But we could add a second paragraph about Epicor: "At Epicor, we’re truly a team..." etc. That is substantive. Let's include it as part of About the role. Thus About the role will have two paragraphs: intro role description and company description. Now Responsibilities: from "What You Will Be Doing". We'll list each bullet as
• . Responsibilities list: - Administer and maintain identity and access management systems, including Entra Active Directory, multi-factor authentication, and single sign-on. - Manage Microsoft 365 services, including Teams, OneDrive, and Office suite, and configure OAuth workflows. - Support virtualization platforms, such as VMware and Hyper-V. - Participate in a 24x7 on-call rotation and respond to infrastructure incidents and critical outage calls. - Collaborate with cross-functional teams across Austin, Irvine, and remote locations. - Contribute to security and compliance efforts, including SOX and audit reporting. - Document processes and share knowledge across the team. - Serve as a subject matter expert for VMware and Microsoft Windows administration. - Work tickets from a service desk queue and use scripting technologies to automate tasks. - Partner with vendors and other teams to architect and implement solutions. - Document design and support procedures for routine tasks to leverage Tier 1 and Tier 2 support. - Lead and participate in process improvement, solutions implementation, and project leadership. Now Requirements: from "What You Will Likely Bring" first part maybe up to "Demonstrated history of leading projects." We'll treat as Requirements. List: - 5+ years’ experience in server administration, with demonstrated success in identity management, authentication, single sign-on, multi-factor authentication, and Entra Active Directory. - Strong Microsoft 365 administration skills, including Teams, OneDrive, and Office suite. - Familiarity with virtualization technologies, such as VMware and Hyper-V. - Proficiency in PowerShell scripting. - Understanding of identity and access management concepts and best practices. - Demonstrated history of leading projects. Now Skills: from the "Subject matter expertise in several of the following technologies:" list. List: - Red Hat Enterprise Linux (RHEL) and RH Satellite - Backup and recovery solutions (Commvault, Cohesity) - SAN networking - TLS certificate lifecycle management automation - Networking (DNS, DHCP, VLANs, VMware VDS) - Data center hardware (servers, storage, networking) - Multiple hypervisors (e.g., Proxmox, OpenShift, Hyper-V) Now maybe also include "What Could Set You Apart" as additional Skills or Qualifications. Could be added to Skills as extra bullet points. But we already have Skills section; we could add those as additional bullet points under Skills. However the instruction: prefer a few substantive sections over many thin ones. Adding more bullets to Skills is fine. Thus Skills bullets will include both the subject matter expertise list and the "What Could Set You Apart" list. What Could Set You Apart: - Experience with G Suite, including migration into Microsoft 365. - Citrix experience. - Experience with automation tools. - Teams administration in a multi-geo enterprise environment. - Exposure to hybrid environments, including on-premises Active Directory. - History of automating routine tasks and commitment to creating documentation. - Passion for learning new technology. We'll combine. Now Benefits: from "Competitive Pay & Benefits" bullet points. List: - Health and Wellness: Comprehensive health and wellness benefits designed to support your overall well-being. - Internal Mobility: Opportunities for mentorship, continuing education, and focused career goal setting, with 25% of positions filled internally. - Career Development: Free LinkedIn Learning licenses for everyone, along with our Mentoring Program to boost your personal development. - Inclusive Workplace: Collaborate with a diverse team in an inclusive, global workplace that fosters innovation and celebrates partnership. - Work-Life Balance: Policies built on mutual trust and support, encouraging time off to rest, recharge, and reconnect. - Global Mobility: Comprehensive support for international relocations and permanent residency processes. Now Pay: from salary range and disclaimer. We'll put

  with the range and note. Pay: Range Minimum: $105,000 USD Maximum: $178,000 USD. The salary range provided reflects the national average for this job title and does not represent compensation specific to Epicor Software Corporation. Actual compensation will vary based on experience, qualifications, and market factors relevant to the position. Now Schedule: from "Participate in a 24x7 on-call rotation and respond to infrastructure incidents and critical outage calls." That's already in Responsibilities but we can also note schedule. However we should not duplicate content. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we already included that bullet in Responsibilities, we can still have Schedule section referencing on-call rotation. But that would duplicate the same sentence. Duplication is to be avoided? The instruction says remove duplicated lines. So we should not duplicate the same sentence. So we need to decide: either keep the on-call bullet only in Responsibilities and not have a Schedule section, or keep it only in Schedule and remove from Responsibilities. Which is better? The Schedule section is specifically for schedule info; the Responsibilities section already includes many duties; the on-call rotation is a duty but also schedule. We could keep it in Responsibilities and not have a Schedule section, because we already have that info. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". If we don't have separate schedule content beyond what's already in Responsibilities, we could omit Schedule section. However the posting does have schedule info (24x7 on-call rotation). It's specific. But we already used it in Responsibilities. If we omit Schedule, we still preserved the info (in Responsibilities). That's okay. The instruction does not require that each piece of info appears only once; it just says don't duplicate lines. Duplicating the same line would be duplicate. So we should avoid duplicating the exact sentence. We can keep it in Responsibilities and not have Schedule. That satisfies preserving info without duplication. Thus we will not include Schedule section. Now Benefits: we have content. Now we need to ensure we don't include any