Job Requisition 2021591 Technical Leader - CX Engineering Productivity

We need to output HTML fragment with sections: About the role? The posting includes "Meet the Team" and "Your Impact". Also "Minimum Qualifications", "Preferred Qualifications". Also "Why Cisco?" maybe not needed? The instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

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

  for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to decide which sections to include. The posting includes: - Hybrid role location note: "***This is a hybrid role and we are looking for candidates local to RTP, NC or San Jose, CA only***". This is location info; could be part of a short paragraph. - "Meet the Team" description: paragraph about team. - "Your Impact": sections with bullet-like paragraphs (Strategic Leadership, Technical Excellence, Influence & Collaboration). Those are subheadings within the posting but not necessarily required to be separate sections; we could treat them as paragraphs or maybe as

  • for each bullet? The instructions: Use
    • for any list of duties/requirements/benefits. The "Your Impact" includes bullet points with headings like "Strategic Leadership", "Technical Excellence", "Influence & Collaboration". Those could be considered list items. We could output a
      with
      • each containing the heading and description. - Minimum Qualifications: list of items (10+ years..., BS or MS..., Proven track record...). Those are bullet list. - Preferred Qualifications: list of items. - "Why Cisco?" includes prose about company; could be optional but it's substantive. Could include as a section "About Cisco" or maybe "Why Cisco?" but the allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Why Cisco?" is not in that list but we could still use

        for any section heading? The instruction says use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive. Likely we should stick to those headings where applicable. We have qualifications (minimum and preferred) could be under "Qualifications". Responsibilities could be under "Your Impact". About the role could be "Meet the Team" maybe? Or we could have "About the role" covering the team description and hybrid note. Then "Responsibilities" for Your Impact. Then "Qualifications" for both minimum and preferred (maybe separate sub-sections? Could combine but we need to preserve all detail; we could have two

        under Qualifications: one for Minimum, one for Preferred, each preceded by a

        or ? But we cannot add extra headings not allowed? We could use

        to label "Minimum Qualifications:" and then

        . Similarly for Preferred. We also have location note; could be a short

        before sections. We should not include Pay/Benefits/Schedule unless explicitly stated. Pay is mentioned: salary range etc. That is pay info. The posting includes salary range and details. According to instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state salary range and benefits description. So we could include a Pay section. However the instruction says "Prefer a few substantive sections over many thin ones." Including Pay may be okay. But we need to see if we should include Pay section. The posting includes salary range and benefits details. That is substantive. So we should include a Pay section with that info. Similarly, Benefits: they talk about benefits (medical, dental, vision, 401k, etc). That's also substantive. So we could include Benefits section. Schedule: not mentioned (no schedule details). So we should not create Schedule. Thus sections: About the role (Meet the Team + location note), Responsibilities (Your Impact), Qualifications (Minimum & Preferred), Pay, Benefits. We must not repeat job title as heading. Good. We must not include boilerplate like EEO etc. The posting includes some boilerplate at end about Cisco sales plans etc. That's not relevant to the role? It's part of "Why Cisco?" maybe but includes details about sales incentive pay etc. That seems like generic boilerplate; but it's still part of the posting. However instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The sales incentive details might be considered boilerplate? Not exactly legal/EEO but it's generic compensation details for sales roles; but the role is not sales. It might be irrelevant. However it's part of the "Why Cisco?" section after the benefits. It seems like generic filler for all roles. Might be considered boilerplate. Safer to remove it? The instruction says remove boilerplate, duplicated lines, and application instructions. The sales incentive details are not application instructions. Might be considered boilerplate but not sure. I'd keep the "Why Cisco?" descriptive part up to the benefits, and cut off the sales incentive details as they are not relevant to the role and could be considered boilerplate. However we need to preserve ALL substantive information; if we cut that, we might be removing substantive info (though it's generic). I'd keep the benefits part and maybe stop before the sales incentive details. The benefits paragraph ends with "Please see the Cisco careers site to discover more benefits and perks." Then after that there is a paragraph about employees may be eligible to receive grants of Cisco restricted stock units... That's still benefits. Then after that there is a paragraph about paid time away details. That's also benefits. Then after that there is a paragraph about bonuses, then a long paragraph about sales plans. That seems like extra info not relevant to the role (non-sales). Could be considered boilerplate for all roles but still part of posting. I'd keep the benefits details up to the paid time away and bonuses? The bonus paragraph mentions "For non-sales roles, employees are also eligible to earn annual bonuses subject to Cisco’s policies." That's relevant. Then the sales plan paragraph is specific to sales roles; could be considered not relevant. I'd cut after the bonus paragraph. Thus Benefits section will include: medical, dental, vision insurance, 401(k) with match, paid parental leave, short/long-term disability, basic life insurance, restricted stock units, paid time away details (holidays, birthday, wellness days, sick time, volunteer days), annual bonuses for non-sales roles. Now we need to format. We'll output something like:

        About the role

        ... hybrid role note ... Meet the Team paragraph ...

        Responsibilities

        • Strategic Leadership: ...
        • Technical Excellence: ...
        • Influence & Collaboration: ...

        Qualifications

        Minimum Qualifications

        • 10+ years in engineering productivity, developer platforms, DevOps, build/release, or infrastructure engineering with demonstrated technical leadership progression
        • BS or MS in Engineering, STEM or related field
        • Proven track record designing and implementing developer platforms, tooling, or CI/CD and build systems that serve multiple teams

        Preferred Qualifications

        • Experience building internal developer platforms, platform-as-a-service offerings, or developer portals (e.g., Backstage)
        • Experience in productivity measurement and delivery practices, including DORA metrics, SLOs, quality gates, and CI/CD
        • Cross-organizational influence with the ability to build consensus and drive adoption of technical strategies and tooling
        • Expertise with CI/CD and GitOps platforms (Jenkins, GitHub Actions, GitLab CI, ArgoCD, Flux) and modern build systems (Bazel, monorepo tooling, remote/build caching)
        • Depth in test infrastructure — fast and reliable test suites, flaky-test management, and test observability
        • Proficiency with IaC tools (Terraform, CloudFormation) and cloud-native platforms (Kubernetes, AWS, Azure, GCP)
        • Proficiency in Python, Go, or Java with strong scripting and automation skills
        • Experience instrumenting the SDLC with observability tooling (Splunk, OpenTelemetry, Prometheus, Grafana) for build, test, and delivery health
        • Hands-on experience integrating AI-assisted and agentic development tools (code assistants, AI-driven review, test generation) into engineering workflows
        • Familiarity with DevEx research methods (developer surveys, SPACE framework) to quantify and improve developer experience
        • Strong communication skills with the ability to influence technical decisions across organizational levels

        Pay

        The starting salary range posted for this position is $214,100.00 to $309,800.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.

        But note we already have Benefits section