Staff Site Reliability Engineer (SRE) (Hybrid)

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the job posting. Key info: - Application window close date: 09/29/2026 (metadata, can be short p) - Hybrid position requiring approx 2 days per week on-site at Cisco offices in either San Francisco, San Jose, or New York City. (Schedule? Actually schedule info: hybrid, 2 days on-site. Could be Schedule section.) - The Splunk Agent Resilience team... description (About the role) - As a Staff Site Reliability Engineer (SRE), you will provide technical leadership... (Responsibilities) - Your Impact bullet list (Responsibilities) - Minimum Qualifications (Requirements/Qualifications) - Preferred Qualifications (Skills? maybe Skills) - Why Cisco? (maybe About the company, but not required) - Message to applicants... includes salary range (Pay) and benefits (Benefits) - Also includes details about vacation etc (Benefits) - Also includes location-based salary ranges (Pay) - Also includes info about bonuses etc (maybe Benefits) - Also includes info about application window close date (metadata) - Also includes hybrid schedule (Schedule) We must not repeat job title as heading. The title is Staff Site Reliability Engineer (SRE) but we shouldn't put that as heading. We need to produce sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. - About the role: we have description of team and role: "The Splunk Agent Resilience team is defining the future of AI resilience..." plus maybe the first paragraph about role. So we can put that. - Responsibilities: we have bullet list under "Your Impact" and also earlier description of what you will do. So we can combine. - Requirements: Minimum Qualifications. - Qualifications: maybe Preferred Qualifications? Actually we have Minimum Qualifications and Preferred Qualifications. Could map Minimum to Requirements, Preferred to Qualifications or Skills. But we have both Requirements and Qualifications sections allowed. Could put Minimum under Requirements, Preferred under Qualifications. - Skills: maybe we could extract specific skills from Preferred Qualifications (expertise in observability, programming Python/Go, Terraform, MLOps, networking, etc). Could put under Skills. - Benefits: we have benefits description (medical, dental, vision, 401k, parental leave, disability, life insurance, stock units, paid time off, holidays, sick time, volunteer days, bonuses). So we can include Benefits. - Pay: we have salary range and location-based ranges. So include Pay. - Schedule: hybrid position requiring approx 2 days per week on-site. So include Schedule. We must not include filler like "commensurate with experience". Not present. We must not include boilerplate like EEO, legal, etc. We removed those. We must not repeat job title as heading. We must not include Job ID/requisition numbers. We must output only HTML fragment, no /, no markdown fences. We need to use

for section headings,

• for any list of duties/requirements/benefits, and

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. We need to include all substantive info from the posting, but we can condense into lists but must preserve detail. However we must not lose detail. For example, we need to keep the exact bullet points from "Your Impact". We can turn each sentence into

