Jobs · Project Management · Georgia

Senior Engineering Program Manager

Cisco · Atlanta, GA · 3 wk ago
Project Management$169k–$237k/yrFull-time
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 must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: application window lines, duplicate lines, cookie/navigation/legal/EEO etc. Also remove duplicated lines like "The application window is expected to close on: 11/29/2026" appears twice; we drop those lines. Also drop "Job posting may be removed earlier..." etc. Also drop "Preferred location for this role : Remote everywhere within USA." That's location info; maybe we can keep as a short paragraph? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So location can be a short

. Also we need to include sections only when posting has real specific content. We have content: "Meet the Team" paragraph describing team vision. That could be "About the role" or maybe "About the team". We'll use

About the role

and put that paragraph. Then "Your Impact" paragraph describing role impact. Could be part of responsibilities? Might be separate "Responsibilities". We'll treat as responsibilities. Then "What You'll Do" list of duties. That's a list; we need
  • . Then "Minimum Qualifications" list of qualifications (bulleted). That's qualifications. Then "Preferred Qualifications" list. Then "Why Cisco?" paragraph about company; could be "About the company" but not required; maybe we can include as a section "About Cisco" but not in prescribed headings. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely we should stick to those headings only. So we need to map content to those headings. We have: - About the role: could include "Meet the Team" and maybe "Why Cisco?"? But "Why Cisco?" is more about company; maybe we can put under About the role as well. - Responsibilities: "Your Impact" and "What You'll Do". - Requirements: maybe combine Minimum Qualifications and Preferred Qualifications? But we have separate headings Qualifications and Skills. Could put Minimum Qualifications under Qualifications, Preferred under Skills? Or we could have Qualifications (minimum) and Skills (preferred). The instruction: "Prefer a few substantive sections over many thin ones." So we could combine qualifications and skills into one Qualifications section. But we have both minimum and preferred; we could keep them as subpoints. We also have Pay and Benefits sections: The posting includes salary range and benefits description. So we should include Pay and Benefits sections. Schedule: Not mentioned; we should not include Schedule if not present. Thus sections: About the role, Responsibilities, Qualifications, Pay, Benefits. We need to preserve all substantive info; not invent or summarize away detail. So we need to include the specific salary ranges, benefits details, etc. We must not include boilerplate like "Message to applicants applying to work in the U.S. and/or Canada:"? That's part of pay details; we need to keep the salary range info. The paragraph about salary range is substantive; we should keep it. Also the full salary ranges for specific states; we should keep that. Also the benefits description: medical, dental, vision, 401(k), paid parental leave, etc. Also the paid time away details. Also the stock units info. Also the bonus info. All that is substantive; we must keep. We must not include duplicated lines, cookie/navigation/legal/EEO etc. The "Message to applicants..." is part of pay; we keep. We need to output only HTML fragment, no /, no markdown fences. Let's craft:

    About the role

    Meet the Team Every line of code Cisco ships carries a promise of trust. Our Security Engineering team builds the foundations that enable us to keep that promise, embedding protection across the development lifecycle so security moves at the speed of engineering. The AI era is revolutionizing how we build and protect software, creating a unique opportunity to modernize security at its core. This is your chance to be a leader in this transformation. This role lives at the heart of our Program Management Office, the team that turns security strategy into predictable, measurable delivery of services that teams across Cisco depend on. Our vision is simple: deliver the greatest security value with the lowest possible friction for Cisco's developers, winning their trust by making security the easy path. Success means protection feels effortless, costs stay low, and the services we build become ones that engineers genuinely love to use. Above all, you'll join a team that's passionate about revolutionizing security — curious, collaborative people who love the mission and enjoy tackling the hard, meaningful problems that come with it.

    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.

    But we might be duplicating "Why Cisco?" content; maybe better to keep it under About the role as a separate paragraph. Now Responsibilities:

    Responsibilities

    Your Impact As a Senior Engineering Program Manager, you'll lead some of Cisco's most consequential security programs. These are cross-functional, multi-year efforts that secure the software the company runs on, shape where the business is headed, and earn the attention of its most senior leaders. You'll own the outcomes end to end and the story we tell about them. In this role, you'll face some of the hardest challenges in the industry today, and when you solve them, security lands across the board — developers across Cisco adopt the services you ship, the commitments leadership is counting on are met predictably, and Cisco's software grows measurably safer over time. If you like to operate in deeply technical spaces, driving measurable outcomes, few roles will stretch you further, or make as material a difference in an organization.

    • Turn service vision into strategy and execution in partnership with Security Engineering Service Owners and Engineering Managers:Set the roadmap and objectives and key results, then drive delivery, holding teams accountable for KPIs to prove it's working.
    • Clear the path as you go. Spot issues early, untangle dependencies, and unblock teams before they stall.
    • Think like a product leader. Treat every service as a product and its developers as customers you must win:Optimize the security value each service delivers and make it the best it can be.Win hearts and minds by hunting down developer friction and redesigning in partnership with key stakeholders, so the secure path is the one they would choose anyway.
    • Be the signal in the noise for leadership. Turn progress, risk, and tradeoffs into the clear picture leaders need to make the right decisions.
    • Steer a portfolio of concurrent service programs. Make the tough prioritization calls when programs compete for the same people, time, and attention.
    • Raise the bar for the whole team. Sharpen the program management practices, standards, and tooling everyone relies on.
    Note: The list items have some run-on sentences without spaces after colons; we should keep as is but maybe add a space after colon for readability? The instruction: preserve ALL substantive information; do not invent or summarize away detail. Changing punctuation could be considered altering detail? It's minor but maybe we should keep exactly as given. However the original text had missing spaces after colons: "Set the roadmap and objectives and key results, then drive delivery, holding teams accountable for KPIs to prove it's working." Actually after colon there is no space? In the text: "Set the roadmap and objectives and key results, then drive delivery, holding teams accountable for KPIs to prove it's working." There's a colon after "Managers:" then "Set". There's no space after colon in original? It shows ":Set". We should keep exactly as given? Probably okay to keep as is; but we could add a space; but that would be altering. Safer to keep exactly as given. Now Qualifications: We have Minimum Qualifications and Preferred Qualifications. We'll combine under Qualifications.

    Qualifications

    Minimum Qualifications Bachelor's + 9 years of related experience; or Master's + 7 years; or PhD + 4 years — or equivalent combination of education, skills, and experience.Demonstrated experience leading large-scale, complex, high-visibility programs to measurable outcomes.Exceptional learning agility: a track record of ramping quickly in unfamiliar, technical domains, digging beneath the surface to find the real problem, and driving resolution.Skilled at influencing without direct authority: a trusted team player who builds alignment across teams and partners and rallies others toward a shared goal.Highly self-directed: operates autonomously under ambiguity and broad scope, delivering with minimal direction.Excellent written and verbal communication skills, with substantial experience at the executive level, to turn complexity into clear, decision-ready narratives.

    Preferred Qualifications Fluency in how modern software is built and secured across the software development lifecycle (SDLC) — enough to partner credibly with engineers. A background in software engineering or DevOps is ideal, and hands-on security experience is a strong plus.An understanding of how AI is reshaping software development and security.Product management experience, or program management working hand in hand with product teams, with a track record of turning customer needs into shipped outcomesA program management certification (e.g., PMP, PGMP) is a plus.

    We need to preserve line breaks? The original had line breaks; we can keep as paragraphs. Now Pay:

    Pay

    Message to applicants applying to work in the U.S. and/or Canada: The starting salary range posted for this position is $169,300.00 to $237,200.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

Similar jobs