Software Engineering Technical Leader - SRE
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Remove boilerplate, navigation, etc. Must preserve all substantive info. We need to parse the posting. Key parts: - Application window close date: "The application window is expected to close on: 09/29/2026". This is metadata; we can put in a short
maybe. - "Meet the Team As a Site Reliability Engineering (SRE) Technical Leader on the Intersight Team you will play a key role..." This is about the role. Could be "About the role" section. - "Your Impact We are seeking an experienced Engineer..." This could be part of About the role or separate? Might be "About the role" includes both. - "Responsibilities Include ..." list. - "Minimum Qualifications ..." list. - "Preferred Qualifications ..." list. - "Why Cisco?" paragraph. - Salary info: "Message to applicants applying to work in the U.S. and/or Canada: The starting salary range posted for this position is $177,600.00 to $257,400.00 ..." plus details about location ranges. This is Pay section. - 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." Also details about PTO etc. That's Benefits. - Schedule? Not mentioned explicitly. No schedule info. So we should not create Schedule section. - Skills? Could be derived from qualifications but we have Requirements/Qualifications sections. We could combine Minimum and Preferred Qualifications into Requirements? The instruction: use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to use. We have Responsibilities, Minimum Qualifications, Preferred Qualifications (these could be under Requirements or Qualifications). We have Skills maybe from programming languages etc. But we can put under Qualifications. We should not create thin sections. So maybe we have: About the role, Responsibilities, Qualifications (combining min+preferred), Benefits, Pay. Possibly also "Why Cisco?" could be under About the role or separate "About Cisco". But we can incorporate into About the role or maybe a separate section "About Cisco". However the instruction list includes "About the role" as a heading; we can put the narrative there. The "Why Cisco?" could be part of About the role or separate but we can include as a paragraph under About the role. We must not repeat job title as heading. So no heading for "Site Reliability Engineering (SRE) Technical Leader". Good. We need to output only HTML fragment, no /, no markdown fences. We need to use
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from the posting, but we can format them.
We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting includes some boilerplate like "Message to applicants applying to work in the U.S. and/or Canada:" which is not boilerplate but salary info; we keep. The "Why Cisco?" is not boilerplate; we keep. The "U.S. employees are offered benefits..." we keep. The "Employees may be eligible to receive grants..." we keep. The "Employees On Sales Plans Earn Performance-based Incentive Pay..." we keep (though it's lengthy). The "The applicable full salary ranges for this position, by specific state, are listed below:" we keep.
We need to ensure we don't include duplicated lines. There's some duplication? Not obvious.
We need to avoid filler like "commensurate with experience", etc. Not present.
Now craft HTML.
Structure:
Application window expected to close on: 09/29/2026
About the role
... (combining Meet the Team, Your Impact, Why Cisco? maybe)
But we need to keep all details. Let's extract the prose:
From "Meet the Team As a Site Reliability Engineering (SRE) Technical Leader on the Intersight Team you will play a key role in ensuring the reliability, scalability, and security of our cloud platforms. The broader team is composed of experienced engineers who value innovation and accountability. You will represent the Intersight SRE team, working in a dynamic environment, tackling challenges with creativity, providing technical leadership in defining and delivering on the team's technical roadmap. You will collaborate with cross-functional teams, including software development, product management, customers and security teams, to design, influence, build, and maintain SaaS systems operating at multi-region scale. Your work will directly impact the success of our initiatives by ensuring the underlying platform infrastructure is robust, efficient, and aligned with operational excellence."
Then "Your Impact We are seeking an experienced Engineer to encourage and represent a high-performing team dedicated to ensuring the reliability and scalability of cloud services, with a focus on a rapidly growing next-generation project. The ideal candidate will have hands-on SRE or systems/network administration experience, with familiarity in AWS. This role involves close collaboration across product engineering, service engineering, and SRE teams in a high-trust, well-coordinated environment."
Then "Why Cisco? At Cisco, we’re revolutionizing how data and infrastructure connect and protect organizations in the AI era – and beyond. We’ve been innovating fearlessly for 40 years to create solutions that power how humans and technology work together across the physical and digital worlds. These solutions provide customers with unparalleled security, visibility, and insights across the entire digital footprint. Fueled by the depth and breadth of our technology, we experiment and create meaningful solutions. Add to that our worldwide network of doers and experts, and you’ll see that the opportunities to grow and build are limitless. We work as a team, collaborating with empathy to make really big things happen on a global scale. Because our solutions are everywhere, our impact is everywhere. We are Cisco, and our power starts with you."
We could keep these as separate paragraphs under About the role.
Now Responsibilities: list items.
We need to capture each bullet after "Responsibilities Include". The text:
"Design, build, and optimize cloud and data infrastructure to ensure the high availability, reliability, and scalability of systems to meet customer needs, while implementing SRE principles such as monitoring, alerting, error budgets, and fault analysis.
Collaborate closely with multi-functional teams, including customers, development, product management, and security teams, to create secure, scalable solutions and enhance operational efficiency through automation.
Troubleshoot complex technical problems in production environments, perform root cause analyses, and contribute to continuous improvement efforts through postmortem reviews and proactive performance optimization.
Lead the architectural vision and shape the team’s technical strategy and roadmap, balancing immediate needs with long-term goals, driving innovation, and influencing the technical direction.
Serve as a mentor and technical leader, guiding teams and fostering a culture of engineering and operational excellence by sharing your deep knowledge and experience.
Engage with customers and stakeholders to understand use cases and feedback, translating them into actionable insights and effectively influencing at all levels.
Apply your strong programming skills to integrate software and systems engineering, building core data platform capabilities and automation to meet enterprise customer needs and roadmap objectives.
Develop strategic roadmaps, processes, plans, and infrastructure to efficiently deploy new software components at an enterprise scale while enforcing engineering standards."
We'll put each as - .
Now Qualifications: we have Minimum Qualifications and Preferred Qualifications. Could combine under Qualifications heading with two sub-sections? But we only allowed headings list; we could have
Qualifications
and then within that we could have Minimum Qualifications:
... etc. Or we could separate into Requirements and Qualifications. But we have both Minimum and Preferred; we could treat Minimum as Requirements and Preferred as Qualifications. However the instruction list includes both Requirements and Qualifications as possible headings. We could use Requirements for Minimum Qualifications and Qualifications for Preferred Qualifications. That seems reasonable.
Thus:
Requirements
Minimum Qualifications
... (list items)
Qualifications
Preferred Qualifications
... (list items)
But we need to avoid repeating "Minimum Qualifications" as heading; we can just put a Minimum Qualifications:
then list.
Now Benefits: we have paragraph about benefits and PTO details. We'll put under Benefits
with ...
maybe multiple paragraphs.
Pay: we have salary range info and location-specific ranges. We'll put under Pay
with paragraphs.
We should not include Schedule.
Now ensure we preserve all substantive info: includes details about certifications, etc. Those are in Preferred Qualifications.
Check we didn't miss any details: The "Certifications: CKA (Certified Kubernetes Administrator), CKAD (Certified Kubernetes Application Developer), AWS Certified DevOps Engineer, or equivalent certifications in cloud and security domains." is part of Preferred Qualifications; we need to include that as a list item.
Also "Experience building/managing a cloud-based data platform, automation and orchestration of their infrastructure and maintaining high availability, system reliability at scale." etc.
Also "Ability to handle multiple competing priorities in a fast-paced environment"
Also "Experience in architecting software and infrastructure at scale with a sense of ownership and accountability."
Also "Strong passion for learning, researching, and developing innovative technologies that deliver significant customer impact."
Also "Exceptional communication and presentation skills, with the ability to translate complex technical concepts for non-experts while fostering collaboration and driving excellence within diverse technical teams."
Also "Experience in providing technical leadership and mentoring engineers."
Also "Experience with cloud and infrastructure security."
Now also the "Why Cisco?" paragraph we included.
Now also the "Message to applicants applying to work in the U.S. and/or Canada: The starting salary range posted for this position is $177,600.00 to $257,400.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. 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
for prose. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from the posting, but we can format them. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting includes some boilerplate like "Message to applicants applying to work in the U.S. and/or Canada:" which is not boilerplate but salary info; we keep. The "Why Cisco?" is not boilerplate; we keep. The "U.S. employees are offered benefits..." we keep. The "Employees may be eligible to receive grants..." we keep. The "Employees On Sales Plans Earn Performance-based Incentive Pay..." we keep (though it's lengthy). The "The applicable full salary ranges for this position, by specific state, are listed below:" we keep. We need to ensure we don't include duplicated lines. There's some duplication? Not obvious. We need to avoid filler like "commensurate with experience", etc. Not present. Now craft HTML. Structure:
Application window expected to close on: 09/29/2026
About the role
... (combining Meet the Team, Your Impact, Why Cisco? maybe)
But we need to keep all details. Let's extract the prose: From "Meet the Team As a Site Reliability Engineering (SRE) Technical Leader on the Intersight Team you will play a key role in ensuring the reliability, scalability, and security of our cloud platforms. The broader team is composed of experienced engineers who value innovation and accountability. You will represent the Intersight SRE team, working in a dynamic environment, tackling challenges with creativity, providing technical leadership in defining and delivering on the team's technical roadmap. You will collaborate with cross-functional teams, including software development, product management, customers and security teams, to design, influence, build, and maintain SaaS systems operating at multi-region scale. Your work will directly impact the success of our initiatives by ensuring the underlying platform infrastructure is robust, efficient, and aligned with operational excellence." Then "Your Impact We are seeking an experienced Engineer to encourage and represent a high-performing team dedicated to ensuring the reliability and scalability of cloud services, with a focus on a rapidly growing next-generation project. The ideal candidate will have hands-on SRE or systems/network administration experience, with familiarity in AWS. This role involves close collaboration across product engineering, service engineering, and SRE teams in a high-trust, well-coordinated environment." Then "Why Cisco? At Cisco, we’re revolutionizing how data and infrastructure connect and protect organizations in the AI era – and beyond. We’ve been innovating fearlessly for 40 years to create solutions that power how humans and technology work together across the physical and digital worlds. These solutions provide customers with unparalleled security, visibility, and insights across the entire digital footprint. Fueled by the depth and breadth of our technology, we experiment and create meaningful solutions. Add to that our worldwide network of doers and experts, and you’ll see that the opportunities to grow and build are limitless. We work as a team, collaborating with empathy to make really big things happen on a global scale. Because our solutions are everywhere, our impact is everywhere. We are Cisco, and our power starts with you." We could keep these as separate paragraphs under About the role. Now Responsibilities: list items. We need to capture each bullet after "Responsibilities Include". The text: "Design, build, and optimize cloud and data infrastructure to ensure the high availability, reliability, and scalability of systems to meet customer needs, while implementing SRE principles such as monitoring, alerting, error budgets, and fault analysis. Collaborate closely with multi-functional teams, including customers, development, product management, and security teams, to create secure, scalable solutions and enhance operational efficiency through automation. Troubleshoot complex technical problems in production environments, perform root cause analyses, and contribute to continuous improvement efforts through postmortem reviews and proactive performance optimization. Lead the architectural vision and shape the team’s technical strategy and roadmap, balancing immediate needs with long-term goals, driving innovation, and influencing the technical direction. Serve as a mentor and technical leader, guiding teams and fostering a culture of engineering and operational excellence by sharing your deep knowledge and experience. Engage with customers and stakeholders to understand use cases and feedback, translating them into actionable insights and effectively influencing at all levels. Apply your strong programming skills to integrate software and systems engineering, building core data platform capabilities and automation to meet enterprise customer needs and roadmap objectives. Develop strategic roadmaps, processes, plans, and infrastructure to efficiently deploy new software components at an enterprise scale while enforcing engineering standards." We'll put each asQualifications
and then within that we could haveMinimum Qualifications:
- ... etc. Or we could separate into Requirements and Qualifications. But we have both Minimum and Preferred; we could treat Minimum as Requirements and Preferred as Qualifications. However the instruction list includes both Requirements and Qualifications as possible headings. We could use Requirements for Minimum Qualifications and Qualifications for Preferred Qualifications. That seems reasonable.
Thus:
Requirements
Minimum Qualifications
- ... (list items)
Qualifications
Preferred Qualifications
- ... (list items)
Minimum Qualifications:
then list. Now Benefits: we have paragraph about benefits and PTO details. We'll put underBenefits
with...
maybe multiple paragraphs. Pay: we have salary range info and location-specific ranges. We'll put under