Senior Server Administrator
Epicor · Austin, TX · 1 mo ago
HybridInformation Technology$105k/yrFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate.
We need to parse the posting.
Content:
- 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."
That's prose about the role. Could be "About the role" section.
- "What You Will Be Doing" list: bullet points (actually sentences separated by periods). We'll convert to
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate.
We need to parse the posting.
Content:
- 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."
That's prose about the role. Could be "About the role" section.
- "What You Will Be Doing" list: bullet points (actually sentences separated by periods). We'll convert to - .
List items:
- 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.
- "What You Will Likely Bring": list of qualifications/experience.
List items:
- 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:
- 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)
We need to decide how to format nested list? Probably just separate items; but we can keep sub-bullets as separate
- with indentation? Simpler: treat each bullet as
- . For the sublist, we could embed
inside - . But spec says use
- for any list of duties/requirements/benefits. It doesn't forbid nested lists. We'll do nested.
- "What Could Set You Apart": list of desirable extras.
List items:
- 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.
- "About Epicor": prose about company.
- "Competitive Pay & Benefits": then bullet list of benefits.
List items:
- 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.
Also there is a salary range: "Range Minimum: $105,000 USD Maximum: $178,000 USD". That's Pay info. Also note: "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." We should include Pay section with that info. Since they said include Pay section only if posting actually states them. Yes they state range. So we include Pay.
Schedule: Not mentioned besides "Participate in a 24x7 on-call rotation". That's schedule info? Could be considered schedule. But they didn't give explicit schedule like "Full-time". Might not create Schedule section unless explicit. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. They gave schedule info (24x7 on-call rotation) but not a schedule like "Full-time". Might still be considered schedule? Safer to not create Schedule section unless explicit schedule like "Full-time", "Part-time", "Shift". We'll omit Schedule.
Benefits: we have list; include Benefits section.
Now we need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. However we need to avoid thin sections. We have multiple lists that could map to these headings.
We need to decide mapping:
- About the role: intro paragraph.
- Responsibilities: "What You Will Be Doing" list.
- Requirements: "What You Will Likely Bring" list (core qualifications).
- Qualifications: maybe "What Could Set You Apart" (preferred qualifications). Could also be Skills. But we have both Requirements and Qualifications; we could treat "What You Will Likely Bring" as Requirements, and "What Could Set You Apart" as Qualifications (or Skills). However we also have technical skills like PowerShell etc inside Requirements. Might be okay.
Alternatively we could combine Requirements and Qualifications into one section, but instruction: prefer a few substantive sections over many thin ones. We have many sections already; maybe we can combine some.
We have: About the role, Responsibilities, Requirements (core), Preferred Qualifications (What Could Set You Apart), Benefits, Pay. That's 6 sections. Could be okay.
We also have About Epicor company description; could be part of About the role or separate "About Epicor". But we already have About the role for role description; we could add a section "About Epicor" but that's not in the allowed headings list? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Not About Epicor. So we should incorporate About Epicor prose into About the role or maybe as a separate paragraph under About the role. Since we cannot create a heading not in list. So we will add About Epicor content to About the role section (maybe after intro). That's fine.
Thus About the role will contain intro paragraph + About Epicor paragraph.
Now we need to ensure we don't include boilerplate like Equal Opportunities statement, Recruiter Mouy Bun, etc. Remove those.
Also remove "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." We'll keep the range and maybe a brief note that actual compensation varies? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the salary range and the note about it being national average and actual compensation varies. That's substantive. So include in Pay section.
Now we need to output only HTML fragment, no /, no markdown fences.
We'll produce something like:
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.
At Epicor, we’re truly a team. Join 5,000 talented professionals in creating a world of better business through data, AI, and cognitive ERP. We help businesses stay future-ready by connecting people, processes, and technology. From software engineers who command the latest AI technology to business development reps who help us seize new opportunities, the work we do matters. Together, Epicor employees are creating a more resilient global supply chain. We’re Proactive, Proud, Partners. Whatever your career journey, we’ll help you find the right path. Through our training courses, mentorship, and continuous support, you’ll get everything you need to thrive. At Epicor, your success is our success. And that success really matters, because we’re the essential partners for the world’s most essential businesses—the hardworking companies who make, move, and sell the things the world needs.
Responsibilities
- 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.
Requirements
- 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:
- 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
- inside
- . But spec says use
- for any list of duties/requirements/benefits. It doesn't forbid nested lists. We'll do nested.
- "What Could Set You Apart": list of desirable extras.
List items:
- 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.
- "About Epicor": prose about company.
- "Competitive Pay & Benefits": then bullet list of benefits.
List items:
- 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.
Also there is a salary range: "Range Minimum: $105,000 USD Maximum: $178,000 USD". That's Pay info. Also note: "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." We should include Pay section with that info. Since they said include Pay section only if posting actually states them. Yes they state range. So we include Pay.
Schedule: Not mentioned besides "Participate in a 24x7 on-call rotation". That's schedule info? Could be considered schedule. But they didn't give explicit schedule like "Full-time". Might not create Schedule section unless explicit. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. They gave schedule info (24x7 on-call rotation) but not a schedule like "Full-time". Might still be considered schedule? Safer to not create Schedule section unless explicit schedule like "Full-time", "Part-time", "Shift". We'll omit Schedule.
Benefits: we have list; include Benefits section.
Now we need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. However we need to avoid thin sections. We have multiple lists that could map to these headings.
We need to decide mapping:
- About the role: intro paragraph.
- Responsibilities: "What You Will Be Doing" list.
- Requirements: "What You Will Likely Bring" list (core qualifications).
- Qualifications: maybe "What Could Set You Apart" (preferred qualifications). Could also be Skills. But we have both Requirements and Qualifications; we could treat "What You Will Likely Bring" as Requirements, and "What Could Set You Apart" as Qualifications (or Skills). However we also have technical skills like PowerShell etc inside Requirements. Might be okay.
Alternatively we could combine Requirements and Qualifications into one section, but instruction: prefer a few substantive sections over many thin ones. We have many sections already; maybe we can combine some.
We have: About the role, Responsibilities, Requirements (core), Preferred Qualifications (What Could Set You Apart), Benefits, Pay. That's 6 sections. Could be okay.
We also have About Epicor company description; could be part of About the role or separate "About Epicor". But we already have About the role for role description; we could add a section "About Epicor" but that's not in the allowed headings list? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Not About Epicor. So we should incorporate About Epicor prose into About the role or maybe as a separate paragraph under About the role. Since we cannot create a heading not in list. So we will add About Epicor content to About the role section (maybe after intro). That's fine.
Thus About the role will contain intro paragraph + About Epicor paragraph.
Now we need to ensure we don't include boilerplate like Equal Opportunities statement, Recruiter Mouy Bun, etc. Remove those.
Also remove "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." We'll keep the range and maybe a brief note that actual compensation varies? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the salary range and the note about it being national average and actual compensation varies. That's substantive. So include in Pay section.
Now we need to output only HTML fragment, no /, no markdown fences.
We'll produce something like:
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.
At Epicor, we’re truly a team. Join 5,000 talented professionals in creating a world of better business through data, AI, and cognitive ERP. We help businesses stay future-ready by connecting people, processes, and technology. From software engineers who command the latest AI technology to business development reps who help us seize new opportunities, the work we do matters. Together, Epicor employees are creating a more resilient global supply chain. We’re Proactive, Proud, Partners. Whatever your career journey, we’ll help you find the right path. Through our training courses, mentorship, and continuous support, you’ll get everything you need to thrive. At Epicor, your success is our success. And that success really matters, because we’re the essential partners for the world’s most essential businesses—the hardworking companies who make, move, and sell the things the world needs.
Responsibilities
- 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.
Requirements
- 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:
- 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
- for any list of duties/requirements/benefits. It doesn't forbid nested lists. We'll do nested.
- "What Could Set You Apart": list of desirable extras.
List items:
- 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.
- "About Epicor": prose about company.
- "Competitive Pay & Benefits": then bullet list of benefits.
List items:
- 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.
Also there is a salary range: "Range Minimum: $105,000 USD Maximum: $178,000 USD". That's Pay info. Also note: "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." We should include Pay section with that info. Since they said include Pay section only if posting actually states them. Yes they state range. So we include Pay.
Schedule: Not mentioned besides "Participate in a 24x7 on-call rotation". That's schedule info? Could be considered schedule. But they didn't give explicit schedule like "Full-time". Might not create Schedule section unless explicit. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. They gave schedule info (24x7 on-call rotation) but not a schedule like "Full-time". Might still be considered schedule? Safer to not create Schedule section unless explicit schedule like "Full-time", "Part-time", "Shift". We'll omit Schedule.
Benefits: we have list; include Benefits section.
Now we need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. However we need to avoid thin sections. We have multiple lists that could map to these headings.
We need to decide mapping:
- About the role: intro paragraph.
- Responsibilities: "What You Will Be Doing" list.
- Requirements: "What You Will Likely Bring" list (core qualifications).
- Qualifications: maybe "What Could Set You Apart" (preferred qualifications). Could also be Skills. But we have both Requirements and Qualifications; we could treat "What You Will Likely Bring" as Requirements, and "What Could Set You Apart" as Qualifications (or Skills). However we also have technical skills like PowerShell etc inside Requirements. Might be okay.
Alternatively we could combine Requirements and Qualifications into one section, but instruction: prefer a few substantive sections over many thin ones. We have many sections already; maybe we can combine some.
We have: About the role, Responsibilities, Requirements (core), Preferred Qualifications (What Could Set You Apart), Benefits, Pay. That's 6 sections. Could be okay.
We also have About Epicor company description; could be part of About the role or separate "About Epicor". But we already have About the role for role description; we could add a section "About Epicor" but that's not in the allowed headings list? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Not About Epicor. So we should incorporate About Epicor prose into About the role or maybe as a separate paragraph under About the role. Since we cannot create a heading not in list. So we will add About Epicor content to About the role section (maybe after intro). That's fine.
Thus About the role will contain intro paragraph + About Epicor paragraph.
Now we need to ensure we don't include boilerplate like Equal Opportunities statement, Recruiter Mouy Bun, etc. Remove those.
Also remove "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." We'll keep the range and maybe a brief note that actual compensation varies? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the salary range and the note about it being national average and actual compensation varies. That's substantive. So include in Pay section.
Now we need to output only HTML fragment, no /, no markdown fences.
We'll produce something like: