Site Reliability Engineer (SRE) - FEDRAMP | NIGHTS | Remote
or drop it." So we can include a short p with that date maybe. - Note: successful applicant will be performing work on US Gov classified environments, must be US Person (citizen, national, lawful permanent resident, asylee, refugee). Also may perform work only by US citizen on US soil. - Note: In this role you will work 4X10 shifts (Wed-Sat) Midnight to 10am EST and must be able to work nights, weekends and on-call during your shift. This position is remote. - Splunk description: building safer digital world etc. - Meet the Team: Join Splunk’s FedRAMP Cloud Ops team! Looking for experienced engineer to support next generation of large-scale cloud offering with operational/maintenance and documentation support. - Your Impact: Individuals will be cross collaborating with multiple teams to: * Test features in our Splunk Cloud offering * Develop and update documentation around configuration and infrastructure changes * Execute configuration and infrastructure changes on customer cloud environments * Lead customer related incidents in troubleshooting the SplunkCloud platform. * Develop/update automation tools - We’re seeking an engineer with operational experience working at scale, with technical knowledge of large complex distributed systems. Hands-on experience with operating systems (particularly Linux), networking and, cloud technologies (particularly AWS). - As a key member of the team, you have an insatiable appetite for technology, a deep passion for learning, and a love for teamwork in an open and fun environment. - Minimum Qualifications: * 3+ years of Linux experience * 2+ years' experience scripting in Python, Golang or Bash * 3+ years' experience working on distributed systems * 1+ year experience participating in incident management - Preferred Qualifications: * Must be willing and able to acquire the SplunkCloud Architect Certification and either the Splunk administration or Splunk Power User certificate within the first 2 years of employment * Experience working with Puppet * Experience working with Jenkins * Experience working with AWS (preferred) or GCP * Experience scripting with Powershell * Experience with Microsoft Azure is a plus * AWS Solutions Architect certificate and/or experience - Why Cisco? (Cisco description) - maybe part of About the role? Could be "About the company" but not requested. We have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content. About the role: likely the introductory paragraphs about Splunk, FedRAMP Cloud Ops team, remote, shift, US Person requirement, etc. Responsibilities: the bullet list under "Your Impact". Requirements: maybe Minimum Qualifications? Or could be "Requirements" for mandatory items (US Person, shift, remote, etc). But we have Minimum Qualifications and Preferred Qualifications. Could treat Minimum as Requirements, Preferred as Qualifications? Or Skills separate. We need to follow typical job posting: About the role (description), Responsibilities (duties), Requirements (mandatory), Qualifications (preferred), Skills (technical skills), Benefits, Pay, Schedule. We must not create sections with filler like "commensurate with experience". Must only include if real content. We have Pay: salary ranges provided: starting salary range posted for this position is $128,600.00 to $184,900.00 (U.S. and/or Canada). Also full salary ranges for specific locations: New York City Metro Area $155,000.00 - $256,000.00; Non-Metro New York State & Washington State $138,100.00 - $227,900.00. Also note about incentive compensation etc. So we have pay info. Schedule: shift info: 4X10 shifts (Wed-Sat) Midnight to 10am EST, must be able to work nights, weekends and on-call during your shift. Position remote. Benefits: Cisco benefits described: medical, dental, vision insurance, 401(k) with match, paid parental leave, short/long-term disability, basic life insurance, paid holidays, floating holiday, birthday day off, year-end shutdown, 4 paid days off for personal wellness, vacation time details, sick time, volunteer days, bonuses, stock units, etc. So we have benefits. Thus we can include Benefits, Pay, Schedule sections. Now we need to output HTML fragment only, no or . Use
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title as heading. Not include Job ID.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can condense into prose or lists as appropriate, but must not lose detail. However we must not create filler sections.
We need to decide what goes where.
Let's outline:
- Opening paragraph: maybe a short p with application window close date? Could be considered metadata; we can include as a short p before sections.
- About the role: include description of Splunk, FedRAMP Cloud Ops team, remote, shift, US Person requirement, mission, team description.
We need to include the US Person requirement and classified environment note. Also note about performing work only by US citizen on US soil.
Also note about remote.
Also note about shift.
Also note about Splunk description.
Also note about "Meet the Team Join Splunk’s FedRAMP Cloud Ops team! We are looking for an experienced engineer to support the next generation of our large-scale cloud offering with operational/ maintenance and documentation support."
Also note about "Come help organizations be their best, while you reach new heights with a team that has your back."
Also note about "Splunk, a Cisco company, is building a safer and more resilient digital world with an end-to-end full stack platform made for a hybrid, multi-cloud world. Leading enterprises use our unified security and observability platform to keep their digital systems secure and reliable."
Also note about "Why Cisco?" maybe part of About the role or could be separate but we don't have a section for company description; we could include in About the role.
Thus About the role will be a few paragraphs.
- Responsibilities: list the bullet points under "Your Impact": Test features, Develop/update documentation, Execute configuration/infrastructure changes, Lead customer related incidents, Develop/update automation tools.
We could also include "cross collaborating with multiple teams" as part of responsibilities.
- Requirements: maybe include Minimum Qualifications and US Person requirement, shift requirement, remote? But shift and remote could be in Schedule. US Person requirement could be in Requirements.
We could treat Requirements as mandatory qualifications: 3+ years Linux, 2+ years scripting (Python/Golang/Bash), 3+ years distributed systems, 1+ year incident management, US Person eligibility, ability to work nights/weekends/on-call, remote work capability.
But we also have shift specifics (4X10 Wed-Sat Midnight-10am EST). That's schedule.
Thus Requirements could be the mandatory qualifications (minimum). We'll list them as
.
- Qualifications: Preferred Qualifications list: SplunkCloud Architect Cert, Splunk admin or Power User cert within 2 years, Puppet, Jenkins, AWS or GCP, Powershell scripting, Azure experience plus, AWS Solutions Architect cert/experience.
- Skills: maybe technical skills: Linux, networking, cloud (AWS), scripting languages, incident management, automation tools, etc. But we already have those in requirements/qualifications. Could combine but we need to avoid duplication. Perhaps we can put Skills as a list of technical competencies: Linux, networking, cloud (AWS/GCP), scripting (Python, Golang, Bash, Powershell), Puppet, Jenkins, incident management, automation, documentation, etc. But we must not invent; we can derive from the posting.
But we must preserve all substantive info; we can include them in Requirements and Qualifications; Skills could be optional but we need to decide if we have real specific content for Skills. The posting does not have a separate "Skills" section; but we can extract skills from the qualifications. However the instruction: "Prefer a few substantive sections over many thin ones." So maybe we skip Skills if it would be thin. But we need to include all substantive info; we can put those details in Requirements and Qualifications. So we could omit Skills section entirely.
But the instruction says: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not mandatory to include all. It says "include a section ONLY when the posting has real, specific content for it". So we can omit Skills if we don't have distinct content beyond what's already covered.
Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule.
We also might include a short p for application window date.
Now we need to ensure we don't include boilerplate like EEO, legal, etc. The posting includes some Cisco benefits description; we keep that as Benefits.
We must not include duplicated lines.
Now craft HTML.
We'll start with a p for application window close: maybe "
Application window expected to close on: 10/11/2026
".
Then About the role: maybe multiple paragraphs.
We need to preserve all substantive info; we can split into paragraphs but keep details.
Let's draft About the role:
Paragraph 1: Splunk, a Cisco company, is building a safer and more resilient digital world with an end-to-end full stack platform made for a hybrid, multi-cloud world. Leading enterprises use our unified security and observability platform to keep their digital systems secure and reliable.
Paragraph 2: Come help organizations be their best, while you reach new heights with a team that has your back. Meet the Team Join Splunk’s FedRAMP Cloud Ops team! We are looking for an experienced engineer to support the next generation of our large-scale cloud offering with operational/maintenance and documentation support.
Paragraph 3: This position is remote. The successful applicant will be performing work on US Government classified environments, and therefore, must be a U.S. Person (i.e., U.S. citizen, U.S. national, lawful permanent resident, asylee, or refugee). This position may also perform work that the U.S. government has specified can only be performed by a U.S. citizen on U.S. soil.
Paragraph 4: In this role you will work 4X10 shifts (Wed-Sat) Midnight to 10am EST and must be able to work nights, weekends and on-call during your shift.
That covers About the role.
Now Responsibilities: list bullet points.
We'll create - Test features in our Splunk Cloud offering
etc.
Also maybe include "Develop and update documentation around configuration and infrastructure changes", "Execute configuration and infrastructure changes on customer cloud environments", "Lead customer related incidents in troubleshooting the SplunkCloud platform.", "Develop/update automation tools". Also maybe "Cross collaborating with multiple teams" but that's covered.
Now Requirements: Minimum Qualifications.
List:
- 3+ years of Linux experience
- 2+ years' experience scripting in Python, Golang or Bash
- 3+ years' experience working on distributed systems
- 1+ year experience participating in incident management
- Must be a
for prose. We must not repeat job title as heading. Not include Job ID. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can condense into prose or lists as appropriate, but must not lose detail. However we must not create filler sections. We need to decide what goes where. Let's outline: - Opening paragraph: maybe a short p with application window close date? Could be considered metadata; we can include as a short p before sections. - About the role: include description of Splunk, FedRAMP Cloud Ops team, remote, shift, US Person requirement, mission, team description. We need to include the US Person requirement and classified environment note. Also note about performing work only by US citizen on US soil. Also note about remote. Also note about shift. Also note about Splunk description. Also note about "Meet the Team Join Splunk’s FedRAMP Cloud Ops team! We are looking for an experienced engineer to support the next generation of our large-scale cloud offering with operational/ maintenance and documentation support." Also note about "Come help organizations be their best, while you reach new heights with a team that has your back." Also note about "Splunk, a Cisco company, is building a safer and more resilient digital world with an end-to-end full stack platform made for a hybrid, multi-cloud world. Leading enterprises use our unified security and observability platform to keep their digital systems secure and reliable." Also note about "Why Cisco?" maybe part of About the role or could be separate but we don't have a section for company description; we could include in About the role. Thus About the role will be a few paragraphs. - Responsibilities: list the bullet points under "Your Impact": Test features, Develop/update documentation, Execute configuration/infrastructure changes, Lead customer related incidents, Develop/update automation tools. We could also include "cross collaborating with multiple teams" as part of responsibilities. - Requirements: maybe include Minimum Qualifications and US Person requirement, shift requirement, remote? But shift and remote could be in Schedule. US Person requirement could be in Requirements. We could treat Requirements as mandatory qualifications: 3+ years Linux, 2+ years scripting (Python/Golang/Bash), 3+ years distributed systems, 1+ year incident management, US Person eligibility, ability to work nights/weekends/on-call, remote work capability. But we also have shift specifics (4X10 Wed-Sat Midnight-10am EST). That's schedule. Thus Requirements could be the mandatory qualifications (minimum). We'll list them as
- .
- Qualifications: Preferred Qualifications list: SplunkCloud Architect Cert, Splunk admin or Power User cert within 2 years, Puppet, Jenkins, AWS or GCP, Powershell scripting, Azure experience plus, AWS Solutions Architect cert/experience.
- Skills: maybe technical skills: Linux, networking, cloud (AWS), scripting languages, incident management, automation tools, etc. But we already have those in requirements/qualifications. Could combine but we need to avoid duplication. Perhaps we can put Skills as a list of technical competencies: Linux, networking, cloud (AWS/GCP), scripting (Python, Golang, Bash, Powershell), Puppet, Jenkins, incident management, automation, documentation, etc. But we must not invent; we can derive from the posting.
But we must preserve all substantive info; we can include them in Requirements and Qualifications; Skills could be optional but we need to decide if we have real specific content for Skills. The posting does not have a separate "Skills" section; but we can extract skills from the qualifications. However the instruction: "Prefer a few substantive sections over many thin ones." So maybe we skip Skills if it would be thin. But we need to include all substantive info; we can put those details in Requirements and Qualifications. So we could omit Skills section entirely.
But the instruction says: "Use
- Test features in our Splunk Cloud offering etc. Also maybe include "Develop and update documentation around configuration and infrastructure changes", "Execute configuration and infrastructure changes on customer cloud environments", "Lead customer related incidents in troubleshooting the SplunkCloud platform.", "Develop/update automation tools". Also maybe "Cross collaborating with multiple teams" but that's covered. Now Requirements: Minimum Qualifications. List: - 3+ years of Linux experience - 2+ years' experience scripting in Python, Golang or Bash - 3+ years' experience working on distributed systems - 1+ year experience participating in incident management - Must be a
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not mandatory to include all. It says "include a section ONLY when the posting has real, specific content for it". So we can omit Skills if we don't have distinct content beyond what's already covered. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. We also might include a short p for application window date. Now we need to ensure we don't include boilerplate like EEO, legal, etc. The posting includes some Cisco benefits description; we keep that as Benefits. We must not include duplicated lines. Now craft HTML. We'll start with a p for application window close: maybe "
Application window expected to close on: 10/11/2026
". Then About the role: maybe multiple paragraphs. We need to preserve all substantive info; we can split into paragraphs but keep details. Let's draft About the role: Paragraph 1: Splunk, a Cisco company, is building a safer and more resilient digital world with an end-to-end full stack platform made for a hybrid, multi-cloud world. Leading enterprises use our unified security and observability platform to keep their digital systems secure and reliable. Paragraph 2: Come help organizations be their best, while you reach new heights with a team that has your back. Meet the Team Join Splunk’s FedRAMP Cloud Ops team! We are looking for an experienced engineer to support the next generation of our large-scale cloud offering with operational/maintenance and documentation support. Paragraph 3: This position is remote. The successful applicant will be performing work on US Government classified environments, and therefore, must be a U.S. Person (i.e., U.S. citizen, U.S. national, lawful permanent resident, asylee, or refugee). This position may also perform work that the U.S. government has specified can only be performed by a U.S. citizen on U.S. soil. Paragraph 4: In this role you will work 4X10 shifts (Wed-Sat) Midnight to 10am EST and must be able to work nights, weekends and on-call during your shift. That covers About the role. Now Responsibilities: list bullet points. We'll create