Senior Windows Server Engineer

We need to produce HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate like EEO, legal, etc. Also remove duplicated lines, navigation, cookie, etc. Must not repeat job title as heading. Must not put Job ID/requisition numbers as headings. We need to parse the posting. Let's extract content: Paragraphs: - "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." - "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." - "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)." - "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 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." - "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." (Remove EEO boilerplate.) - "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) and remote application platforms (Citrix)" Actually text: "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 sections. About the role: Could be description of role: design, deploy, operate application delivery platforms, part of Application Delivery workgroup, building/maintaining secure scalable Windows-based infrastructure, blending hands-on infrastructure engineering with automation, security hardening, cross-team collaboration. Responsibilities: Might be tasks: design, deploy, operate application delivery platforms; build/maintain secure scalable Windows-based infrastructure; automation; security hardening; cross-team collaboration; support growing complex services. Requirements: Might be eligibility: relocation reimbursed? Actually relocation is a benefit. Requirements: Experience deploying/supporting Windows Server-based application infrastructure; Experience with web application hosting (IIS) and remote application platforms (Citrix); Proficiency with scripting or 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. Qualifications: Might be similar to requirements; but we can combine. However we need to avoid thin sections. Perhaps we have Requirements and Qualifications combined? But we need to follow instruction: Use headings only when posting has real specific content. We can have sections: About the role, Responsibilities, Requirements, Benefits. Possibly Skills (maybe separate). Pay and Schedule only if stated. Pay: mention merit-based compensation, annual raises, bonuses, stock grants. That's compensation details. So we can include Pay section with that info. Schedule: not mentioned (no schedule like full-time/part-time). So omit Schedule. Benefits: mention financial relocation assistance, comprehensive benefits, meals, sabbatical after five years, healthcare global, etc. Also mention living affordably, city accolades, campus themed, meals, sabbatical. So Benefits section. Skills: maybe list technical skills: Windows Server, IIS, Citrix, PowerShell, scripting/programming, CI/CD, troubleshooting, customer service. Could be under Skills. We need to preserve all substantive info; not invent or summarize away detail. So we need to include each piece exactly as given, but we can format as list items. We must not include boilerplate like EEO, navigation, etc. Also remove duplicated lines. Let's gather each piece and assign. About the role: Could be first paragraph(s) describing 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." That seems good. Responsibilities: Could be bullet list of duties: design, deploy, operate application delivery platforms; build/maintain secure scalable Windows-based infrastructure; automation; security hardening; cross-team collaboration; support growing complex set of services. But that overlaps with About the role. Might be redundant. Perhaps we treat About the role as overview, Responsibilities as specific duties. We can extract from text: "help design, deploy, and operate application delivery platforms", "building and maintaining secure, scalable Windows-based infrastructure", "hands-on infrastructure engineering with automation, security hardening, and cross-team collaboration". Also maybe "support Epic training environments, hosted client systems, and critical testing platforms used worldwide". That's part of responsibility. We'll produce a

with those. Requirements: 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". Also maybe "Relocation to the Madison, WI area (reimbursed)" is a benefit not requirement. Qualifications: Might be similar; but we could skip Qualifications if it duplicates Requirements. However we need to decide if we have separate sections for Requirements and Qualifications. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but we can choose which to include. We should include sections only when posting has real specific content. If we think Requirements and Qualifications overlap, we could combine them into one section called Requirements (or Qualifications). But we need to decide which heading to use. The posting includes both "Experience..." etc which could be considered requirements. There's no separate "Qualifications" distinct list. So we can have Requirements section and maybe skip Qualifications. Skills: Could list technical skills: Windows Server, IIS, Citrix, PowerShell/scripting, CI/CD, troubleshooting, customer service. But those are already in Requirements. Might be redundant. However we could still have Skills section summarizing those. But we need to avoid thin sections; maybe we combine Requirements and Skills into one? But the instruction says prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements, Benefits, Pay. That's five sections. That seems good. Pay: mention merit-based compensation, annual raises, bonuses, stock grants. Also maybe "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". That's compensation. Benefits: include relocation assistance, comprehensive benefits, meals, sabbatical, city accolades, campus themed, etc. Also mention healthcare global? Actually healthcare is global mentioned under "Healthcare is global, and building the best ideas from around the world into Epic software is a point of pride." That's more about work, not benefit. But we can include as benefit? It's not exactly a benefit but could be part of work. Might be better to include under About the role? Not sure. We'll keep it as part of Benefits? It says "Healthcare is global, and building the best ideas from around the world into Epic software is a point of pride." That's more about the company's value, not a direct employee benefit. Could be omitted as not a benefit. But we can include under Benefits as "global healthcare perspective"? Might be stretching. Safer to omit if not clearly a benefit. However the instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we must include that statement somewhere. Where does it fit? It's a statement about healthcare being global and building best ideas into Epic software is a point of pride. That's more about the work/mission. Could go under About the role or Responsibilities? It's not a duty. Could be under About the role as part of company culture. We'll include it in About the role maybe as a sentence. But we need to preserve all substantive info: we must not drop any piece. So we need to ensure each piece appears in output. Let's list all substantive sentences/phrases: 1. "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." 2. "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." 3. "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." 4. "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." 5. "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)." 6. "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