Windows Server Engineer

We need to produce HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate like EEO, legal, etc. Must preserve all substantive info. Let's parse the posting: - "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." => This is about location and relocation assistance. Could go under "About the role" or maybe "Benefits"? It's about relocation assistance, which is a benefit. Could be under Benefits. - "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." => About the role. - "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." => Responsibilities. - "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." => Responsibilities. - "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)." => Could be under About the role (location description) or maybe a separate section? Not a standard heading; we can include in About the role. - "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 (campus amenities, sabbatical, etc.) - "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." => Benefits and Pay. - "Healthcare is global, and building the best ideas from around the world into Epic software is a point of pride." => Could be Benefits (healthcare global) but it's vague. - "As an Equal Opportunity Employer, we know that inclusive teams design software that supports the delivery of quality care for all patients, so diversity, equity, and inclusion are written into our principles. Please see our full non-discrimination statement at https://careers.epic.com/EEO." => This is boilerplate EEO, should be removed. - "Relocation to the Madison, WI area (reimbursed)" => Benefit. - "Experience deploying and supporting Windows Server-based application infrastructure" => Requirement/Qualification. - "Experience with web application hosting (IIS) and remote application platforms (Citrix)" => Requirement. - "Proficiency with scripting or programming. PowerShell experience is a plus" => Skill/Requirement. - "Exposure to CI/CD deployment processes" => Requirement. - "Strong troubleshooting skills and excellent customer service" => Skill. - "Eligibility to work in the U.S. without visa sponsorship" => Requirement. - "COVID-19 vaccination" => Requirement (maybe). We need to decide sections. Potential sections: - About the role: description of team, purpose, location, campus, etc. - Responsibilities: design, deploy, operate application delivery platforms; building/maintaining secure scalable Windows-based infrastructure; automation, security hardening, cross-team collaboration. - Requirements/Qualifications: Experience deploying/supporting Windows Server-based application infrastructure; Experience with IIS and Citrix; Proficiency with scripting/programming (PowerShell plus); Exposure to CI/CD deployment processes; Strong troubleshooting skills and excellent customer service; Eligibility to work in US without visa sponsorship; COVID-19 vaccination. - Skills: maybe separate but we can combine with Requirements. The instruction says use headings for sections like Requirements, Qualifications, Skills. We could have Requirements and Skills separate, but we need to avoid thin sections. Could combine Requirements and Qualifications into one section (maybe "Requirements") and Skills as another if we have distinct skill list. But we have skills like troubleshooting, customer service, PowerShell, scripting, CI/CD. Could put under Skills. - Benefits: financial relocation assistance; comprehensive benefits; merit-based compensation; annual raises and bonuses; stock grants; healthcare global; campus amenities (unique themed campus, meals, sabbatical, etc.) - Pay: merit-based compensation, annual raises and bonuses, stock grants. Could be under Benefits or Pay. Since we have both Benefits and Pay headings possible, we should include Pay if there is specific content: merit-based compensation, annual raises and bonuses, stock grants. That's specific enough. - Schedule: not mentioned; do not include. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay. We must not include empty sections. Now craft HTML. We need

for each section heading. Inside each section, use

for prose,

• for lists. We need to preserve all substantive information; do not invent or summarize away detail. We must not repeat job title. We must not include boilerplate like EEO, legal, etc. We must not include duplicated lines. Let's extract each piece. About the role: - "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 description: "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 description: "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." We could combine location and campus description under About the role. Responsibilities: - "help design, deploy, and operate application delivery platforms that support Epic's internal staff, customers, and global training programs." (maybe already in About) - "building and maintaining secure, scalable Windows-based infrastructure that powers Epic training environments, hosted client systems, and critical testing platforms used worldwide." - "hands-on infrastructure engineering with automation, security hardening, and cross-team collaboration" We could list responsibilities as bullet points. Requirements: - "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: Maybe separate: "Proficiency with scripting or programming. PowerShell experience is a plus" could be skill; "Strong troubleshooting skills and excellent customer service" also skill; "Exposure to CI/CD deployment processes" maybe skill. But we already have those in Requirements. To avoid duplication, we could put all under Requirements and not have Skills. But the instruction says prefer a few substantive sections over many thin ones. So we could combine Requirements and Skills into one section called "Requirements". However they ask to use headings for sections like Requirements, Qualifications, Skills. It's not mandatory to use all; we just must not create a heading without real content. So we can have only Requirements (which includes both requirements and skills). That's fine. Benefits: - "We recruit nationally and provide financial relocation assistance." (relocation reimbursed) - "We offer comprehensive benefits to keep you healthy and happy as you grow in your life and career," - "Your merit-based compensation will reflect the impact your work has on the company and our customers." (maybe Pay) - "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." (Pay) - "Healthcare is global, and building the best ideas from around the world into Epic software is a point of pride." (Benefit) - Campus amenities: "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." - Relocation to Madison, WI area (reimbursed) (already mentioned) We need to avoid duplication: relocation assistance appears twice; we can mention once. Pay: - "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." We could put these under Pay. Now we must ensure we don't include boilerplate like EEO, etc. Now produce HTML. Structure:

  About the role

  ... paragraphs ...

  Maybe we need to split into multiple

  for readability. We'll include bullet lists where appropriate. Let's craft. About the role: combine team purpose, responsibilities? Actually responsibilities separate. About the role paragraph: "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." Then location/campus: maybe another paragraph. We'll do:

  Live affordably in a city known for its rising tech talent. Epic is located just outside Madison,