Senior Site Reliability Engineer (SRE) (Hybrid)

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 Job ID etc. Must preserve all substantive info, remove boilerplate, duplicate lines, application instructions. Must not include sections with filler like "commensurate with experience". Must include Pay and Schedule only if posting actually states them. The posting includes salary range and benefits details, and schedule: Hybrid position requiring approx 2 days per week on-site. So we have Pay and Schedule content. Benefits: they list benefits (medical, dental, vision, 401k, parental leave, etc). So Benefits section. We need sections: About the role (maybe intro paragraph). Responsibilities (list of duties). Requirements (minimum qualifications). Qualifications (preferred qualifications). Skills (maybe combine? but we can separate). However we must not create thin sections. We can combine some. But we need to follow instruction: use headings for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Include a section only when posting has real specific content for it. So we need to decide which sections have content. We have: - About the role: description of team and role: "The Splunk Agent Resilience team is defining the future of AI resilience... As a Senior Site Reliability Engineer (SRE), you will build, operate, and continuously improve..." That's substantive. - Responsibilities: list of duties under "Your Impact": bullet points. - Requirements: Minimum Qualifications. - Qualifications: Preferred Qualifications. - Skills: Could be derived from both but maybe we can include a Skills section summarizing technical skills (Python/Go, Terraform, Kubernetes, etc). However we might risk duplication. But we can still include if we have specific content. The posting includes many skill mentions in both minimum and preferred. Could create Skills section summarizing them. But we must not repeat content? It says preserve ALL substantive information; do NOT invent or summarize away detail. So we cannot summarize away detail; we must keep the details. If we create a Skills section, we would need to list skills, but that would be summarizing (maybe okay if we just list them). However we risk losing detail if we omit some details. Better to keep details in Requirements and Qualifications sections, and not create a separate Skills section unless there is explicit skills list separate. The posting does not have a separate "Skills" heading; skills are embedded in qualifications. So we might omit Skills section to avoid thin/filler. - Benefits: yes. - Pay: yes (salary range). - Schedule: yes (Hybrid 2 days on-site). Thus we output sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. We must not include Job ID etc. Must not include boilerplate like EEO etc. Must remove duplicated lines, navigation, cookie, legal, scam-warning, etc. The posting includes a lot of Cisco benefits description; we need to keep that but remove fluff like "Message to applicants applying to work in the U.S. and/or Canada:" maybe keep as part of Benefits? It's about compensation and benefits. We'll keep the benefits description. We need to format:

About the role

then

...

. For lists use

