Senior Windows Server Engineer
for headings. Use - for lists. Use
for prose.
We need to decide which sections to include.
Potential sections:
- About the role (paragraph summarizing role, location, relocation assistance)
- Responsibilities (list)
- Requirements (list)
- Skills (list) (maybe combine with Requirements? But we can separate.)
- Benefits (list)
- Pay (paragraph)
We should avoid duplication.
Let's craft:
About the role:
This position is based on Epic's campus in Madison, WI and requires relocation to the area; financial relocation assistance is provided. You will join the Windows Server Engineering team within the Application Delivery workgroup, designing, deploying, and operating application delivery platforms that support Epic's internal staff, customers, and global training programs. You will build and maintain secure, scalable Windows‑based infrastructure for Epic training environments, hosted client systems, and critical testing platforms worldwide, blending hands‑on infrastructure engineering with automation, security hardening, and cross‑team collaboration.
Responsibilities: - Design, deploy, and operate application delivery platforms supporting internal staff, customers, and global training programs.
- Build and maintain secure, scalable Windows‑based infrastructure for Epic training environments, hosted client systems, and critical testing platforms.
- Implement automation and security hardening measures.
- Collaborate across teams to support a growing and increasingly complex set of services.
Requirements: Could be list of experience/qualifications: - Experience deploying and supporting Windows Server‑based application infrastructure.
- Experience with web application hosting (IIS) and remote application platforms (Citrix).
- Proficiency with scripting or programming; PowerShell experience is a plus.
- Exposure to CI/CD deployment processes.
- Strong troubleshooting skills and excellent customer service.
- Eligibility to work in the U.S. without visa sponsorship.
- COVID‑19 vaccination.
Skills: Could be similar but maybe we can combine; but we need to avoid duplication. Perhaps we can treat Requirements as the list of required experience, and Skills as technical competencies: Windows Server, IIS, Citrix, PowerShell, scripting, CI/CD, troubleshooting, customer service. However that duplicates. Better to have only one list for qualifications/requirements and maybe not have Skills separate. But the instruction says we can include sections only when posting has real specific content. We have content for skills (technical skills). We could list them.
But we must avoid repeating same info. Could separate: Requirements list includes experience and eligibility; Skills list includes technical proficiencies.
Let's define:
Requirements (experience/eligibility): as above.
Skills (technical): - Windows Server administration
- IIS web application hosting
- Citrix remote application platforms
- Scripting/programming (PowerShell preferred)
- CI/CD deployment processes
- Troubleshooting and customer service
Benefits: list: - Financial relocation assistance to Madison, WI
- Comprehensive benefits package
- Merit‑based compensation reflecting impact
- Annual raises and bonuses
- Stock grants
- Four‑week sabbatical after five years of service
- Restaurant‑quality meals at low cost
- Uniquely themed campus with varied workspaces
- Global healthcare coverage
Pay: maybe a paragraph: Compensation is merit‑based, with eligibility for annual raises, bonuses, and stock grants that increase your stake in Epic’s success.
Schedule: none.
We must not include headings for sections without content.
Now ensure we removed boilerplate: EEO, etc.
Now produce HTML fragment:
About the role
...
Responsibilities
...
Requirements
...
Skills
...
Benefits
...
Pay
...
Make sure no extra whitespace? It's fine.
Let's craft the exact text.
About the role paragraph: "This position is based on Epic's campus in Madison, WI and requires relocation to the area; financial relocation assistance is provided. You will join the Windows Server Engineering team within the Application Delivery workgroup, designing, deploying, and operating application delivery platforms that support Epic's internal staff, customers, and global training programs. You will build and maintain secure, scalable Windows‑based infrastructure for Epic training environments, hosted client systems, and critical testing platforms worldwide, blending hands‑on infrastructure engineering with automation, security hardening, and cross‑team collaboration."
Responsibilities list items as above.
Requirements list: include each bullet.
Skills list: as above.
Benefits list: as above.
Pay paragraph: "Compensation is merit‑based, with eligibility for annual raises, bonuses, and stock grants that increase your stake in Epic’s success."
Check for any duplicated content: Benefits includes "Merit‑based compensation reflecting impact" which is similar to Pay paragraph; but we can keep both as they are slightly different framing. Might be okay but could be considered duplication. However the instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep both merit-based compensation mention and annual raises etc. If we put merit-based compensation in Benefits and also in Pay, that's duplication but both are present in original. Could we avoid duplication by moving merit-based compensation to Pay only and not list it in Benefits? Benefits list includes "Comprehensive benefits package", "Financial relocation assistance", "Four‑week sabbatical", "Restaurant‑quality meals", "Uniquely themed campus", "Global healthcare". Merit-based compensation is more about pay, not a benefit. So better to move merit-based compensation to Pay section and not duplicate in Benefits. Let's adjust Benefits list accordingly.
Thus Benefits list:
- Financial relocation assistance to Madison, WI
- Comprehensive benefits package
- Four‑week sabbatical after five years of service
- Restaurant‑quality meals at low cost
- Uniquely themed campus with varied workspaces
- Global healthcare coverage
Pay paragraph: "Compensation is merit‑based, reflecting the impact of your work, with eligibility for annual raises, bonuses, and stock grants that increase your stake in Epic’s success."
Now ensure we haven't missed any substantive info: The posting also mentions "Live affordably in a city known for its rising tech talent." That's location benefit; maybe we can add to Benefits: "Affordable living in
for prose. We need to decide which sections to include. Potential sections: - About the role (paragraph summarizing role, location, relocation assistance) - Responsibilities (list) - Requirements (list) - Skills (list) (maybe combine with Requirements? But we can separate.) - Benefits (list) - Pay (paragraph) We should avoid duplication. Let's craft: About the role:
This position is based on Epic's campus in Madison, WI and requires relocation to the area; financial relocation assistance is provided. You will join the Windows Server Engineering team within the Application Delivery workgroup, designing, deploying, and operating application delivery platforms that support Epic's internal staff, customers, and global training programs. You will build and maintain secure, scalable Windows‑based infrastructure for Epic training environments, hosted client systems, and critical testing platforms worldwide, blending hands‑on infrastructure engineering with automation, security hardening, and cross‑team collaboration.
Responsibilities:- Design, deploy, and operate application delivery platforms supporting internal staff, customers, and global training programs.
- Build and maintain secure, scalable Windows‑based infrastructure for Epic training environments, hosted client systems, and critical testing platforms.
- Implement automation and security hardening measures.
- Collaborate across teams to support a growing and increasingly complex set of services.
- Experience deploying and supporting Windows Server‑based application infrastructure.
- Experience with web application hosting (IIS) and remote application platforms (Citrix).
- Proficiency with scripting or programming; PowerShell experience is a plus.
- Exposure to CI/CD deployment processes.
- Strong troubleshooting skills and excellent customer service.
- Eligibility to work in the U.S. without visa sponsorship.
- COVID‑19 vaccination.
- Windows Server administration
- IIS web application hosting
- Citrix remote application platforms
- Scripting/programming (PowerShell preferred)
- CI/CD deployment processes
- Troubleshooting and customer service
- Financial relocation assistance to Madison, WI
- Comprehensive benefits package
- Merit‑based compensation reflecting impact
- Annual raises and bonuses
- Stock grants
- Four‑week sabbatical after five years of service
- Restaurant‑quality meals at low cost
- Uniquely themed campus with varied workspaces
- Global healthcare coverage
Compensation is merit‑based, with eligibility for annual raises, bonuses, and stock grants that increase your stake in Epic’s success.
Schedule: none. We must not include headings for sections without content. Now ensure we removed boilerplate: EEO, etc. Now produce HTML fragment:About the role
...
Responsibilities
- ...
Requirements
- ...
Skills
- ...
Benefits
- ...
Pay
...
Make sure no extra whitespace? It's fine. Let's craft the exact text. About the role paragraph: "This position is based on Epic's campus in Madison, WI and requires relocation to the area; financial relocation assistance is provided. You will join the Windows Server Engineering team within the Application Delivery workgroup, designing, deploying, and operating application delivery platforms that support Epic's internal staff, customers, and global training programs. You will build and maintain secure, scalable Windows‑based infrastructure for Epic training environments, hosted client systems, and critical testing platforms worldwide, blending hands‑on infrastructure engineering with automation, security hardening, and cross‑team collaboration." Responsibilities list items as above. Requirements list: include each bullet. Skills list: as above. Benefits list: as above. Pay paragraph: "Compensation is merit‑based, with eligibility for annual raises, bonuses, and stock grants that increase your stake in Epic’s success." Check for any duplicated content: Benefits includes "Merit‑based compensation reflecting impact" which is similar to Pay paragraph; but we can keep both as they are slightly different framing. Might be okay but could be considered duplication. However the instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep both merit-based compensation mention and annual raises etc. If we put merit-based compensation in Benefits and also in Pay, that's duplication but both are present in original. Could we avoid duplication by moving merit-based compensation to Pay only and not list it in Benefits? Benefits list includes "Comprehensive benefits package", "Financial relocation assistance", "Four‑week sabbatical", "Restaurant‑quality meals", "Uniquely themed campus", "Global healthcare". Merit-based compensation is more about pay, not a benefit. So better to move merit-based compensation to Pay section and not duplicate in Benefits. Let's adjust Benefits list accordingly. Thus Benefits list: - Financial relocation assistance to Madison, WI - Comprehensive benefits package - Four‑week sabbatical after five years of service - Restaurant‑quality meals at low cost - Uniquely themed campus with varied workspaces - Global healthcare coverage Pay paragraph: "Compensation is merit‑based, reflecting the impact of your work, with eligibility for annual raises, bonuses, and stock grants that increase your stake in Epic’s success." Now ensure we haven't missed any substantive info: The posting also mentions "Live affordably in a city known for its rising tech talent." That's location benefit; maybe we can add to Benefits: "Affordable living in