Jobs · Wyoming

Windows Server Engineer

Epic · Gillette, WY · 1 mo ago
On-siteFull-time
We need to produce HTML fragment with sections only if content exists. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. No Job ID. Remove boilerplate like EEO, equal-opportunity, scam warning, application instructions, navigation, cookie, legal. Also remove duplicated lines. 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." - Then EEO statement etc (remove). - Then bullet list (maybe 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 likely requirements/qualifications. We need to decide sections: About the role (overview), Responsibilities, Requirements/Qualifications/Skills, Benefits, maybe Pay (mention merit-based compensation, annual raises, bonuses, stock grants). Schedule? Not mentioned. So we should not create Schedule section. We must not create sections with filler like "not specified". So only include sections with real content. We need to use

for each section heading. Use
  • for any list of duties/requirements/benefits. Use

    for prose. We need to preserve all substantive information; do not invent or summarize away detail. Let's craft sections: About the role: could include description of team, purpose, location, relocation assistance, etc. Responsibilities: design, deploy, operate application delivery platforms; building/maintaining secure scalable Windows-based infrastructure; automation, security hardening, cross-team collaboration. Requirements/Qualifications/Skills: list items: relocation to Madison WI area (reimbursed) (maybe as requirement?), 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 experience a 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. Benefits: comprehensive benefits, merit-based compensation, annual raises and bonuses, stock grants, healthcare global, sabbatical after five years (four-week), themed campus, meals restaurant-quality low cost, ability to get stuff done in office/conference room/fireplace, etc. Also mention living affordably, city accolades, etc. Those could be benefits or location description. Might fit under Benefits or About the role. But we need to avoid duplication. We could have sections: About the role (overview, location, relocation assistance, campus perks), Responsibilities, Requirements, Benefits (including compensation, sabbatical, meals, etc). Pay maybe part of Benefits; but we could have Pay section if we have specific compensation details: merit-based compensation, annual raises, bonuses, stock grants. That's pay-related. So we could have Pay section. Schedule: not present, so omit. Thus sections: About the role, Responsibilities, Requirements, Pay, Benefits. Check if any content duplicates across sections; we need to preserve all info but not duplicate unnecessarily. Might be okay to have some info in multiple sections if it's distinct aspect, but better to avoid duplication. Let's extract each piece: Location & 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." Also "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)." This is location/area info. 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." Also "Healthcare is global, and building the best ideas from around the world into Epic software is a point of pride." Pay: merit-based compensation, annual raises and bonuses, stock grants. Could be part of Benefits but we can separate. Responsibilities: design, deploy, operate application delivery platforms; building/maintaining secure scalable Windows-based infrastructure; automation, security hardening, cross-team collaboration. Requirements: relocation to Madison WI area (reimbursed) (maybe part of About role), 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 experience a 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. We need to avoid duplication: relocation appears both in About role and Requirements; we could keep it in About role (location) and not repeat in Requirements. But the requirement list includes "Relocation to the Madison, WI area (reimbursed)" as a bullet. Might be considered a requirement. However we can keep it in About role and not duplicate. But we must preserve all substantive information; if we omit it from Requirements, it's still present in About role, so it's preserved. That's fine. Now we need to format. We'll produce:

    About the role

    ... location, relocation assistance, campus perks, city accolades, etc.

    Maybe split location and campus perks into separate paragraphs. Responsibilities:

    Responsibilities

    • ...
    Requirements:

    Requirements

    • ...
    Pay:

    Pay

    ... merit-based compensation, annual raises and bonuses, stock grants.

    Benefits:

    Benefits

    • ... comprehensive benefits, healthcare global, etc.
    Also include sabbatical, meals, campus perks? But we already used campus perks in About role. Might duplicate. Better to keep campus perks in About role and not repeat in Benefits. Benefits could include comprehensive benefits, healthcare global, merit-based compensation (but that's Pay), annual raises and bonuses (Pay), stock grants (Pay). So Benefits could be just comprehensive benefits and healthcare global. But we also have "We offer comprehensive benefits to keep you healthy and happy as you grow in your life and career". That's vague. Could be a sentence. We could combine Pay and Benefits into one section "Compensation and Benefits". But rules say use headings for specific sections; we can create a section "Compensation and Benefits" if we want, but not listed in allowed headings? The allowed headings list includes Benefits, Pay, etc. We can use both. Thus: Pay: merit-based compensation, annual raises and bonuses, stock grants. Benefits: comprehensive benefits, healthcare global. Also we could add "four-week sabbatical after five years" as a benefit; but we already placed that in About role (campus perks). Might be better to move sabbatical to Benefits. Let's think: The sabbatical is a benefit. The campus perks (themed campus, meals, ability to get stuff done) are more about work environment. Could be part of About role or Benefits. To avoid duplication, we can put sabbatical in Benefits, and keep campus environment in About role. Thus About role: location, relocation assistance, city accolades, campus environment (themed campus, meals, ability to get stuff done). Benefits: comprehensive benefits, healthcare global, four-week sabbatical, etc. Pay: merit-based compensation, annual raises and bonuses, stock grants. Now we need to ensure we don't create sections with filler. All have content. Now craft the HTML. Let's write About the role paragraph(s): - Position based on campus in Madison, WI, requires relocation, financial relocation assistance provided. - Recruit nationally. - Live affordably in city known for rising tech talent; Epic just outside Madison, WI; second fastest growing market for tech talent; home to state capital and University of Wisconsin. - Madison accolades: greenest city (NerdWallet), best city for renters (SmartAsset), fittest city (Fitbit), third best metro for young professionals (Forbes Advisor). - Uniquely themed campus designed to heighten ability to get stuff done in office, conference room, or by fireplace in comfy chair. - All meals restaurant-quality but cost only a few dollars; prepared by kitchen talent from restaurants around the country. That's about it. Now Responsibilities: - Help design, deploy, and operate application delivery platforms that support Epic's internal staff, customers, and global training programs. - Part of Application Delivery workgroup

Similar jobs