Mgr - Global Network Operations

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes "About us" but not "About the role". There's a "Position Overview" which could be considered About the role. The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. So we can have About the role (maybe using Position Overview). Responsibilities: there is a list of key responsibilities. Requirements: maybe qualifications & experience. Qualifications: maybe separate? The posting lumps Qualifications & Experience. We could treat that as Requirements. Skills: maybe list of technical skills. Benefits: there is mention of benefits package earlier: medical, dental, vision insurance, paid time off, retirement savings, professional development, work-life balance, perks. Also mention US benefits website. So we can include Benefits section. Pay: salary range given: $112,600.00 - $169,000.00. So include Pay. Schedule: not mentioned, so omit. We must not include boilerplate like EEO, accommodation request, etc. Also remove duplicated lines. Also remove navigation etc. We need to preserve all substantive information. So we need to include the About us content? The About us is not a section heading but could be part of About the role? Actually About us is company overview; maybe we can include it under About the role? The instruction: "About the role" heading for section headings. The About us is not about the role but about company. Could we still include it under About the role? Might be okay as it's substantive. But we need to avoid filler. The About us paragraph is substantive. We'll include it under About the role. We need to use

• for any list of duties/requirements/benefits. So responsibilities list should be ul. Requirements list maybe ul. Skills list maybe ul. Benefits list maybe ul. We need to use

  for prose. We must not include headings with filler. So we will include sections: About the role, Responsibilities, Requirements (or Qualifications?), Skills, Benefits, Pay. Possibly also Qualifications separate? The posting has "Qualifications & Experience". Could treat that as Requirements. Skills could be extracted from the qualifications list (technical proficiencies). But we might combine. Better: Have sections: About the role (position overview + about us), Responsibilities, Requirements (education/experience), Skills (technical proficiencies), Benefits, Pay. We must not repeat job title as heading. Not include Job ID. Let's extract content. About us paragraph: "At Plexus, our vision is to help create the products that build a better world. Driven by a passion for excellence, we partner with leading Aerospace/Defense, Healthcare/Life Sciences and Industrial companies to design, manufacture and service some of the world’s most transformative products, including advanced surgical systems, diagnostic instruments, healthcare imaging equipment, mission critical aerospace systems, and electric vehicle (EV) charging solutions. Visit Plexus.com to learn more about our unwavering commitment to our vision. When we invest in our people, we invest in building a better world. With a vision rooted in the wellbeing and inclusive engagement of our team members, our customers, their end users and our communities, people are the heart of what we do and who we are. It is our values that unite us and guide us in everything that we do, including how we operate, behave and interact to foster a workplace where every team member feels valued and empowered to contribute their best. Our values include: Growing our People, Building Belonging, Innovating Responsibly, Delivering Excellence and Creating Customer Success. As a team member, you will engage in impactful work through global collaboration and the use of emerging technologies, join an inclusive culture where every team member is valued and working toward a greater purpose, and be empowered to reach your full potential through various development programs designed to accelerate your growth. Plexus offers a comprehensive benefits package designed to support team members' wellbeing, including medical, dental, and vision insurance, paid time off, retirement savings, and opportunities for professional development. We also prioritize work-life balance and offer a variety of perks to enhance the team member experience. For more information, visit our US benefits website at usbenefits.plexus.com." But note benefits also appear later; we might duplicate. We'll keep benefits section separate; but we can still include this paragraph as part of About the role (company overview). It mentions benefits but we will still have a Benefits section later; that's okay as long as we don't duplicate exact same sentences? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep that benefits info somewhere. If we put it in About the role and also in Benefits section, that's duplication. Better to avoid duplication: we could put the benefits details only in Benefits section, and not repeat them in About the role. However the About us paragraph includes benefits description; we could keep it but then Benefits section would be duplicate. The instruction says preserve ALL substantive information; duplication is not forbidden but might be considered redundant. It says "remove duplicated lines". So we should avoid duplicating the same lines. So we should not repeat the benefits description in both places. We'll keep the benefits description only in Benefits section, and in About the role we can omit the benefits sentence or rephrase? But we cannot invent or summarize away detail; we can omit if it's duplicated elsewhere? The instruction: "remove duplicated lines". So if the same sentence appears elsewhere, we can remove one occurrence. So we can keep the benefits description only in Benefits section, and remove it from About the role paragraph. However the About us paragraph also includes other info about vision, values, etc. We'll keep those. Thus we need to edit the About us paragraph to remove the benefits sentence: "Plexus offers a comprehensive benefits package designed to support team members' wellbeing, including medical, dental, and vision insurance, paid time off, retirement savings, and opportunities for professional development. We also prioritize work-life balance and offer a variety of perks to enhance the team member experience. For more information, visit our US benefits website at usbenefits.plexus.com." We'll remove those sentences. Now About the role: we also have Position Overview paragraph: "At Plexus, lead technology-driven initiatives as part of a winning team, focused on creating products that build a better world. Position Overview: Manager, Global Network Operations is a strategic role responsible for the engineering and operational evolution of our core enterprise networking ecosystem. You will be a key technical leader for solutions spanning our global SD-WAN footprint, Google Cloud Platform (GCP) connectivity, Intent-Based Networking (IBN), and factory-edge/OT environments. The ideal candidate is a deep-thinking strategic leader able to operationalize scalable, robust, and secure network architectures. You will be instrumental in modernizing our digital backbone, right-sizing datacenter fabrics, and ensuring seamless, zero-downtime connectivity across our enterprise, from local manufacturing plants to global cloud landing zones." We can combine About us (company overview) and Position Overview under About the role heading. Now Responsibilities: list of bullet points under "Key Responsibilities". We need to extract each bullet. The text: "Key Responsibilities Global Network Strategy & Execution: Own the end-to-end lifecycle, and 24/7 operational performance of enterprise WAN, SD-WAN, LAN, Wi-Fi, and GCP cloud networking environments.Software-Defined & Intent-Based Networking: Drive the transition toward Intent-Based Networking (IBN) and AIOps, translating business policies into declarative network state and automated closed-loop assurance.GCP Cloud & SASE Architecture: Optimize resilient, low-latency connectivity between on-premise sites, factory edge nodes, and GCP (Cloud Interconnect, Cloud Router, Shared VPCs) utilizing SASE and Zero Trust Network Access (ZTNA) frameworks.Datacenter Fabric Right-Sizing: Deliver modern EVPN-VXLAN Leaf-Spine datacenter fabrics; manage the compression and optimization of on-premise hardware footprints as workloads migrate into GCP.Network Automation & IaC: Lead a "Network as Code" strategy, driving continuous integration and automated change management via Terraform, Ansible, Python, and GitOps workflows.IT/OT Convergence & Manufacturing Integration: Partner with manufacturing and OT security teams to deploy, segment, and protect shop-floor networks (Purdue Model, industrial firewalls) and plant-floor compute nodes.Governance & Global Team Leadership: Direct and mentor a team of high-performing network engineers across regions). Establish operational standards, SLOs/SLAs, observability metrics, and seamless escalation paths with the Global NOC.Carrier & Vendor Management: Manage commercial contracts, SLAs, and relationships with global ISP carriers, telecom providers, and hardware vendors." We need to split into list items. Each bullet seems separated by a period after the colon? Actually each heading ends with colon then description. We'll make each as