• . We must preserve all substantive info; do not invent or summarize away detail. So we need to copy the text exactly? Not necessarily exact wording but must not lose detail. We'll paraphrase but keep all points. Let's extract content. About the role paragraph: "The Splunk Agent Resilience team is defining the future of AI resilience. Our team provides scalable, cost-effective evaluation and guardrails that ensure AI agents behave as intended, improving reliability and reducing risks. This unified approach empowers our customers to confidently deploy and manage AI-powered applications with enhanced observability and control. As a Senior Site Reliability Engineer (SRE), you will build, operate, and continuously improve the reliability, scalability, and operational excellence of Splunk Agent Observability's deployment platform and production infrastructure. You will own the operational backbone supporting both cloud and air-gapped customer deployments, develop automation to improve operational efficiency, and partner closely with engineering teams to deliver reliable, secure, and scalable systems." That's good. Responsibilities: list from "Your Impact": - Operate and improve Kubernetes-based production infrastructure and deployment systems - Own customer deployments across cloud and air-gapped environments, including installation, upgrades, troubleshooting, and lifecycle management - Build and improve deployment observability, monitoring, logging, and alerting - Improve reliability, scalability, and operational efficiency through automation and performance optimization - Participate in production incident response, root cause analysis, and reliability improvements - Tune infrastructure components—including databases and services—to improve performance and resilience - Design and develop internal tooling using Python and/or Go - Debug complex production issues spanning Kubernetes, networking, storage, and application layers - Manage infrastructure using Terraform or similar Infrastructure as Code tools - Collaborate with software engineers and customers to design secure, scalable, and reliable deployment architectures We'll put each as
• . Requirements (Minimum Qualifications): - 7+ years’ experience with a Bachelor's degree or 4+ yrs with a Masters or 1 year with a PhD, or equivalent related experience; Experience to include at least 4 years in Site Reliability Engineering, Platform / Cloud / Infrastructure Engineering, or related fields - 3+ years’ operating Kubernetes in production; experience with Helm - Experience building and maintaining CI/CD platforms and deployment automation - Experience working with AWS, GCP, or similar cloud platforms We'll keep as list. Qualifications (Preferred Qualifications): - Experience improving production reliability, scalability, and availability - Experience with monitoring, logging, observability, and alerting platforms - Strong scripting or programming skills in Python and/or Go - Experience with Infrastructure as Code tools such as Terraform - Experience with MLOps preferred - Solid understanding of networking fundamentals (VPCs, DNS, routing, load balancing) - Experience operating databases and tuning them for performance and reliability - Experience deploying and supporting cloud and air-gapped/on-prem environments - Strong debugging and troubleshooting skills across distributed systems We'll list. Benefits: The paragraph about benefits: "U.S. employees are offered benefits, subject to Cisco’s plan eligibility rules, which include medical, dental and vision insurance, a 401(k) plan with a Cisco matching contribution, paid parental leave, short and long-term disability coverage, and basic life insurance. Please see the Cisco careers site to discover more benefits and perks. Employees may be eligible to receive grants of Cisco restricted stock units, which vest following continued employment with Cisco for defined periods of time. U.S. employees are eligible for paid time away as described below, subject to Cisco’s policies: 10 paid holidays per full calendar year, plus 1 floating holiday for non-exempt employees1 paid day off for employee’s birthday, paid year-end holiday shutdown, and 4 paid days off for personal wellness determined by CiscoNon-exempt employees** receive 16 days of paid vacation time per full calendar year, accrued at rate of 4.92 hours per pay period for full-time employeesExempt employees participate in Cisco’s flexible vacation time off program, which has no defined limit on how much vacation time eligible employees may use (subject to availability and some business limitations)80 hours of sick time off provided on hire date and each January 1st thereafter, and up to 80 hours of unused sick time carried forward from one calendar year to the nextAdditional paid time away may be requested to deal with critical or emergency issues for family membersOptional 10 paid days per full calendar year to volunteer For non-sales roles, employees are also eligible to earn annual bonuses subject to Cisco’s policies. Employees On Sales Plans Earn Performance-based Incentive Pay On Top Of Their Base Salary, Which Is Split Between Quota And Non-quota Components, Subject To The Applicable Cisco Plan. For Quota-based Incentive Pay, Cisco Typically Pays As Follows .75% of incentive target for each 1% of revenue attainment up to 50% of quota;1.5% of incentive target for each 1% of attainment between 50% and 75%;1% of incentive target for each 1% of attainment between 75% and 100%; andOnce performance exceeds 100% attainment, incentive rates are at or above 1% for each 1% of attainment with no cap on incentive compensation. For non-quota-based sales performance elements such as strategic sales objectives, Cisco may pay 0% up to 125% of target. Cisco sales plans do not have a minimum threshold of performance for sales incentive compensation to be paid. The applicable full salary ranges for this position, by specific state, are listed below: New York City Metro Area $167,700.00 - $282,000.00 Non-Metro New York State & Washington State $149,100.00 - $250,900.00 For quota-based sales roles on Cisco’s sales plan, the ranges provided in this posting include base pay and sales target incentive compensation combined. Employees in Illinois, whether exempt or non-exempt, will participate in a unique time off program to meet local requirements." We need to separate Benefits and Pay sections. Benefits: medical, dental, vision, 401k, parental leave, disability, life insurance, RSU, paid holidays, floating holiday, birthday day off, year-end shutdown, personal wellness days, vacation, sick time, volunteer days, annual bonuses, etc. Pay: salary ranges. We need to avoid duplication: The benefits paragraph includes also salary ranges later; we will split. Thus Benefits section: list of benefits (medical, dental, vision insurance; 401(k) with Cisco match; paid parental leave; short and long-term disability; basic life insurance; Cisco RSU grants; paid holidays (10 per year + 1 floating for non-exempt); birthday paid day off; paid year-end holiday shutdown; 4 paid personal wellness days; vacation (non-exempt 16 days per year; exempt flexible); sick time (80 hours per year, carry forward); additional paid time for family emergencies; optional 10 paid volunteer days; annual bonuses (non-sales); sales incentive details (maybe keep as part of Pay? Actually it's about incentive pay, which is part of compensation. Could be considered Pay. But we already have Pay section for base salary ranges. The incentive details could be part of Pay or Benefits? It's compensation. Might be better to include in Pay section as details about incentive pay. However the instruction: include Pay section only if posting actually states them. It does state salary ranges and incentive details. So we can include Pay section with base salary range and incentive details. Thus Benefits section: medical, dental, vision, 401k match, parental leave, disability, life insurance, RSU, paid holidays, floating holiday, birthday day off, year-end shutdown, personal wellness days, vacation, sick time, volunteer days, annual bonuses (non-sales). We'll keep as list. Pay section: base salary range: $167,700.00 to $245,200.00 (U.S./Canada) plus location-specific ranges: NYC Metro $167,700-$282,000; Non-Metro NY & WA $149,100-$250,900. Also note that for quota-based sales roles, ranges include base + target incentive. Also incentive details: description of how incentive paid based on quota attainment. We'll include that. Schedule: Hybrid position requiring approx 2 days per week on-site at Cisco offices in either San Francisco, San Jose, or New York City. Now produce HTML. We must not include any markdown fences. Just raw HTML. Let's craft. We'll start with

  About the role

  ...