Senior Network Engineer

We need to output HTML fragment with sections: About the role? The posting includes a paragraph about mission, then Position Summary, then Key Responsibilities, Required Qualifications, Preferred Qualifications, Education Requirements, Pay Range, Benefits. Also mention travel, telework, etc. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we should only include sections when posting has real specific content. The posting includes: Position Summary (could be About the role). Key Responsibilities (Responsibilities). Required Qualifications (Requirements/Qualifications). Preferred Qualifications (maybe Skills). Education Requirements (maybe Qualifications). Pay Range (Pay). Benefits (Benefits). Travel/Telework maybe part of About the role or other. Schedule not mentioned, so we should not create Schedule section. Also we should not repeat job title as heading. No Job ID etc. We need to preserve all substantive information, not invent or summarize away detail. Use

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

  for prose. We need to decide which headings to use: About the role (position summary). Responsibilities (key responsibilities). Requirements (maybe required qualifications). Qualifications (maybe preferred qualifications? Or we could combine required and preferred under Requirements and Qualifications? The instruction: Use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have: - About the role: mission statement and position summary paragraph. - Responsibilities: list of key responsibilities (multiple bullet points). Use

  • . - Requirements: required qualifications (list). Use
    • . - Qualifications: maybe preferred qualifications? Could also be "Preferred Qualifications". Use heading Qualifications? Might be ambiguous. But we have both Required and Preferred. Could put Required under Requirements, Preferred under Qualifications. Or we could put both under Requirements and Qualifications respectively. We'll do that. - Skills: maybe we could include specific skills like Cisco certifications, automation frameworks, etc. But those are in Preferred Qualifications. Could treat them as Skills. However we already have Qualifications heading for preferred qualifications. Might be better to put Preferred Qualifications under Skills. But the instruction says we can use Skills heading. Let's decide: Use Requirements for required qualifications, Qualifications for preferred qualifications, and maybe Skills for specific technical skills (Cisco certifications, automation frameworks, etc.) but that would duplicate. Better to follow the posting: Required Qualifications -> Requirements heading. Preferred Qualifications -> Qualifications heading. Education Requirements could be part of Requirements or Qualifications? Could be separate but we don't have a heading for Education. Could fold into Requirements or Qualifications. Since we have limited headings, we can include Education under Requirements (as part of required qualifications) or Qualifications. Probably better to include Education under Requirements as it's a requirement. But the posting lists Education Requirements separately; we can include it as a bullet under Requirements. - Benefits: list of benefits (medical, dental, vision, PTO, retirement, wellness). Use
      • . - Pay: Pay Range paragraph. - Schedule: not present, so omit. Also include travel/telework info: maybe under About the role as a note. We must not include boilerplate like EEO, application instructions, etc. Remove lines about Qualified applicants with arrest..., benefits details about application window closing date, etc. Those are boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The line about Qualified applicants with arrest or conviction records is EEO/legal; remove. The line about application window closing date is application instruction? It's a date; maybe considered application instruction; remove. The line about benefits details being provided during application process is also application instruction; we can keep generic benefits but remove that sentence. Keep benefits list. We need to preserve all substantive information: mission paragraph, position summary, responsibilities list, required qualifications list, preferred qualifications list, education requirements, pay range, benefits list, travel/telework note. Let's extract text. Mission paragraph: "We’re building a world of health around every individual — shaping a more connected, convenient and compassionate health experience. At CVS Health®, you’ll be surrounded by passionate colleagues who care deeply, innovate with purpose, hold ourselves accountable and prioritize safety and quality in everything we do. Join us and be part of something bigger – helping to simplify health care one person, one family and one community at a time." Position Summary: "CVS Health is seeking a highly skilled and visionary Sr. Manager to lead and manage our enterprise Cisco Application Centric Infrastructure (ACI) environment and the transition to Cisco Nexus Dashboard Fabric Controller (NDFC). This role sits within the Network Engineering team and is pivotal to driving the modernization and scalability of our next-generation data center fabric. This role will help set and drive the network technology strategy for ISTS, ensuring that ISTS delivers on our mission to transform technology and provide an agile, cost optimized and resilient set of network infrastructure services to meet the evolving needs of all the CVS Health lines of business. The ideal candidate will have experience supporting complex enterprise network environments and demonstrate deep expertise in Cisco ACI and NDFC technologies. As a strategic leader, you will be responsible for setting the direction, leading a team of engineers, and ensuring the operational integrity, performance, and evolution of our fabric-based data center architecture. This position will also mentor staff members in an effort to develop excellent enterprise networking skills." Key Responsibilities bullet list: - Lead the deployment, administration, and lifecycle management of the Cisco ACI environment - Oversee the strategic transition to and ongoing management of the Cisco Nexus Dashboard Fabric Controller (NDFC) - Manage a team of network engineers, providing technical guidance, mentorship, and performance management - Develop and articulate a clear vision and roadmap for ACI/NDFC within CVS Health’s broader data center and cloud networking strategy - Collaborate cross-functionally with infrastructure, cloud, security, and application teams to ensure alignment of fabric design with enterprise needs - Establish and maintain operational standards, monitoring strategies, and documentation to support uptime, scalability, and compliance - Serve as a technical SME for ACI/NDFC, engaging in architecture reviews, incident escalations, and vendor management - Define and track key metrics to demonstrate network health, stability, and performance within the fabric environment - Ensure adherence to change management, audit, and security policies across all fabric-related activities - Maintain strong communication with leadership and stakeholders to report progress, risks, and investment needs Required Qualifications bullet list: - 5+ years of experience in a large-scale enterprise network engineering environment - Demonstrated expertise in Cisco ACI (multi-site, multi-pod, L3Out, contracts, etc.) and Cisco NDFC, including architecture, operations, and automation - Strong leadership experience, including being a team lead and leading through influence - Proven ability to develop and communicate a strategic vision and execute on large-scale infrastructure initiatives - In-depth understanding of data center network design, segmentation, routing, and policy-based networking - Experience working in highly regulated environments with a focus on security, compliance, and operational excellence - Fine with 10-15% Travel - Potential Telework Position Preferred Qualifications bullet list: - Cisco certifications (e.g., CCNP, CCIE – Data Center) - Experience with automation frameworks and APIs for ACI/NDFC - Familiarity with hybrid cloud connectivity and fabric integration with cloud platforms (AWS, Azure, GCP) - Experience with network telemetry, monitoring, and performance analytics tools Education Requirements: - Bachelor’s degree or equivalent experience (Highschool diploma plus 4 years relevant work experience) Pay Range: - "The Typical Pay Range For This Role Is $130,295.00 - $260,590.00 This pay range represents the base hourly rate or base annual full-time salary for all positions in the job grade within which this position falls. The actual base salary offer will depend on a variety of factors including experience, education, geography and other relevant factors. This position is eligible for a CVS Health bonus, commission or short-term incentive program in addition to the base pay range listed above. This position also includes an award target in the company’s equity award program." Benefits: - "Great Benefits For Great People We take pride in offering a comprehensive and competitive mix of pay and benefits that reflects our commitment to our colleagues and their families. This full‑time position is eligible for a comprehensive benefits package designed to support the physical, emotional, and financial well‑being of colleagues and their families. The benefits for this position include medical, dental, and vision coverage, paid time off, retirement savings options, wellness programs, and other resources, based on eligibility." We should keep the benefits list as bullet items: medical, dental, vision coverage, paid time off, retirement savings options, wellness programs, and other resources. We need to remove fluff like "Great Benefits For Great People We take pride in offering a comprehensive and competitive mix of pay and benefits that reflects our commitment to our colleagues and their families." That's somewhat boilerplate but still part of benefits description. Might keep but it's not a list. The instruction: Use
        • for any list of duties/requirements/benefits, and

          for prose. So we can have a

          for the benefits intro sentence, then a

          • for the list. Similarly for About the role: we have two paragraphs (mission and position summary). Could combine into one

            or separate

            s. We'll put them in

            maybe two

            elements. For Responsibilities:

            Responsibilities

            then
            • each. For Requirements:

              Requirements

              then
              • each required qualification. For Qualifications:

                Qualifications

                then
                • each preferred qualification. For Education: maybe we could include under Requirements as a bullet, but we have separate heading Education Requirements not in list. Could we add a heading Education? Not in allowed headings list. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to fit Education into one of those. Probably Requirements (since it's a requirement). We'll add education bullet under Requirements. For Skills: we could put specific technical skills under Skills heading, but we already have Qualifications for preferred qualifications. Could treat Qualifications as Skills? But we have both headings; we need to decide. The posting includes "Preferred Qualifications" which includes certifications, automation experience, hybrid cloud, telemetry. Those could be considered Skills. So we could put them under Skills heading. Then we could have Qualifications heading for something else? But we don't have other qualifications. Maybe we can combine Required Qualifications under Requirements, and Preferred Qualifications under Skills. That seems reasonable: Requirements = mandatory; Skills = preferred/desired skills. Then we don't need Qualifications heading. However the instruction list includes Qualifications as a possible heading; we can omit if not needed. We'll use Requirements and Skills. Thus sections: - About the role (mission + position summary) - Responsibilities - Requirements (required qualifications + education) - Skills (preferred qualifications) - Benefits - Pay Check if any content left: travel/telework note included in Requirements bullet. Now ensure we don't include any boilerplate: remove EEO line, remove application window closing date line, remove "Additional details about available benefits are provided during the application process and on Benefits Moments." Also remove "Our people fuel our future..." paragraph (that's boilerplate about diversity). Also remove "We anticipate the application window for this opening will close on: 10/01/2026". Also remove "Qualified applicants with arrest or conviction records will be considered for employment...". Also remove "Our people fuel our future..." paragraph. Also remove "Great Benefits For Great People We take pride in offering a comprehensive and competitive mix of pay and benefits that reflects our commitment to our colleagues