Senior Hardware Engineering Program Manager

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the posting. Content: - Application window close date: 10/16/2026 (metadata, maybe include in a short p) - Onsite position at San Jose, CA location (metadata) - "Meet the team" paragraph: description of team and role. - "Your Impact" bullet list (actually sentences separated by periods). We need to extract duties/responsibilities. - Minimum Qualifications (list) - Preferred Qualifications (list) - Why Cisco? (company description) - Message to applicants applying to work in the U.S. and/or Canada: salary range, benefits description, etc. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. There's no explicit application instructions besides maybe the salary info; but we keep substantive info. We need to decide sections: - About the role: could be the "Meet the team" paragraph describing role and team. Or maybe combine with "Your Impact". Usually About the role is a summary. We'll put that as About the role. - Responsibilities: the "Your Impact" sentences (list of duties). We'll make

• each. - Requirements: Minimum Qualifications (maybe as Requirements). Could also separate Requirements and Qualifications. The instruction says use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. We have Minimum Qualifications and Preferred Qualifications. Could treat Minimum as Requirements, Preferred as Qualifications. Or combine both under Qualifications. But we need to follow instruction: Use headings for those sections if content exists. We'll create:

  About the role

  ... (Meet the team paragraph)

  Responsibilities

  • ... each duty

  Requirements

  • ... Minimum Qualifications items

  Qualifications

  • ... Preferred Qualifications items
  maybe also include Skills? There's no explicit skills list besides maybe "Experience using AI tools", "Expertise in DVT", etc. Those are in Preferred Qualifications. Could also create Skills section for technical skills like Jira, Confluence, MS Project, AI tools, DVT, supply chain, etc. But we already have them in Preferred Qualifications. To avoid duplication, maybe we put those under Qualifications. The instruction says prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one? But they ask to use headings for those sections if content exists. We could have Requirements (minimum) and Qualifications (preferred). That's two sections. Skills: maybe we could extract specific skills: "Experience in project management tools (e.g., Jira, Confluence, MS Project)", "Experience using AI tools", "Expertise in Design Verification Testing (DVT) processes", "Extensive knowledge of hardware manufacturing environments, production workflows, and supply chain operations", "Strategic background in supply chain operations or procurement", "Proven ability to communicate difficult concepts and influence outcomes", "Demonstrated expertise with leading multi-functional dependencies", "Familiarity with demonstrating advanced analytical tools and AI-enabled methodologies". Those are already in qualifications. Could still make a Skills section but would duplicate. Better to not create Skills if content already covered elsewhere; but instruction says include a section ONLY when posting has real, specific content for it. If we put those items under Qualifications, we still have content for Skills but we would be duplicating. To avoid duplication, we could not create Skills section and just rely on Qualifications. That's acceptable. Benefits: The posting includes benefits description under "Message to applicants...": medical, dental, vision insurance, 401(k) with match, paid parental leave, short/long-term disability, basic life insurance, paid holidays, floating holiday, birthday day off, year-end shutdown, personal wellness days, vacation time (different for exempt/non-exempt), sick time, volunteer days, bonuses, etc. That's substantive. So we need a Benefits section. Pay: The posting includes salary range: starting salary range $171,600 to $245,000, plus location-specific ranges (NYC Metro Area, Non-Metro NY & WA). Also mention that full salary ranges for certain states listed. So we have pay info. So we need a Pay section. Schedule: The posting mentions "This is an onsite position at the San Jose, CA location." No explicit schedule (full-time, hours). Not given. So we should not create Schedule section because no specific content. We also have application window close date and location; we can put that in a short p under About the role or maybe a separate metadata paragraph. But instruction: do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short

  or drop it. So we can include a short p with that info, maybe under About the role or at top. We must remove boilerplate: The "Why Cisco?" paragraph is somewhat generic but still substantive about company; we could keep as About the role or maybe as a separate section? But we already have About the role for role description. Could incorporate Why Cisco? into About the role or maybe as a separate section "About Cisco". But headings list does not include About Cisco; only About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not create a heading for Why Cisco?. We could incorporate that content into About the role paragraph (maybe as additional sentences). However, the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the Why Cisco? text somewhere. If we don't have a heading for it, we can put it in a

  under About the role or maybe as a separate

  without heading? The instruction says output ONLY the HTML fragment; we can have multiple

  elements not under headings? It didn't forbid that. It said use

  for section headings (e.g. About the role, Responsibilities, etc). Use

  • for any list, and

    for prose. So we can have prose paragraphs outside headings. But we should prefer a few substantive sections over many thin ones. So we could have About the role heading with paragraph containing both Meet the team and Why Cisco? combined. That would preserve all info. Similarly, the Message to applicants about salary and benefits we will split into Pay and Benefits sections. We need to ensure we don't include filler like "commensurate with experience". Not present. Now craft HTML. First, maybe a short p for metadata: "Application window expected to close on 10/16/2026. This is an onsite position at the San Jose, CA location." Then

    About the role

    ... combine Meet the team and Why Cisco? paragraphs.

    Then

    Responsibilities

    • ... each duty from Your Impact.
    Then

    Requirements

    • ... Minimum Qualifications items.
    Then

    Qualifications

    • ... Preferred Qualifications items.
    Then

    Benefits

    • ... benefits list.
    Then

    Pay

    ... salary ranges.

    We must not include Schedule. Now extract details. Metadata p: "Application window expected to close on 10/16/2026. This is an onsite position at the San Jose, CA location." About the role paragraph: Combine: "Meet the team Our Systems and Optics Hardware PMO team serves as the engine for Cisco’s hardware portfolio, redefining complex strategies into predictable, high-quality delivery through multi-functional governance and operational excellence. As a Hardware Engineering Program Manager, you will act as the primary orchestrator for next-generation platforms, driving the end-to-end product lifecycle while ensuring financial rigor and seamless alignment across our engineering and business partners." Plus Why Cisco? paragraph: "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 need to ensure we don't repeat "Meet the team" as heading; it's fine as part of paragraph. Now Responsibilities: Extract each sentence from "Your Impact". The text: "Your Impact Lead program management of large-scale, high-risk hardware products for Cisco with multiple interdependencies across functions, ensuring successful end-to-end delivery from concept to customer release.Orchestrate multi-functional activities by aligning hardware and software engineering, product management, service, customer documentation and operations teams to ensure cohesive, high-quality execution.Drive complex problem-solving by interpreting current business trends to identify and implement innovative, strategic solutions for program delivery.Monitor program health, lead critical path roadmaps, risk mitigation and necessary course corrections.Lead all aspects of budget preparations, resource allocation, and financial rigor to ensure effective utilization and alignment to business plansInfluence and persuade partners at all levels, providing executive-level status updates and strategic recommendations for maintaining relationships.Provide technical expertise and mentorship to engineering project management staff, fostering process improvements and the implementation of continuous integration methodologies." We need to split into separate duties. Each sentence seems separated by a period but there is no space after some periods. We'll split logically: 1. Lead program management of large-scale, high-risk hardware products for Cisco with multiple interdependencies across functions, ensuring successful end-to-end delivery from concept to customer release. 2. Orchestrate multi-functional activities by aligning hardware and software engineering, product management, service, customer documentation and operations teams to ensure cohesive, high-quality execution. 3. Drive complex problem-solving by interpreting current business trends to identify and implement innovative, strategic solutions for program delivery. 4. Monitor program health, lead critical path roadmaps, risk mitigation and necessary course corrections. 5. Lead all aspects of budget preparations, resource allocation, and financial rigor to ensure effective utilization and alignment to business plans. 6. Influence and persuade partners at all levels, providing executive-level status updates and strategic recommendations for maintaining relationships. 7. Provide technical expertise and mentorship to engineering project management staff, fostering process improvements and the implementation of continuous integration methodologies. We'll put each as
  • . Now Requirements (Minimum Qualifications): Text: "Minimum Qualifications Bachelor’s degree in engineering with 8+ years of experience or a master’s degree in engineering with 6+ years of experience in technical program management, or PhD with 3+ years of experience.Demonstrated experience leading end-to-end, complex hardware programs consisting of multiple PCBAs with moderate to high risk and multi-functional interdependencies.Experience in defining and delivering program plans, schedules, and budgets, including monitoring critical path activities and resource allocation.Experience in project management tools (e.g., Jira, Confluence, MS Project) to track program metrics." We need to split into items: - Bachelor’s degree in engineering with 8+ years of experience or a master’s degree in engineering with 6+ years of experience in technical program management, or PhD with 3+ years of experience. - Demonstrated experience leading end-to-end, complex hardware programs consisting