Engineering Manager- Cloud Operations- Fedramp
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
2. Use - for any list of duties/requirements/benefits, and
for prose
3. Do NOT repeat the job title as a heading (the page already shows it)
4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it
5. Preserve ALL substantive information; do NOT invent or summarize away detail
6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions
7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text
8. Never create Pay/Schedule/Benefits sections unless the posting actually states them
9. Prefer a few substantive sections over many thin ones
10. Output ONLY the HTML fragment — no /, no markdown code fences
Let me analyze the job posting content:
- Application window close date: 12/30/2026 (metadata)
- U.S. citizen requirement (metadata)
- "Meet the Team" section - describes the team
- "Your Impact" section - describes the role responsibilities
- "Minimum Qualifications" section - lists requirements
- "Preferred Qualifications" section - lists preferred qualifications
- "Why Cisco?" section - company description and benefits/pay information
I need to structure this into appropriate sections. The posting has:
- Team description (could be "About the team" or similar)
- Role impact/responsibilities (could be "Responsibilities" or "About the role")
- Minimum Qualifications (Requirements)
- Preferred Qualifications (Preferred Qualifications)
- Benefits and Pay information (Benefits, Pay)
The posting includes detailed salary ranges and benefits. So I should include Pay and Benefits sections.
I should not include the application window close date as a heading, but maybe as a brief note. The U.S. citizen requirement is also metadata.
Let me create the HTML structure:
About the team
...team description...
Responsibilities
- ...responsibilities from "Your Impact"...
Requirements
- ...minimum qualifications...
Preferred qualifications
- ...preferred qualifications...
Pay
...salary ranges...
Benefits
- ...benefits listed...
I need to parse the content carefully and preserve all substantive details.
Let me extract the content:
Meet the Team: "The Webex Contact Center FedRAMP team builds and operates secure, reliable cloud services for U.S. government customers. We partner closely with application engineering, security, compliance, and infrastructure teams to support the Webex for Government environment and deliver services that meet strict availability and control requirements. The team is made up of cloud operations, platform, and security-minded engineers who thrive in a highly regulated, high-visibility environment. What’s exciting about this team is the opportunity to improve reliability and automation at scale while helping power mission-critical services for government users."
Your Impact: "As a Manager of Cloud Operations Engineering, you will lead a team of Cloud Engineers, DevOps, Infrastructure Operations Engineers and Systems Administrators, helping them grow while building a culture focused on reliability and continuous improvement. You'll support your team through day-to-day challenges, mentor them in infrastructure technologies and best practices, and help them develop their careers. You'll oversee the operations and maintenance of cloud-based, hybrid, and data centre infrastructure, working with your team to troubleshoot issues, optimize performance, and keep systems running smoothly. You'll collaborate across the organization with platform, security, and application teams to solve complex infrastructure problems and align on priorities. On the engineering side, you'll champion automation and infrastructure-as-code practices to reduce manual operational work, help streamline deployment and operational workflows, and support your team in adopting modern DevOps and cloud operations best practices. You'll also help establish clear communication during incidents and work with stakeholders to keep everyone informed on system status and technical updates."
Minimum Qualifications:
- Bachelor's degree in Computer Science, Information Technology, Engineering, or related field plus 8 years of relevant experience in cloud operations or DevOps engineering, with 3+ years in a team lead or supervisory role, OR Master's degree plus 6 years of experience with 2+ year in a leadership capacity
- 2+ years of experience leading/supervising technical teams (e.g., cloud operations, DevOps, SRE, infrastructure operations) including mentoring and performance management.
- Experience operating production cloud/hybrid environments and leading incident response, root-cause analysis, and corrective actions in a 24x7 setting.
- Experience with automation and infrastructure-as-code for infrastructure deployments and operational workflows (e.g., Terraform or comparable tooling).
- Experience working with security/compliance to support FedRAMP and/or NIST 800-53 and/or SOC 2-aligned environments.
Preferred Qualifications:
- Experience directly leading multidisciplinary cloud teams (e.g., cloud infrastructure, DevOps, platform, or SRE specialists), including mentoring and performance management.
- Experience operating AWS infrastructure including Kubernetes, CI/CD pipelines, and infrastructure-as-code solutions.
- Hands-on automation tooling experience with Terraform, Jenkins, Git, Python, shell scripting, or comparable technologies.
- Knowledge of FedRAMP continuous monitoring and related security/compliance practices, including vulnerability remediation, audit evidence, incident reporting, and maintaining an authorized system boundary.
- Experience owning operational readiness and high-severity processes, including on-call rotation management (e.g., PagerDuty), and defining runbooks/monitoring/support models/onboarding standards.
Why Cisco? includes company description and then pay and benefits.
Pay: "The starting salary range posted for this position is $166,300.00 to $238,300.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 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. 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%; and Once 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 $186,900.00 - $307,800.00 Non-Metro New York State & Washington State $166,300.00 - $274,100.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."
I need to separate Pay and Benefits. The pay section includes salary ranges and incentive details. Benefits include insurance, 401k, parental leave, disability, life insurance, RSUs, paid time off (holidays, vacation, sick, volunteer), bonuses.
I'll create a Pay section with the salary ranges and incentive info, and a Benefits section with the benefits list.
Also note the application window close date and U.S. citizen requirement. These are minor metadata. I can include them in a brief paragraph at the top or bottom, but not as a heading. The instruction says "fold minor metadata into a short or drop it." I'll include a short paragraph at the beginning.
Now, I'll write the HTML fragment.
I'll use
for each section. Use - for lists. Use
for prose.
Let's structure:
Application window closes 12/30/2026. This position requires U.S. citizenship and work on U.S. soil.
About the team
...
Responsibilities
- Lead a team of Cloud Engineers, DevOps, Infrastructure Operations Engineers and Systems Administrators, fostering growth and a culture of reliability and continuous improvement.
- Support team through day-to-day challenges, mentor in infrastructure technologies and best practices, and guide career development.
- Oversee operations and maintenance of cloud-based, hybrid, and data centre infrastructure; troubleshoot issues, optimize performance, and ensure system stability.
- Collaborate with platform, security, and application teams to solve complex infrastructure problems and align priorities.
- Champion automation and infrastructure-as-code practices to reduce manual operational work, streamline deployment and operational workflows, and adopt modern DevOps and cloud operations best practices.
- Establish clear communication during incidents and keep stakeholders informed on system status and technical updates.
Requirements
- Bachelor's degree in Computer Science, Information Technology, Engineering, or related field plus 8 years of relevant experience in cloud operations or DevOps engineering, with 3+ years in a team lead or supervisory role, OR Master's degree
for prose 3. Do NOT repeat the job title as a heading (the page already shows it) 4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it 5. Preserve ALL substantive information; do NOT invent or summarize away detail 6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions 7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text 8. Never create Pay/Schedule/Benefits sections unless the posting actually states them 9. Prefer a few substantive sections over many thin ones 10. Output ONLY the HTML fragment — no /, no markdown code fences Let me analyze the job posting content: - Application window close date: 12/30/2026 (metadata) - U.S. citizen requirement (metadata) - "Meet the Team" section - describes the team - "Your Impact" section - describes the role responsibilities - "Minimum Qualifications" section - lists requirements - "Preferred Qualifications" section - lists preferred qualifications - "Why Cisco?" section - company description and benefits/pay information I need to structure this into appropriate sections. The posting has: - Team description (could be "About the team" or similar) - Role impact/responsibilities (could be "Responsibilities" or "About the role") - Minimum Qualifications (Requirements) - Preferred Qualifications (Preferred Qualifications) - Benefits and Pay information (Benefits, Pay) The posting includes detailed salary ranges and benefits. So I should include Pay and Benefits sections. I should not include the application window close date as a heading, but maybe as a brief note. The U.S. citizen requirement is also metadata. Let me create the HTML structure:
About the team
...team description...
Responsibilities
- ...responsibilities from "Your Impact"...
Requirements
- ...minimum qualifications...
Preferred qualifications
- ...preferred qualifications...
Pay
...salary ranges...
Benefits
- ...benefits listed...
or drop it." I'll include a short paragraph at the beginning. Now, I'll write the HTML fragment. I'll use
for each section. Use - for lists. Use
for prose.
Let's structure:
Application window closes 12/30/2026. This position requires U.S. citizenship and work on U.S. soil.
About the team
...
Responsibilities
- Lead a team of Cloud Engineers, DevOps, Infrastructure Operations Engineers and Systems Administrators, fostering growth and a culture of reliability and continuous improvement.
- Support team through day-to-day challenges, mentor in infrastructure technologies and best practices, and guide career development.
- Oversee operations and maintenance of cloud-based, hybrid, and data centre infrastructure; troubleshoot issues, optimize performance, and ensure system stability.
- Collaborate with platform, security, and application teams to solve complex infrastructure problems and align priorities.
- Champion automation and infrastructure-as-code practices to reduce manual operational work, streamline deployment and operational workflows, and adopt modern DevOps and cloud operations best practices.
- Establish clear communication during incidents and keep stakeholders informed on system status and technical updates.
Requirements
- Bachelor's degree in Computer Science, Information Technology, Engineering, or related field plus 8 years of relevant experience in cloud operations or DevOps engineering, with 3+ years in a team lead or supervisory role, OR Master's degree
for prose. Let's structure:
Application window closes 12/30/2026. This position requires U.S. citizenship and work on U.S. soil.
About the team
...
Responsibilities
- Lead a team of Cloud Engineers, DevOps, Infrastructure Operations Engineers and Systems Administrators, fostering growth and a culture of reliability and continuous improvement.
- Support team through day-to-day challenges, mentor in infrastructure technologies and best practices, and guide career development.
- Oversee operations and maintenance of cloud-based, hybrid, and data centre infrastructure; troubleshoot issues, optimize performance, and ensure system stability.
- Collaborate with platform, security, and application teams to solve complex infrastructure problems and align priorities.
- Champion automation and infrastructure-as-code practices to reduce manual operational work, streamline deployment and operational workflows, and adopt modern DevOps and cloud operations best practices.
- Establish clear communication during incidents and keep stakeholders informed on system status and technical updates.
Requirements
- Bachelor's degree in Computer Science, Information Technology, Engineering, or related field plus 8 years of relevant experience in cloud operations or DevOps engineering, with 3+ years in a team lead or supervisory role, OR Master's degree