Windows Server Engineer
Epic · Winston-Salem, NC · 1 mo ago
On-siteInformation TechnologyFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include boilerplate like EEO, etc. Must preserve all substantive info.
Let's parse the posting.
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." => location, 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." => role description.
- "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)." => location benefits.
- "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, meals, sabbatical, perks).
- "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/compensation.
- "Healthcare is global, and building the best ideas from around the world into Epic software is a point of pride." => maybe not needed.
- Then bullet list (actually lines) after that: "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"
These are requirements/qualifications.
We need to decide sections.
Potential sections:
- About the role: description of team, purpose.
- 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; excellent customer service; eligibility to work in US without visa sponsorship; COVID-19 vaccination; relocation reimbursed (maybe as benefit). Also mention relocation assistance.
- Benefits: comprehensive benefits; merit-based compensation; annual raises and bonuses; stock grants; campus amenities (themed campus, meals, sabbatical, perks); location benefits (Madison accolades, affordable living, rising tech talent). Also relocation financial assistance.
- Pay: not explicitly given; only merit-based compensation, annual raises, bonuses, stock grants. No specific numbers. Should we include Pay section? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does mention merit-based compensation, annual raises, bonuses, stock grants. That is compensation info but not specific pay. It's still compensation info. The rule says: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state compensation aspects (merit-based compensation, annual raises, bonuses, stock grants). So we could include a Pay section with that info. However we also have Benefits section for other benefits. Could combine compensation into Benefits? But they said prefer few substantive sections over many thin ones. We could have Benefits covering compensation and other perks. But they also said include a section ONLY when posting has real, specific content for it. The posting does have content about compensation (merit-based, raises, bonuses, stock grants). So we could have a Pay section with that. But we also have Benefits section for other benefits (campus, meals, sabbatical, location accolades, relocation assistance, comprehensive benefits). Might be okay to have both Pay and Benefits.
Schedule: no mention of schedule (full-time, hours). Not present, so omit Schedule.
Now we need to output HTML fragment with headings for each section we include, and
headings for each section we include, and - for any list of duties/requirements/benefits, and
for prose.
We must not repeat job title. No markdown.
We need to preserve all substantive information; do not invent or summarize away detail.
Let's extract details precisely.
About the role: Could be a paragraph summarizing 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 increasingly complex set of services."
That seems fine.
Responsibilities: Could be list: design, deploy, operate application delivery platforms; build and maintain secure, scalable Windows-based infrastructure; automation; security hardening; cross-team collaboration. But we already covered some in About. Might be redundant. Perhaps better to have Responsibilities as list of duties: design, deploy, operate application delivery platforms; build and maintain secure, scalable Windows-based infrastructure; implement automation; perform security hardening; collaborate across teams. However we need to avoid duplication. The instructions: preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details, but we can organize them.
Let's list responsibilities from text:
- help design, deploy, and operate application delivery platforms that support Epic's internal staff, customers, and global training programs.
- 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.
- automation.
- security hardening.
- cross-team collaboration.
- support a growing and increasingly complex set of services.
We can put these as
- .
Requirements/Qualifications: 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.
- Excellent customer service.
- Eligibility to work in the U.S. without visa sponsorship.
- COVID-19 vaccination.
- Relocation to the Madison, WI area (reimbursed) (maybe as benefit but it's a requirement? It's stated as "Relocation to the Madison, WI area (reimbursed)" under the list; it's a requirement that you must be willing to relocate and they provide reimbursement.)
We'll include that as a requirement: willingness to relocate to Madison, WI area (reimbursed).
Benefits: list:
- Comprehensive benefits to keep you healthy and happy.
- Merit-based compensation reflecting impact.
- Annual raises and bonuses.
- Stock grants.
- Uniquely themed campus designed to heighten ability to get stuff done (office, conference room, fireplace).
- All meals restaurant-quality but cost only a few dollars, prepared by kitchen talent from restaurants around the country.
- After five years, four-week sabbatical anywhere in the world.
- Staff have kayaked in Patagonia, attended a Beyoncé concert in Ireland, built a library in Tanzania, run a marathon in Antarctica (these are examples of sabbatical usage; maybe keep as part of sabbatical benefit).
- Live affordably in a city known for its rising tech talent.
- Epic located just outside Madison, Wisconsin, second fastest growing market for tech talent in US, home to state capital and University of Wisconsin.
- Madison accolades: greenest city in America (NerdWallet), best city for renters (SmartAsset), fittest city in America (Fitbit), third best metro in US for young professionals (Forbes Advisor).
- Financial relocation assistance (reimbursed).
- Healthcare is global (maybe benefit).
- Building best ideas from around the world into Epic software is a point of pride (maybe not a benefit but could be included under "About the company").
We need to decide what to include as Benefits. The instruction: include a section ONLY when posting has real, specific content for it. So we can include Benefits with the above.
Pay: we could include merit-based compensation, annual raises, bonuses, stock grants. But those are already in Benefits. Might be redundant to have both Pay and Benefits. Since they said prefer few substantive sections over many thin ones, we could combine compensation into Benefits and omit Pay. However they said never create Pay/Schedule/Benefits sections unless posting actually states them. It does state compensation details, but we could still put them under Benefits. The rule: "Prefer a few substantive sections over many thin ones." So better to have one Benefits section that includes compensation and other perks. Then we don't need a separate Pay section. That seems good.
Thus sections: About the role, Responsibilities, Requirements (or Qualifications), Benefits.
We need to decide heading names: They gave examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use Requirements (or Qualifications). Since we have both experience and skills, maybe "Requirements" is fine. Or "Qualifications". We'll use "Requirements". Could also add "Skills" but we have skills listed; but we can put them under Requirements.
We'll output:
About the role
... paragraph ...
Responsibilities
- ...
...
Requirements
- ...
...
Benefits
- ...
...
We must not include any extra text outside HTML fragment.
Now craft the content precisely, preserving details.
About the role paragraph: combine sentences.
"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."
That's all.
Responsibilities list: each bullet as a distinct responsibility.
From text:
- help design, deploy, and operate application delivery platforms that support Epic's internal staff, customers, and global training programs.
- building and maintaining secure, scalable Windows-based infrastructure that powers Epic training environments, hosted client systems, and critical testing platforms used worldwide
for prose. We must not repeat job title. No markdown. We need to preserve all substantive information; do not invent or summarize away detail. Let's extract details precisely. About the role: Could be a paragraph summarizing 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 increasingly complex set of services." That seems fine. Responsibilities: Could be list: design, deploy, operate application delivery platforms; build and maintain secure, scalable Windows-based infrastructure; automation; security hardening; cross-team collaboration. But we already covered some in About. Might be redundant. Perhaps better to have Responsibilities as list of duties: design, deploy, operate application delivery platforms; build and maintain secure, scalable Windows-based infrastructure; implement automation; perform security hardening; collaborate across teams. However we need to avoid duplication. The instructions: preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details, but we can organize them. Let's list responsibilities from text: - help design, deploy, and operate application delivery platforms that support Epic's internal staff, customers, and global training programs. - 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. - automation. - security hardening. - cross-team collaboration. - support a growing and increasingly complex set of services. We can put these as
- .
Requirements/Qualifications: 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.
- Excellent customer service.
- Eligibility to work in the U.S. without visa sponsorship.
- COVID-19 vaccination.
- Relocation to the Madison, WI area (reimbursed) (maybe as benefit but it's a requirement? It's stated as "Relocation to the Madison, WI area (reimbursed)" under the list; it's a requirement that you must be willing to relocate and they provide reimbursement.)
We'll include that as a requirement: willingness to relocate to Madison, WI area (reimbursed).
Benefits: list:
- Comprehensive benefits to keep you healthy and happy.
- Merit-based compensation reflecting impact.
- Annual raises and bonuses.
- Stock grants.
- Uniquely themed campus designed to heighten ability to get stuff done (office, conference room, fireplace).
- All meals restaurant-quality but cost only a few dollars, prepared by kitchen talent from restaurants around the country.
- After five years, four-week sabbatical anywhere in the world.
- Staff have kayaked in Patagonia, attended a Beyoncé concert in Ireland, built a library in Tanzania, run a marathon in Antarctica (these are examples of sabbatical usage; maybe keep as part of sabbatical benefit).
- Live affordably in a city known for its rising tech talent.
- Epic located just outside Madison, Wisconsin, second fastest growing market for tech talent in US, home to state capital and University of Wisconsin.
- Madison accolades: greenest city in America (NerdWallet), best city for renters (SmartAsset), fittest city in America (Fitbit), third best metro in US for young professionals (Forbes Advisor).
- Financial relocation assistance (reimbursed).
- Healthcare is global (maybe benefit).
- Building best ideas from around the world into Epic software is a point of pride (maybe not a benefit but could be included under "About the company").
We need to decide what to include as Benefits. The instruction: include a section ONLY when posting has real, specific content for it. So we can include Benefits with the above.
Pay: we could include merit-based compensation, annual raises, bonuses, stock grants. But those are already in Benefits. Might be redundant to have both Pay and Benefits. Since they said prefer few substantive sections over many thin ones, we could combine compensation into Benefits and omit Pay. However they said never create Pay/Schedule/Benefits sections unless posting actually states them. It does state compensation details, but we could still put them under Benefits. The rule: "Prefer a few substantive sections over many thin ones." So better to have one Benefits section that includes compensation and other perks. Then we don't need a separate Pay section. That seems good.
Thus sections: About the role, Responsibilities, Requirements (or Qualifications), Benefits.
We need to decide heading names: They gave examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use Requirements (or Qualifications). Since we have both experience and skills, maybe "Requirements" is fine. Or "Qualifications". We'll use "Requirements". Could also add "Skills" but we have skills listed; but we can put them under Requirements.
We'll output:
About the role
... paragraph ...
Responsibilities
- ... ...
Requirements
- ... ...
Benefits
- ... ...