Cisco Network Engineer II
for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should only include sections that have real specific content.
We have pay: $56.00/hr - $66.00/hr based on experience and academia. So we can have Pay section.
Schedule: Hybrid: Onsite 3 days per week in either Charlotte NC, Raleigh NC, Cincinnati OH, St. Petersburg FL, or Plainfield IN. So we can have Schedule section.
Benefits: The posting says: no PTO or benefits; ACA compliance medical coverage available for enrollment. That's a benefit? It says no PTO or benefits; ACA compliance medical coverage available for enrollment. That's minimal. Should we include Benefits? It says "no PTO or benefits; ACA compliance medical coverage available for enrollment". That's somewhat a benefit (medical coverage). But the rule: never create Benefits section unless posting actually states them. It does state ACA compliance medical coverage available for enrollment. So we can include Benefits with that detail.
We also have Contract: 12 months, extensions likely, conversion possible. Could be part of About the role or maybe a Contract section? Not in list of headings. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to fit contract info somewhere, maybe About the role.
Location: hybrid position operating out of those cities. Could be in About the role or Schedule.
We need to avoid repeating job title as heading. Not include Job ID etc.
We need to preserve all substantive information. So we need to include summary, responsibilities, required qualifications, desired qualifications, candidate profile, pay, contract, type, hybrid schedule, location, benefits (ACA medical coverage). Also note type: W-2, cannot support C2C or provide visa sponsorship; no PTO or benefits; ACA compliance medical coverage available for enrollment.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We need to decide which sections to use.
Possible sections:
- About the role (summary + contract + type + location maybe)
- Responsibilities (list)
- Requirements (maybe required qualifications)
- Qualifications (maybe desired qualifications)
- Skills (maybe combine desired qualifications? But we have both required and desired; maybe we put required under Requirements, desired under Qualifications, and maybe Skills separate? But we can also put desired under Qualifications and maybe Skills not needed. However we must only include sections when posting has real specific content. We have content for Responsibilities, Required Qualifications, Desired Qualifications, Candidate Profile (maybe part of About the role). We have Pay, Schedule, Benefits.
We need to avoid filler like "commensurate with experience". Not present.
We'll produce:
About the role
Primary Talent Partners has a 12 month contract opening for a Cisco Network Engineer II to join a national energy & utilities company for a hybrid position operating out of Charlotte NC, Raleigh NC, Cincinnati OH, St. Petersburg FL, or Plainfield IN. Pay: $56.00/hr - $66.00/hr based on experience and academia. Contract: 12 months, extensions likely, conversion possible. Type: W-2, cannot support C2C or provide visa sponsorship; no PTO or benefits; ACA compliance medical coverage available for enrollment. Hybrid: Onsite 3 days per week in either Charlotte NC, Raleigh NC, Cincinnati OH, St. Petersburg FL, or Plainfield IN.
But we also have separate Pay and Schedule sections; we might move pay and schedule to their own sections. However we already included them in About the role; but we could still have separate sections. The rule: prefer a few substantive sections over many thin ones. So maybe combine pay and schedule into About the role is okay. But we also need Benefits section.
We have Benefits: ACA compliance medical coverage available for enrollment. Also note "no PTO or benefits". So we can state that.
Thus Benefits section: No PTO or other benefits; ACA-compliant medical coverage available for enrollment.
Now Responsibilities: list.
Requirements: required qualifications list.
Qualifications: desired qualifications list.
Skills: maybe we could combine desired qualifications into Skills? But we already have Qualifications for desired. Could also put Skills separate but we might not need.
We need to ensure we don't repeat content. Let's extract responsibilities list from posting:
- Configure, implement, test, and support Cisco routers, switches, wireless access points, and related network infrastructure using established architecture standards and templates.
- Deploy and support Cisco Catalyst SD-WAN solutions, including WAN edge routers, transport connectivity, segmentation, centralized policies, and application-aware routing.
- Support WAN modernization across SD-WAN, MPLS, private Ethernet, internet, cellular, and other public or private WAN services.
- Troubleshoot routing, switching, SD-WAN, wireless, WAN connectivity, firewall policy, and Layer 2/Layer 3 communication issues.
- Implement and validate network resiliency, segmentation, failover, quality of service, and high-availability capabilities.
- Prepare engineering job packages with equipment lists, installation instructions, implementation and test plans, rollback procedures, and supporting documentation.
- Create and maintain physical and logical network drawings, rack elevations, wiring diagrams, layouts, and power drawings using Microsoft Visio.
- Ensure monitoring, alarming, logging, asset records, and operational documentation are complete before solutions are placed into service.
- Coordinate, activate, test, and troubleshoot private and public WAN circuits.
- Monitor implementation work for compliance with engineering standards, cybersecurity requirements, applicable regulations, and approved procedures.
- Support network automation using Python, Ansible, REST APIs, Git, or similar scripting and orchestration technologies.
- Collaborate with engineering, operations, cybersecurity, field resources, telecommunications carriers, vendors, and business partners.
- Follow formal change management practices, including impact analysis, peer review, approvals, validation, rollback planning, and documentation.
- Participate in planned implementations, maintenance, and troubleshooting outside normal business hours when required.
- Work within an Agile engineering environment on team-based projects and assignments.
Now Required Qualifications list:
- High school diploma or GED.
- 5 years hands on experience in an Enterprise Environment
- Ability to successfully complete required background screening.
- Demonstrated experience configuring, implementing, or supporting Cisco routers and switches.
- Solid understanding of IPv4, subnetting, TCP/IP, VLANs, IEEE 802.1Q trunks, Spanning Tree Protocol, and link aggregation.
- Working knowledge of OSPF, BGP, enterprise WAN concepts, and route selection.
- Ability to troubleshoot Layer 2 and Layer 3 connectivity issues using a structured approach.
- General understanding of wireless, firewall, access control, and network segmentation technologies.
- Working knowledge of copper and fiber cabling standards and connector types.
- Ability to create and maintain accurate technical documentation and network diagrams.
- Strong attention to detail and ability to follow engineering, cybersecurity, and change management processes.
- Effective written, verbal, interpersonal, and teamwork skills.
- Ability to work productively with limited direct supervision.
- Willingness and ability to support scheduled work outside normal business hours when required.
Desired Qualifications list:
- Cisco CCNA, CCNP Enterprise, CCNP Security, or comparable demonstrated experience.
- Experience with Cisco Catalyst platforms and Cisco IOS or IOS-XE.
- Experience deploying, migrating, supporting, or troubleshooting Cisco Catalyst SD-WAN, formerly Cisco Viptela.
- Advanced knowledge of OSPF and BGP, including path selection, filtering, summarization, and redistribution.
- Experience with VRFs, MPLS Layer 3 VPNs, DMVPN, IPsec, quality of service, route maps, prefix lists, access control lists, and BGP communities.
- Experience with Cisco Catalyst Center, Cisco ISE, Cisco ACI, or controller-based wireless technologies.
- Experience with Palo Alto Networks firewalls or Cisco Secure Firewall.
- Experience using Python, Ansible, REST APIs, Git, PowerShell, Bash, or similar technologies for network automation.
- Experience with SolarWinds, BlueCat IPAM, Opengear terminal servers, SNMP, syslog, NetFlow, or packet analysis tools.
- Experience preparing engineering job packages, implementation plans, test plans, rollback plans, equipment lists, and network diagrams.
- Ability to develop effective prompts that leverage generative AI tools to produce accurate, relevant, and business-focused outcomes.
- Experience with SCADA communications, operational technology networks, substations, control centers, regulated utilities, or other critical infrastructure.
- Experience with Jira, Agile methodologies, and formal change management processes.
- Self-directed, organized, collaborative, and willing to learn new technologies.
Candidate Profile paragraph: "Candidates do not need experience with every technology listed. Individuals with a strong Cisco routing and switching foundation, practical troubleshooting ability, disciplined change and documentation practices, and an interest in developing deeper SD-WAN and automation expertise are encouraged to apply"
We could incorporate that into About the role or maybe a separate section like "Candidate Profile". But not in allowed headings. Could put under About the role as a paragraph.
We need to avoid duplication. The summary already mentions seeking a Telecom Data Network Engineer to support implementation, modernization, lifecycle management of critical network infrastructure across Midwest region. That's part of About the role.
Thus About the role could include summary + contract + type + location + hybrid schedule + pay + benefits? But we decided to have separate Benefits section. We could keep About the role with summary, contract, type, location, hybrid schedule, candidate profile. Pay and Schedule separate.
But we already have Pay and Schedule sections; we could still include them in About the role but that would duplicate. Better to keep them separate.
Thus:
- About the role: summary, contract, type, location, hybrid schedule? Actually schedule is separate; we could keep location and hybrid mention in About the role but schedule separate. Might be okay.
But we need to avoid too many sections. Let's decide:
Sections:
- About the role (summary, contract, type, location, hybrid note maybe)
- Responsibilities
- Requirements (required qualifications)
- Qualifications (desired qualifications)
- Benefits
- Pay
- Schedule
That's 7 sections. Might be okay but we could combine some. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we can combine Requirements and Qualifications into one "Requirements" section with subheadings? But we must use for section headings only; we cannot have subheadings. Could we put both required and desired under Requirements with separate
paragraphs? That would be okay. But we need to preserve all info; we can list required qualifications then desired qualifications in same section.
Similarly, we could combine Benefits, Pay, Schedule into one "Compensation & Logistics" but not allowed headings. So we need to stick to allowed headings.
We could have About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. That's 6 sections. Qualifications (desired) could be merged into Requirements.
Let's do that.
Thus:
About the role
Primary Talent Partners has a 12 month contract opening for a Cisco Network Engineer II to join a national energy & utilities company for a hybrid position operating out of Charlotte NC, Raleigh NC, Cincinnati OH, St. Petersburg FL, or Plainfield IN. Summary: Seeking a Telecom Data Network Engineer to support the implementation, modernization, and lifecycle management of critical network infrastructure across the Midwest region. This role provides hands-on experience with Cisco enterprise routing, switching, SD-WAN, wireless, and network security technologies supporting substations, corporate offices, and other business-critical locations. Contract: 12 months, extensions likely, conversion possible. Type: W-2, cannot support C2C or provide
for prose. We need to decide which sections to use. Possible sections: - About the role (summary + contract + type + location maybe) - Responsibilities (list) - Requirements (maybe required qualifications) - Qualifications (maybe desired qualifications) - Skills (maybe combine desired qualifications? But we have both required and desired; maybe we put required under Requirements, desired under Qualifications, and maybe Skills separate? But we can also put desired under Qualifications and maybe Skills not needed. However we must only include sections when posting has real specific content. We have content for Responsibilities, Required Qualifications, Desired Qualifications, Candidate Profile (maybe part of About the role). We have Pay, Schedule, Benefits. We need to avoid filler like "commensurate with experience". Not present. We'll produce:
About the role
Primary Talent Partners has a 12 month contract opening for a Cisco Network Engineer II to join a national energy & utilities company for a hybrid position operating out of Charlotte NC, Raleigh NC, Cincinnati OH, St. Petersburg FL, or Plainfield IN. Pay: $56.00/hr - $66.00/hr based on experience and academia. Contract: 12 months, extensions likely, conversion possible. Type: W-2, cannot support C2C or provide visa sponsorship; no PTO or benefits; ACA compliance medical coverage available for enrollment. Hybrid: Onsite 3 days per week in either Charlotte NC, Raleigh NC, Cincinnati OH, St. Petersburg FL, or Plainfield IN.
But we also have separate Pay and Schedule sections; we might move pay and schedule to their own sections. However we already included them in About the role; but we could still have separate sections. The rule: prefer a few substantive sections over many thin ones. So maybe combine pay and schedule into About the role is okay. But we also need Benefits section. We have Benefits: ACA compliance medical coverage available for enrollment. Also note "no PTO or benefits". So we can state that. Thus Benefits section:No PTO or other benefits; ACA-compliant medical coverage available for enrollment.
Now Responsibilities: list. Requirements: required qualifications list. Qualifications: desired qualifications list. Skills: maybe we could combine desired qualifications into Skills? But we already have Qualifications for desired. Could also put Skills separate but we might not need. We need to ensure we don't repeat content. Let's extract responsibilities list from posting: - Configure, implement, test, and support Cisco routers, switches, wireless access points, and related network infrastructure using established architecture standards and templates. - Deploy and support Cisco Catalyst SD-WAN solutions, including WAN edge routers, transport connectivity, segmentation, centralized policies, and application-aware routing. - Support WAN modernization across SD-WAN, MPLS, private Ethernet, internet, cellular, and other public or private WAN services. - Troubleshoot routing, switching, SD-WAN, wireless, WAN connectivity, firewall policy, and Layer 2/Layer 3 communication issues. - Implement and validate network resiliency, segmentation, failover, quality of service, and high-availability capabilities. - Prepare engineering job packages with equipment lists, installation instructions, implementation and test plans, rollback procedures, and supporting documentation. - Create and maintain physical and logical network drawings, rack elevations, wiring diagrams, layouts, and power drawings using Microsoft Visio. - Ensure monitoring, alarming, logging, asset records, and operational documentation are complete before solutions are placed into service. - Coordinate, activate, test, and troubleshoot private and public WAN circuits. - Monitor implementation work for compliance with engineering standards, cybersecurity requirements, applicable regulations, and approved procedures. - Support network automation using Python, Ansible, REST APIs, Git, or similar scripting and orchestration technologies. - Collaborate with engineering, operations, cybersecurity, field resources, telecommunications carriers, vendors, and business partners. - Follow formal change management practices, including impact analysis, peer review, approvals, validation, rollback planning, and documentation. - Participate in planned implementations, maintenance, and troubleshooting outside normal business hours when required. - Work within an Agile engineering environment on team-based projects and assignments. Now Required Qualifications list: - High school diploma or GED. - 5 years hands on experience in an Enterprise Environment - Ability to successfully complete required background screening. - Demonstrated experience configuring, implementing, or supporting Cisco routers and switches. - Solid understanding of IPv4, subnetting, TCP/IP, VLANs, IEEE 802.1Q trunks, Spanning Tree Protocol, and link aggregation. - Working knowledge of OSPF, BGP, enterprise WAN concepts, and route selection. - Ability to troubleshoot Layer 2 and Layer 3 connectivity issues using a structured approach. - General understanding of wireless, firewall, access control, and network segmentation technologies. - Working knowledge of copper and fiber cabling standards and connector types. - Ability to create and maintain accurate technical documentation and network diagrams. - Strong attention to detail and ability to follow engineering, cybersecurity, and change management processes. - Effective written, verbal, interpersonal, and teamwork skills. - Ability to work productively with limited direct supervision. - Willingness and ability to support scheduled work outside normal business hours when required. Desired Qualifications list: - Cisco CCNA, CCNP Enterprise, CCNP Security, or comparable demonstrated experience. - Experience with Cisco Catalyst platforms and Cisco IOS or IOS-XE. - Experience deploying, migrating, supporting, or troubleshooting Cisco Catalyst SD-WAN, formerly Cisco Viptela. - Advanced knowledge of OSPF and BGP, including path selection, filtering, summarization, and redistribution. - Experience with VRFs, MPLS Layer 3 VPNs, DMVPN, IPsec, quality of service, route maps, prefix lists, access control lists, and BGP communities. - Experience with Cisco Catalyst Center, Cisco ISE, Cisco ACI, or controller-based wireless technologies. - Experience with Palo Alto Networks firewalls or Cisco Secure Firewall. - Experience using Python, Ansible, REST APIs, Git, PowerShell, Bash, or similar technologies for network automation. - Experience with SolarWinds, BlueCat IPAM, Opengear terminal servers, SNMP, syslog, NetFlow, or packet analysis tools. - Experience preparing engineering job packages, implementation plans, test plans, rollback plans, equipment lists, and network diagrams. - Ability to develop effective prompts that leverage generative AI tools to produce accurate, relevant, and business-focused outcomes. - Experience with SCADA communications, operational technology networks, substations, control centers, regulated utilities, or other critical infrastructure. - Experience with Jira, Agile methodologies, and formal change management processes. - Self-directed, organized, collaborative, and willing to learn new technologies. Candidate Profile paragraph: "Candidates do not need experience with every technology listed. Individuals with a strong Cisco routing and switching foundation, practical troubleshooting ability, disciplined change and documentation practices, and an interest in developing deeper SD-WAN and automation expertise are encouraged to apply" We could incorporate that into About the role or maybe a separate section like "Candidate Profile". But not in allowed headings. Could put under About the role as a paragraph. We need to avoid duplication. The summary already mentions seeking a Telecom Data Network Engineer to support implementation, modernization, lifecycle management of critical network infrastructure across Midwest region. That's part of About the role. Thus About the role could include summary + contract + type + location + hybrid schedule + pay + benefits? But we decided to have separate Benefits section. We could keep About the role with summary, contract, type, location, hybrid schedule, candidate profile. Pay and Schedule separate. But we already have Pay and Schedule sections; we could still include them in About the role but that would duplicate. Better to keep them separate. Thus: - About the role: summary, contract, type, location, hybrid schedule? Actually schedule is separate; we could keep location and hybrid mention in About the role but schedule separate. Might be okay. But we need to avoid too many sections. Let's decide: Sections: - About the role (summary, contract, type, location, hybrid note maybe) - Responsibilities - Requirements (required qualifications) - Qualifications (desired qualifications) - Benefits - Pay - Schedule That's 7 sections. Might be okay but we could combine some. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we can combine Requirements and Qualifications into one "Requirements" section with subheadings? But we must usefor section headings only; we cannot have subheadings. Could we put both required and desired under Requirements with separate
paragraphs? That would be okay. But we need to preserve all info; we can list required qualifications then desired qualifications in same section. Similarly, we could combine Benefits, Pay, Schedule into one "Compensation & Logistics" but not allowed headings. So we need to stick to allowed headings. We could have About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. That's 6 sections. Qualifications (desired) could be merged into Requirements. Let's do that. Thus:
About the role
Primary Talent Partners has a 12 month contract opening for a Cisco Network Engineer II to join a national energy & utilities company for a hybrid position operating out of Charlotte NC, Raleigh NC, Cincinnati OH, St. Petersburg FL, or Plainfield IN. Summary: Seeking a Telecom Data Network Engineer to support the implementation, modernization, and lifecycle management of critical network infrastructure across the Midwest region. This role provides hands-on experience with Cisco enterprise routing, switching, SD-WAN, wireless, and network security technologies supporting substations, corporate offices, and other business-critical locations. Contract: 12 months, extensions likely, conversion possible. Type: W-2, cannot support C2C or provide