• . Must keep the content. Similarly for Minimum Qualifications: we need to keep each requirement. Preferred Qualifications: we need to keep each bullet. Benefits: we need to keep each benefit item. Pay: we need to keep salary ranges. Schedule: we need to keep hybrid schedule. Also include application window close date maybe as a short p at top. We must not include duplicated lines. Let's extract content. First, parse the posting: - "The application window is expected to close on: 09/29/2026" -> metadata. - "This is a Hybrid position requiring approximately 2 days per week on-site at Cisco offices in either San Francisco, San Jose, or New York City." -> schedule. - "The Splunk Agent Resilience team is defining the future of AI resilience. Together 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 expertly deploy and manage AI-powered applications with enhanced observability and control." -> about the role/team. - "As a Staff Site Reliability Engineer (SRE), you will provide technical leadership for the reliability, scalability, and operational architecture of Splunk Agent Observability's platform. You will define the long-term reliability strategy, lead major infrastructure initiatives, and drive engineering excellence across deployment automation, production operations, and platform resiliency. In addition to owning complex production systems, you will influence engineering direction across teams and establish best practices for operating large-scale cloud and on-prem deployments." -> responsibilities intro. - "Your Impact" bullet list: - Define and drive the technical roadmap for platform reliability, scalability, and operational excellence. - Lead the architecture and evolution of deployment platforms supporting cloud and air-gapped customer environments. - Establish reliability engineering standards, including service level objectives (SLOs), operational readiness, capacity planning, and resiliency reviews. - Lead major reliability and scalability initiatives across Kubernetes, deployment infrastructure, databases, and networking. - Drive automation to eliminate operational toil and improve engineering productivity. - Design and build internal platforms, frameworks, and tooling that enable reliable operations at scale. - Lead complex production incident response and drive systemic improvements through root cause analysis and long-term remediation. - Partner with engineering leadership to influence platform architecture, deployment strategy, and production readiness. - Mentor engineers and raise the engineering bar through technical leadership, design reviews, and operational guidelines. - Collaborate with customers and internal teams to build secure, scalable, and highly reliable deployment architectures for both cloud and on-prem environments. - "Minimum Qualifications" bullet list (actually sentences): - 8+ years’ experience with a Bachelor's degree or 6+ yrs with Masters or 3+ years with a PhD, or equivalent related experience; Experience to include at least 6 years in Site Reliability Engineering, Platform / Cloud / Infrastructure Engineering, or related fields. - 5+ years’ operating large-scale Kubernetes platforms in production. - Experience designing highly available, scalable, and resilient distributed systems. - Experience with AWS, GCP, or other public cloud platforms. - Strong experience designing CI/CD platforms and deployment automation at scale. - "Preferred Qualifications" bullet list: - Expertise in observability, monitoring, alerting, capacity planning, and performance engineering. - Strong programming skills in Python and/or Go - Deep experience with Infrastructure as Code (Terraform or similar) - Experience with MLOps preferred - Strong understanding of networking, distributed systems, storage, databases, and cloud architecture - Experience operating both SaaS and enterprise/on-prem deployments - Demonstrated technical leadership across multiple engineering teams - Experience leading incident management, postmortems, and long-term reliability initiatives - "Why Cisco?" paragraph: we could treat as About the company but not required; we could omit as not a required section. But we might include under About the role? Probably not needed. The instruction: include a section ONLY when the posting has real, specific content for it. We have content for About the role (team description). We could also include Why Cisco? as part of About the role or maybe as a separate section like "About Cisco". But we only have predefined headings; we could put it under About the role as additional prose. However we must not invent sections. We can keep it as part of About the role paragraph. - "Message to applicants applying to work in the U.S. and/or Canada:" includes salary range and benefits details. We need to extract Pay and Benefits. Pay content: - "The starting salary range posted for this position is $186,900.00 to $267,700.00 and reflects the projected salary range for new hires in this position in U.S. and/or Canada locations, not including incentive compensation*, equity, or benefits. Individual pay is determined by the candidate's hiring location, market conditions, job-related skillset, experience, qualifications, education, certifications, and/or training. The full salary range for certain locations is listed below. For locations not listed below, the recruiter can share more details about compensation for the role in your location during the hiring process." - Then list: - U.S. employees are offered benefits... (that's benefits) - Then later: "The applicable full salary ranges for this position, by specific state, are listed below: New York City Metro Area $186,900.00 - $307,800.00 Non-Metro New York State & Washington State $166,300.00 - $274,100.00" - Also: "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." (but this is not relevant as role is SRE, not sales). Might still be part of Pay but we can keep. - Also: "Employees in Illinois, whether exempt or non-exempt, will participate in a unique time off program to meet local requirements." (that's benefits). Thus Pay section should include the salary ranges and note about determination. Benefits section should include: - 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 employees - 1 paid day off for employee’s birthday, paid year-end holiday shutdown, and 4 paid days off for personal wellness determined by Cisco - Non-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 employees - Exempt 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 next - Additional paid time away may be requested to deal with critical or emergency issues for family members - Optional 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. (maybe not needed but it's part of benefits) - 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 7