Splunk Engineer
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use - for lists
- Use
for prose
- Do NOT repeat job title as heading
- Do NOT put Job ID/requisition numbers as headings
- Preserve ALL substantive information
- Remove boilerplate (EEO, equal opportunity, scam warnings, application instructions)
- Include section ONLY when real specific content exists
- Never emit heading followed by filler/placeholder text
- Never create Pay/Schedule/Benefits unless posting actually states them
- Output ONLY HTML fragment, no html/body, no markdown fences
Let me parse the content:
1. First paragraph: "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 location/relocation info.
2. Second paragraph: "Splunk is one of the key technologies Epic relies on to improve healthcare delivery to over 70% of patients in the US, and around the world. As a Splunk Engineer, you'll optimize and maintain our cloud installation and help teams realize the potential of the Splunk platform. Our deployment serves critical areas including IT operations, Security, R&D, and Business Intelligence. You'll have the freedom to flex your creativity as well as identify and implement new and impactful use cases for Splunk." -> This is About the role / Responsibilities.
3. "Desired Skills and Knowledge Areas:" followed by bullet points:
- Bachelor's Degree
- 1+ year of Splunk Administration experience.
- Cribl experience is a plus.
- Experience with CI/CD concepts and technologies. GitLab experience is a plus.
- Familiarity with Infrastructure as Code concepts and technologies. Experience with Ansible and Terraform is a plus.
- Strong troubleshooting and customer service skills.
4. Next paragraph: "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.
5. Next paragraph: "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." -> Campus benefits.
6. Next paragraph: "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 compensation.
7. Next paragraph: "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." -> EEO boilerplate, should remove.
8. Then a list at the end:
- Bachelor's Degree
- Relocation to the Madison, WI area (reimbursed).
- A history of academic and professional success
- Eligible to work in the U.S. without visa sponsorship.
- COVID-19 vaccination
This seems like a summary of requirements. Some duplication with earlier list.
I need to structure this into sections. Let me decide on sections:
- About the role (the intro about Splunk at Epic)
- Responsibilities (what the engineer will do)
- Requirements (the desired skills list)
- Benefits (campus, meals, sabbatical, comprehensive benefits, compensation)
- Location (Madison details, relocation assistance)
- Additional Requirements (the final list: degree, relocation, academic success, work eligibility, vaccination)
But note: "Bachelor's Degree" appears in both lists. I should consolidate.
Also, the rules say: "Prefer a few substantive sections over many thin ones." So maybe combine Location and Relocation into one section.
Let me create sections:
1. About the role (prose)
2. Responsibilities (prose or list? The text says "you'll optimize and maintain... help teams realize... freedom to flex creativity... identify and implement new use cases". Could be a list or prose. I'll use prose since it's narrative.)
3. Requirements (list from Desired Skills and Knowledge Areas)
4. Benefits (list from the benefits paragraphs)
5. Location & Relocation (prose about Madison and relocation assistance)
6. Additional Requirements (the final list, but note duplication)
But the final list includes "Bachelor's Degree" and "Relocation to Madison, WI area (reimbursed)" which are already covered. Also "A history of academic and professional success" is vague. "Eligible to work in the U.S. without visa sponsorship" and "COVID-19 vaccination" are specific.
I should include all substantive info. The final list seems like a summary of requirements. I'll include it as "Requirements" or "Qualifications". But we already have a Requirements section from Desired Skills. Maybe combine.
Better: Have one "Requirements" section that includes both the Desired Skills list and the final list, but avoid duplication. However, the final list includes items not in Desired Skills: "A history of academic and professional success", "Eligible to work in the U.S. without visa sponsorship", "COVID-19 vaccination". Also "Relocation to Madison, WI area (reimbursed)" is in Location.
I'll structure:
- About the role
- Responsibilities
- Requirements (combining Desired Skills and the final list, but unique)
- Benefits
- Location & Relocation
But the rules say use headings like "Requirements", "Qualifications", "Skills". I'll use "Requirements" for the skills list, and maybe "Qualifications" for the final list? But they are similar. The user said "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I can use both Requirements and Qualifications if distinct.
However, the posting has "Desired Skills and Knowledge Areas" and then a separate list at the end. The end list seems like "Qualifications" or "Requirements". I'll make two sections: "Requirements" for the technical skills, and "Qualifications" for the other requirements (degree, relocation, work eligibility, vaccination, academic success). But "Bachelor's Degree" appears in both. I'll include in Qualifications.
Alternatively, combine into one "Requirements" section with sub-lists? But the rule says use - for any list. I can have multiple lists under one heading.
Let me think: The user wants clean semantic HTML. I'll create sections as appropriate.
I'll do:
About the role
...
Responsibilities
...
(or list)
Requirements
- ...
(from Desired Skills)
Qualifications
- ...
(from final list, but exclude duplicates)
Benefits
- ...
(from benefits paragraphs)
Location & Relocation
...
(Madison details and relocation assistance)
But the benefits paragraphs are prose, not list. I can convert to list items.
Let me extract benefits:
- Uniquely themed campus designed for productivity
- Restaurant-quality meals at low cost
- Four-week sabbatical after five years (with examples)
- Comprehensive benefits for health and happiness
- Merit-based compensation reflecting impact
- Annual raises and bonuses
- Stock grants
Also location benefits: Madison accolades.
I'll include location benefits in Location section.
Now, the EEO paragraph should be removed.
Also, the line "Please see our full non-discrimination statement at https://careers.epic.com/EEO." is boilerplate.
Now, the final list: "Bachelor's Degree", "Relocation to the Madison, WI area (reimbursed).", "A history of academic and professional success", "Eligible to work in the U.S. without visa sponsorship.", "COVID-19 vaccination"
Note: "Relocation to the Madison, WI area (reimbursed)." is already in Location section. I'll keep it in Qualifications as a requirement.
But the rule: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short or drop it." This is not Job ID.
I'll include all.
Now, write HTML.
I need to output only the HTML fragment.
Let me draft.
First, About the role: combine first two paragraphs? Actually first paragraph is location/relocation. Second paragraph is about Splunk at Epic and role. I'll put first paragraph in Location & Relocation, second in About the role.
But the first paragraph: "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." That's location and relocation.
Second paragraph: "Splunk is one of the key technologies Epic relies on to improve healthcare delivery to over 70% of patients in the US, and around the world. As a Splunk Engineer, you'll optimize and maintain our cloud installation and help teams realize the potential of the Splunk platform. Our deployment serves critical areas including IT operations, Security, R&D, and Business Intelligence. You'll have the freedom to flex your creativity as well as identify and implement new and impactful use cases for Splunk." That's About the role and Responsibilities.
I'll split: About the role (first two sentences), Responsibilities (the rest).
But the rule: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I can have both.
Let me do:
About the role
Splunk is one of the key technologies Epic relies on to improve healthcare delivery to over 70% of patients in the US, and around the world.
Responsibilities
As a Splunk Engineer, you'll optimize and maintain our cloud installation and help teams realize the potential of the Splunk platform. Our deployment serves critical areas including IT operations, Security, R&D, and Business Intelligence. You'll have the freedom to flex your creativity as well as identify and implement new and impactful use cases for Spl
for prose - Do NOT repeat job title as heading - Do NOT put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove boilerplate (EEO, equal opportunity, scam warnings, application instructions) - Include section ONLY when real specific content exists - Never emit heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits unless posting actually states them - Output ONLY HTML fragment, no html/body, no markdown fences Let me parse the content: 1. First paragraph: "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 location/relocation info. 2. Second paragraph: "Splunk is one of the key technologies Epic relies on to improve healthcare delivery to over 70% of patients in the US, and around the world. As a Splunk Engineer, you'll optimize and maintain our cloud installation and help teams realize the potential of the Splunk platform. Our deployment serves critical areas including IT operations, Security, R&D, and Business Intelligence. You'll have the freedom to flex your creativity as well as identify and implement new and impactful use cases for Splunk." -> This is About the role / Responsibilities. 3. "Desired Skills and Knowledge Areas:" followed by bullet points: - Bachelor's Degree - 1+ year of Splunk Administration experience. - Cribl experience is a plus. - Experience with CI/CD concepts and technologies. GitLab experience is a plus. - Familiarity with Infrastructure as Code concepts and technologies. Experience with Ansible and Terraform is a plus. - Strong troubleshooting and customer service skills. 4. Next paragraph: "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. 5. Next paragraph: "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." -> Campus benefits. 6. Next paragraph: "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 compensation. 7. Next paragraph: "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." -> EEO boilerplate, should remove. 8. Then a list at the end: - Bachelor's Degree - Relocation to the Madison, WI area (reimbursed). - A history of academic and professional success - Eligible to work in the U.S. without visa sponsorship. - COVID-19 vaccination This seems like a summary of requirements. Some duplication with earlier list. I need to structure this into sections. Let me decide on sections: - About the role (the intro about Splunk at Epic) - Responsibilities (what the engineer will do) - Requirements (the desired skills list) - Benefits (campus, meals, sabbatical, comprehensive benefits, compensation) - Location (Madison details, relocation assistance) - Additional Requirements (the final list: degree, relocation, academic success, work eligibility, vaccination) But note: "Bachelor's Degree" appears in both lists. I should consolidate. Also, the rules say: "Prefer a few substantive sections over many thin ones." So maybe combine Location and Relocation into one section. Let me create sections: 1. About the role (prose) 2. Responsibilities (prose or list? The text says "you'll optimize and maintain... help teams realize... freedom to flex creativity... identify and implement new use cases". Could be a list or prose. I'll use prose since it's narrative.) 3. Requirements (list from Desired Skills and Knowledge Areas) 4. Benefits (list from the benefits paragraphs) 5. Location & Relocation (prose about Madison and relocation assistance) 6. Additional Requirements (the final list, but note duplication) But the final list includes "Bachelor's Degree" and "Relocation to Madison, WI area (reimbursed)" which are already covered. Also "A history of academic and professional success" is vague. "Eligible to work in the U.S. without visa sponsorship" and "COVID-19 vaccination" are specific. I should include all substantive info. The final list seems like a summary of requirements. I'll include it as "Requirements" or "Qualifications". But we already have a Requirements section from Desired Skills. Maybe combine. Better: Have one "Requirements" section that includes both the Desired Skills list and the final list, but avoid duplication. However, the final list includes items not in Desired Skills: "A history of academic and professional success", "Eligible to work in the U.S. without visa sponsorship", "COVID-19 vaccination". Also "Relocation to Madison, WI area (reimbursed)" is in Location. I'll structure: - About the role - Responsibilities - Requirements (combining Desired Skills and the final list, but unique) - Benefits - Location & Relocation But the rules say use headings like "Requirements", "Qualifications", "Skills". I'll use "Requirements" for the skills list, and maybe "Qualifications" for the final list? But they are similar. The user said "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I can use both Requirements and Qualifications if distinct.
However, the posting has "Desired Skills and Knowledge Areas" and then a separate list at the end. The end list seems like "Qualifications" or "Requirements". I'll make two sections: "Requirements" for the technical skills, and "Qualifications" for the other requirements (degree, relocation, work eligibility, vaccination, academic success). But "Bachelor's Degree" appears in both. I'll include in Qualifications.
Alternatively, combine into one "Requirements" section with sub-lists? But the rule says use - for any list. I can have multiple lists under one heading.
Let me think: The user wants clean semantic HTML. I'll create sections as appropriate.
I'll do:
About the role
...
Responsibilities
...
(or list)
Requirements
- ...
(from Desired Skills)
Qualifications
- ...
(from final list, but exclude duplicates)
Benefits
- ...
(from benefits paragraphs)
Location & Relocation
...
(Madison details and relocation assistance)
But the benefits paragraphs are prose, not list. I can convert to list items.
Let me extract benefits:
- Uniquely themed campus designed for productivity
- Restaurant-quality meals at low cost
- Four-week sabbatical after five years (with examples)
- Comprehensive benefits for health and happiness
- Merit-based compensation reflecting impact
- Annual raises and bonuses
- Stock grants
Also location benefits: Madison accolades.
I'll include location benefits in Location section.
Now, the EEO paragraph should be removed.
Also, the line "Please see our full non-discrimination statement at https://careers.epic.com/EEO." is boilerplate.
Now, the final list: "Bachelor's Degree", "Relocation to the Madison, WI area (reimbursed).", "A history of academic and professional success", "Eligible to work in the U.S. without visa sponsorship.", "COVID-19 vaccination"
Note: "Relocation to the Madison, WI area (reimbursed)." is already in Location section. I'll keep it in Qualifications as a requirement.
But the rule: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short or drop it." This is not Job ID.
I'll include all.
Now, write HTML.
I need to output only the HTML fragment.
Let me draft.
First, About the role: combine first two paragraphs? Actually first paragraph is location/relocation. Second paragraph is about Splunk at Epic and role. I'll put first paragraph in Location & Relocation, second in About the role.
But the first paragraph: "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." That's location and relocation.
Second paragraph: "Splunk is one of the key technologies Epic relies on to improve healthcare delivery to over 70% of patients in the US, and around the world. As a Splunk Engineer, you'll optimize and maintain our cloud installation and help teams realize the potential of the Splunk platform. Our deployment serves critical areas including IT operations, Security, R&D, and Business Intelligence. You'll have the freedom to flex your creativity as well as identify and implement new and impactful use cases for Splunk." That's About the role and Responsibilities.
I'll split: About the role (first two sentences), Responsibilities (the rest).
But the rule: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I can have both.
Let me do:
About the role
Splunk is one of the key technologies Epic relies on to improve healthcare delivery to over 70% of patients in the US, and around the world.
Responsibilities
As a Splunk Engineer, you'll optimize and maintain our cloud installation and help teams realize the potential of the Splunk platform. Our deployment serves critical areas including IT operations, Security, R&D, and Business Intelligence. You'll have the freedom to flex your creativity as well as identify and implement new and impactful use cases for Spl
About the role
...
Responsibilities
...
(or list)Requirements
- ...
Qualifications
- ...
Benefits
- ...
Location & Relocation
...
(Madison details and relocation assistance) But the benefits paragraphs are prose, not list. I can convert to list items. Let me extract benefits: - Uniquely themed campus designed for productivity - Restaurant-quality meals at low cost - Four-week sabbatical after five years (with examples) - Comprehensive benefits for health and happiness - Merit-based compensation reflecting impact - Annual raises and bonuses - Stock grants Also location benefits: Madison accolades. I'll include location benefits in Location section. Now, the EEO paragraph should be removed. Also, the line "Please see our full non-discrimination statement at https://careers.epic.com/EEO." is boilerplate. Now, the final list: "Bachelor's Degree", "Relocation to the Madison, WI area (reimbursed).", "A history of academic and professional success", "Eligible to work in the U.S. without visa sponsorship.", "COVID-19 vaccination" Note: "Relocation to the Madison, WI area (reimbursed)." is already in Location section. I'll keep it in Qualifications as a requirement. But the rule: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a shortor drop it." This is not Job ID. I'll include all. Now, write HTML. I need to output only the HTML fragment. Let me draft. First, About the role: combine first two paragraphs? Actually first paragraph is location/relocation. Second paragraph is about Splunk at Epic and role. I'll put first paragraph in Location & Relocation, second in About the role. But the first paragraph: "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." That's location and relocation. Second paragraph: "Splunk is one of the key technologies Epic relies on to improve healthcare delivery to over 70% of patients in the US, and around the world. As a Splunk Engineer, you'll optimize and maintain our cloud installation and help teams realize the potential of the Splunk platform. Our deployment serves critical areas including IT operations, Security, R&D, and Business Intelligence. You'll have the freedom to flex your creativity as well as identify and implement new and impactful use cases for Splunk." That's About the role and Responsibilities. I'll split: About the role (first two sentences), Responsibilities (the rest). But the rule: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I can have both.
Let me do:
About the role
Splunk is one of the key technologies Epic relies on to improve healthcare delivery to over 70% of patients in the US, and around the world.
Responsibilities
As a Splunk Engineer, you'll optimize and maintain our cloud installation and help teams realize the potential of the Splunk platform. Our deployment serves critical areas including IT operations, Security, R&D, and Business Intelligence. You'll have the freedom to flex your creativity as well as identify and implement new and impactful use cases for Spl