• with the heading bold? Not required; just plain text. We'll produce list items: - Global Network Strategy & Execution: Own the end-to-end lifecycle, and 24/7 operational performance of enterprise WAN, SD-WAN, LAN, Wi-Fi, and GCP cloud networking environments. - Software-Defined & Intent-Based Networking: Drive the transition toward Intent-Based Networking (IBN) and AIOps, translating business policies into declarative network state and automated closed-loop assurance. - GCP Cloud & SASE Architecture: Optimize resilient, low-latency connectivity between on-premise sites, factory edge nodes, and GCP (Cloud Interconnect, Cloud Router, Shared VPCs) utilizing SASE and Zero Trust Network Access (ZTNA) frameworks. - Datacenter Fabric Right-Sizing: Deliver modern EVPN-VXLAN Leaf-Spine datacenter fabrics; manage the compression and optimization of on-premise hardware footprints as workloads migrate into GCP. - Network Automation & IaC: Lead a "Network as Code" strategy, driving continuous integration and automated change management via Terraform, Ansible, Python, and GitOps workflows. - IT/OT Convergence & Manufacturing Integration: Partner with manufacturing and OT security teams to deploy, segment, and protect shop-floor networks (Purdue Model, industrial firewalls) and plant-floor compute nodes. - Governance & Global Team Leadership: Direct and mentor a team of high-performing network engineers across regions. Establish operational standards, SLOs/SLAs, observability metrics, and seamless escalation paths with the Global NOC. - Carrier & Vendor Management: Manage commercial contracts, SLAs, and relationships with global ISP carriers, telecom providers, and hardware vendors. Note there is a stray ")". We'll fix. Now Requirements: The posting has "Qualifications & Experience" section with bullet-like sentences. We'll extract each requirement. Text: "Qualifications & Experience Bachelor's degree in Computer Science, Information Systems, Network Engineering, or a related field. Master’s degree in a relevant field preferred.5+ years of related experience in enterprise network engineering required, 10+ years of progressive experience in IT preferred.3+ years of experience in a technical leadership or engineering management role overseeing distributed global teams preferred.Proven track record leading enterprise-wide SD-WAN transformations (e.g., Cisco, Fortinet, Palo Alto) and SASE/ZTNA deployments (e.g., Prisma).Deep functional and technical knowledge of Google Cloud Platform (GCP) cloud-native networking (Shared VPCs, Cloud Interconnect, Cloud Router, VPC Service Controls).Demonstrated experience designing EVPN-VXLAN Leaf-Spine topologies, micro-segmentation, and right-sizing hybrid/on-premise datacenter networks during active cloud migrations.Proficiency in managing network infrastructure through automation pipelines using Infrastructure as Code (IaC) tools such as Terraform, Ansible, Python, and Git/GitOps.Expert knowledge of core protocols including BGP (multi-homing