Windows Server Engineer
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include each piece.
Let's extract each piece:
Location and relocation: "Please note that this position is based on our campus in Madison, WI, and requires relocation to the area. We recruit nationally and provide financial relocation assistance."
We could put that in About the role or Benefits? Probably About the role includes location.
Description: "Our Windows Server Engineering team is seeking a talented engineer to help design, deploy, and operate application delivery platforms that support Epic's internal staff, customers, and global training programs. You will be part of the Application Delivery workgroup, responsible for building and maintaining secure, scalable Windows-based infrastructure that powers Epic training environments, hosted client systems, and critical testing platforms used worldwide. This role blends hands-on infrastructure engineering with automation, security hardening, and cross-team collaboration to support a growing and increasing complex set of services."
Location benefits: "Live affordably in a city known for its rising tech talent. Epic is located just outside Madison, Wisconsin, the second fastest growing market for tech talent in the United States and home to the state capital and the University of Wisconsin. Madison, a city surrounded by water, has received accolades for being the greenest city in America (NerdWallet), the best city for renters (SmartAsset), the fittest city in America (Fitbit), and the third best metro in the US for young professionals (Forbes Advisor)."
Campus/perks: "More than just important work. Our uniquely themed campus was designed to heighten your ability to get stuff done in your office, a conference room, or by the fireplace in a comfy chair. All meals are restaurant-quality but cost only a few dollars, and they’re prepared by a team comprised of kitchen talent from restaurants around the country. And, after five years here, you’ll earn a four-week sabbatical anywhere in the world. Staff have kayaked in Patagonia, attended a Beyoncé concert in Ireland, built a library in Tanzania, and run a marathon in Antarctica."
Benefits: "We offer comprehensive benefits to keep you healthy and happy as you grow in your life and career, and your merit-based compensation will reflect the impact your work has on the company and our customers. You'll also be eligible for annual raises and bonuses, as well as stock grants, which give you an even greater stake in the success of Epic and our customers. Healthcare is global, and building the best ideas from around the world into Epic software is a point of pride."
Now requirements list:
- Relocation to the Madison, WI area (reimbursed)
- 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
We need to decide which go to Requirements, Qualifications, Skills. Typically Requirements: experience, eligibility, vaccination. Qualifications: maybe education? Not present. Skills: scripting, PowerShell, CI/CD, troubleshooting, customer service.
But we must not invent sections; we can include any of the three if we have content. Let's allocate:
- Requirements: Experience deploying/supporting Windows Server, Experience with IIS/Citrix, Proficiency with scripting or programming (PowerShell plus), Exposure to CI/CD, Strong troubleshooting skills and excellent customer service, Eligibility to work in US without visa sponsorship, COVID-19 vaccination, Relocation reimbursement? Actually relocation assistance is a benefit, not a requirement. But the line "Relocation to the Madison, WI area (reimbursed)" is more like a requirement (must relocate) with reimbursement as benefit. Could be in Requirements or Benefits. I'd put in Requirements as "Must be willing to relocate to Madison, WI area (reimbursement provided)". Keep as requirement.
- Qualifications: maybe none specific besides eligibility? But eligibility is more a requirement. Could put eligibility and vaccination under Qualifications. But we need to avoid thin sections. Perhaps combine Requirements and Qualifications into one? But we need to follow instruction: include a section ONLY when posting has real specific content for it. We can have multiple sections if content exists.
We could have:
About the role (description + location + location benefits + campus perks?) Might be too much. Better to split: About the role (role description), Responsibilities (maybe from description: design, deploy, operate application delivery platforms, building/maintaining infrastructure, automation, security hardening, cross-team collaboration). Requirements (experience, relocation, eligibility, vaccination). Skills (scripting, PowerShell, CI/CD, troubleshooting, customer service). Benefits (relocation assistance, campus, meals, sabbatical, comprehensive benefits, merit-based compensation, raises, bonuses, stock grants, healthcare global). Pay (maybe merit-based compensation, annual raises, bonuses, stock grants). But Pay overlaps with Benefits; we could combine compensation into Benefits and omit Pay if not distinct. However instruction: Prefer a few substantive sections over many thin ones. So maybe we combine compensation into Benefits and not have separate Pay. Since Pay section would be thin if we only list merit-based compensation, raises, bonuses, stock grants. But we could still include Pay if we have those details. However we already have those details in Benefits; we could keep Benefits and not Pay. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits and compensation, so we can have Benefits section. Pay is also stated (merit-based compensation, annual raises, bonuses, stock grants). So we could have both Benefits and Pay, but that may be thin. Better to have Benefits include compensation details, and not have separate Pay. Since they said "Prefer a few substantive sections over many thin ones." So we will have Benefits covering compensation, relocation, campus, meals, sabbatical, healthcare global.
Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits.
Now we need to extract prose for About the role: maybe first paragraph about team and role. Also location info? Could be part of About the role. Let's craft About the role as:
Our Windows Server Engineering team is seeking a talented engineer to help design, deploy, and operate application delivery platforms that support Epic's internal staff, customers, and global training programs. You will be part of the Application Delivery workgroup, responsible for building and maintaining secure, scalable Windows-based infrastructure that powers Epic training environments, hosted client systems, and critical testing platforms used worldwide. This role blends hands-on infrastructure engineering with automation, security hardening, and cross-team collaboration to support a growing and increasingly complex set of services. The position is based on our campus in Madison, WI, and requires relocation to the area; we recruit nationally and provide financial relocation assistance.
That covers location and relocation.
Responsibilities: maybe we can pull from description: design, deploy, operate application delivery platforms; building/maintaining secure scalable Windows-based infrastructure; automation; security hardening; cross-team collaboration. Also supporting Epic training environments, hosted client systems, critical testing platforms. Let's list as - Design, deploy, and operate application delivery platforms for Epic internal staff, customers, and global training programs.
- Build and maintain secure, scalable Windows-based infrastructure powering Epic training environments, hosted client systems, and critical testing platforms worldwide.
- Apply hands‑on infrastructure engineering combined with automation and security hardening.
- Collaborate across teams to support a growing and increasingly complex set of services.
Requirements: list of experience, relocation, eligibility, vaccination. Let's list:
- 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
for prose. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include each piece. Let's extract each piece: Location and relocation: "Please note that this position is based on our campus in Madison, WI, and requires relocation to the area. We recruit nationally and provide financial relocation assistance." We could put that in About the role or Benefits? Probably About the role includes location. Description: "Our Windows Server Engineering team is seeking a talented engineer to help design, deploy, and operate application delivery platforms that support Epic's internal staff, customers, and global training programs. You will be part of the Application Delivery workgroup, responsible for building and maintaining secure, scalable Windows-based infrastructure that powers Epic training environments, hosted client systems, and critical testing platforms used worldwide. This role blends hands-on infrastructure engineering with automation, security hardening, and cross-team collaboration to support a growing and increasing complex set of services." Location benefits: "Live affordably in a city known for its rising tech talent. Epic is located just outside Madison, Wisconsin, the second fastest growing market for tech talent in the United States and home to the state capital and the University of Wisconsin. Madison, a city surrounded by water, has received accolades for being the greenest city in America (NerdWallet), the best city for renters (SmartAsset), the fittest city in America (Fitbit), and the third best metro in the US for young professionals (Forbes Advisor)." Campus/perks: "More than just important work. Our uniquely themed campus was designed to heighten your ability to get stuff done in your office, a conference room, or by the fireplace in a comfy chair. All meals are restaurant-quality but cost only a few dollars, and they’re prepared by a team comprised of kitchen talent from restaurants around the country. And, after five years here, you’ll earn a four-week sabbatical anywhere in the world. Staff have kayaked in Patagonia, attended a Beyoncé concert in Ireland, built a library in Tanzania, and run a marathon in Antarctica." Benefits: "We offer comprehensive benefits to keep you healthy and happy as you grow in your life and career, and your merit-based compensation will reflect the impact your work has on the company and our customers. You'll also be eligible for annual raises and bonuses, as well as stock grants, which give you an even greater stake in the success of Epic and our customers. Healthcare is global, and building the best ideas from around the world into Epic software is a point of pride." Now requirements list: - Relocation to the Madison, WI area (reimbursed) - 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 We need to decide which go to Requirements, Qualifications, Skills. Typically Requirements: experience, eligibility, vaccination. Qualifications: maybe education? Not present. Skills: scripting, PowerShell, CI/CD, troubleshooting, customer service. But we must not invent sections; we can include any of the three if we have content. Let's allocate: - Requirements: Experience deploying/supporting Windows Server, Experience with IIS/Citrix, Proficiency with scripting or programming (PowerShell plus), Exposure to CI/CD, Strong troubleshooting skills and excellent customer service, Eligibility to work in US without visa sponsorship, COVID-19 vaccination, Relocation reimbursement? Actually relocation assistance is a benefit, not a requirement. But the line "Relocation to the Madison, WI area (reimbursed)" is more like a requirement (must relocate) with reimbursement as benefit. Could be in Requirements or Benefits. I'd put in Requirements as "Must be willing to relocate to Madison, WI area (reimbursement provided)". Keep as requirement. - Qualifications: maybe none specific besides eligibility? But eligibility is more a requirement. Could put eligibility and vaccination under Qualifications. But we need to avoid thin sections. Perhaps combine Requirements and Qualifications into one? But we need to follow instruction: include a section ONLY when posting has real specific content for it. We can have multiple sections if content exists. We could have: About the role (description + location + location benefits + campus perks?) Might be too much. Better to split: About the role (role description), Responsibilities (maybe from description: design, deploy, operate application delivery platforms, building/maintaining infrastructure, automation, security hardening, cross-team collaboration). Requirements (experience, relocation, eligibility, vaccination). Skills (scripting, PowerShell, CI/CD, troubleshooting, customer service). Benefits (relocation assistance, campus, meals, sabbatical, comprehensive benefits, merit-based compensation, raises, bonuses, stock grants, healthcare global). Pay (maybe merit-based compensation, annual raises, bonuses, stock grants). But Pay overlaps with Benefits; we could combine compensation into Benefits and omit Pay if not distinct. However instruction: Prefer a few substantive sections over many thin ones. So maybe we combine compensation into Benefits and not have separate Pay. Since Pay section would be thin if we only list merit-based compensation, raises, bonuses, stock grants. But we could still include Pay if we have those details. However we already have those details in Benefits; we could keep Benefits and not Pay. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits and compensation, so we can have Benefits section. Pay is also stated (merit-based compensation, annual raises, bonuses, stock grants). So we could have both Benefits and Pay, but that may be thin. Better to have Benefits include compensation details, and not have separate Pay. Since they said "Prefer a few substantive sections over many thin ones." So we will have Benefits covering compensation, relocation, campus, meals, sabbatical, healthcare global. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits. Now we need to extract prose for About the role: maybe first paragraph about team and role. Also location info? Could be part of About the role. Let's craft About the role as:
Our Windows Server Engineering team is seeking a talented engineer to help design, deploy, and operate application delivery platforms that support Epic's internal staff, customers, and global training programs. You will be part of the Application Delivery workgroup, responsible for building and maintaining secure, scalable Windows-based infrastructure that powers Epic training environments, hosted client systems, and critical testing platforms used worldwide. This role blends hands-on infrastructure engineering with automation, security hardening, and cross-team collaboration to support a growing and increasingly complex set of services. The position is based on our campus in Madison, WI, and requires relocation to the area; we recruit nationally and provide financial relocation assistance.
That covers location and relocation. Responsibilities: maybe we can pull from description: design, deploy, operate application delivery platforms; building/maintaining secure scalable Windows-based infrastructure; automation; security hardening; cross-team collaboration. Also supporting Epic training environments, hosted client systems, critical testing platforms. Let's list as- Design, deploy, and operate application delivery platforms for Epic internal staff, customers, and global training programs.
- Build and maintain secure, scalable Windows-based infrastructure powering Epic training environments, hosted client systems, and critical testing platforms worldwide.
- Apply hands‑on infrastructure engineering combined with automation and security hardening.
- 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