Sr. Network Engineer (Direct Hire, No C2C)
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But we can use other headings if they match content? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use those headings when appropriate. However we can also use other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they want us to use those exact headings when we have that content. But we have content like "Job Description" which could map to "About the role" or "Responsibilities". "Technical Stack And Experience Needed" could be "Requirements" or "Qualifications". "Top Skills' Details" and "Secondary Skills - Nice TonHaves" could be "Skills". "Pay And Benefits" could be "Pay" and "Benefits". "Workplace Type" could be "Schedule"? Actually schedule is about work schedule; we have hybrid position. Could be "Schedule". "Job Type & Location" maybe not a standard heading; but we could embed location in a paragraph. "Application Deadline" maybe not needed; could be omitted as minor metadata. "About TEKsystems" and "About TEKsystems And TEKsystems Global Services" could be combined into a paragraph about company; but we might drop as boilerplate? It's not EEO/legal but it's company description; maybe keep as a short paragraph under "About the role"? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company description is not exactly boilerplate but could be considered generic; but it's substantive about the employer. Might keep as a brief paragraph.
We need to preserve ALL substantive information; do NOT invent or summarize away detail. Remove duplicated lines. So we need to include details: top skills: Cisco Networking Expertise, Team-focused and Collaborative, min 7 years in networking role, ideally has been a sr in the past. Secondary skills: Firewall, Cisco switches, Data center, Switches. Also technical stack details: Cisco Nexus and Catalyst switching, Cisco Meraki networking and Cisco WiFi environments, Advanced routing and enterprise networking fundamentals including BGP and CCNA/CCNP-level knowledge, LAN-to-LAN VPNs, Azure ExpressRoute, WAN connectivity, hybrid network connectivity, Firewall operations awareness, Cisco ISE operations, network analyzers, network monitoring tools, Some Data center infrastructure awareness including CRAC, UPS, PDU, ATS, rack/stack work, cabling, fiber standards, copper cabling standards.
Responsibilities: Lead day-to-day support, monitoring, configuration, repair, and lifecycle work for network equipment and connected devices. Support and troubleshoot WAN, LAN, WiFi, internet, VPN, firewall-related, and application connectivity issues. Serve as an escalation point and mentor for other network team members. Partner with internal IT teams, vendors, and suppliers to deliver network projects and resolve service issues. Support disaster planning, documentation, inventory tracking, budgeting, and standards development.
Job Type & Location: Permanent position based out of Lansing, MI.
Pay And Benefits: Pay range $99,000.00 - $127,000.00/yr. Individual compensation depends on many factors... Offers a competitive benefits package centered on health coverage, retirement savings, paid time off, parental leave, flexible work arrangements, career development, and a family-oriented culture that emphasizes community involvement and employee growth.
Workplace Type: This is a hybrid position in Lansing, MI.
Application Deadline: anticipated to close on Oct 8, 2026.
About TEKsystems: description.
About TEKsystems And TEKsystems Global Services: similar.
We need to avoid repeating job title as heading. The job title is "sr Network Engineer". Not to repeat.
We need to output only HTML fragment, no /, no markdown.
We need to decide which sections to include. Likely sections: About the role (maybe combine job description and responsibilities?), Responsibilities, Requirements (or Qualifications), Skills, Pay, Benefits, Schedule (maybe hybrid), Location? But we have location in Job Type & Location. Could embed location in a paragraph under About the role or separate.
We need to avoid filler like "commensurate with experience". Not present.
We need to include a section only when posting has real, specific content for it. So we can include sections: About the role (maybe short intro), Responsibilities, Requirements (or Qualifications), Skills, Pay, Benefits, Schedule (maybe hybrid), Location? But location could be part of About the role or Job Type.
Better to follow typical headings: About the role, Responsibilities, Requirements, Skills, Pay, Benefits, Schedule. We'll embed location in About the role or Requirements.
Let's extract content:
About the role: Could be a brief summary: "The sr Network Engineer will serve as a technical leader for enterprise network operations, data center connectivity, WAN, wireless, VPN, firewall-adjacent networking, and network reliability. This role needs someone who can lead complex troubleshooting, manage vendors, guide other team members, and support infrastructure planning over the next few years." Also mention permanent position based out of Lansing, MI, hybrid.
Responsibilities: list bullet points.
Requirements: maybe combine Technical Stack And Experience Needed plus top skills details. Could be "Requirements" heading.
Skills: list top skills and secondary skills.
Pay: pay range.
Benefits: benefits package.
Schedule: hybrid position.
We need to avoid duplication: Technical Stack details also include skills; but we can keep them under Requirements.
Let's craft HTML:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they want us to use those exact headings when we have that content. But we have content like "Job Description" which could map to "About the role" or "Responsibilities". "Technical Stack And Experience Needed" could be "Requirements" or "Qualifications". "Top Skills' Details" and "Secondary Skills - Nice TonHaves" could be "Skills". "Pay And Benefits" could be "Pay" and "Benefits". "Workplace Type" could be "Schedule"? Actually schedule is about work schedule; we have hybrid position. Could be "Schedule". "Job Type & Location" maybe not a standard heading; but we could embed location in a paragraph. "Application Deadline" maybe not needed; could be omitted as minor metadata. "About TEKsystems" and "About TEKsystems And TEKsystems Global Services" could be combined into a paragraph about company; but we might drop as boilerplate? It's not EEO/legal but it's company description; maybe keep as a short paragraph under "About the role"? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company description is not exactly boilerplate but could be considered generic; but it's substantive about the employer. Might keep as a brief paragraph.
We need to preserve ALL substantive information; do NOT invent or summarize away detail. Remove duplicated lines. So we need to include details: top skills: Cisco Networking Expertise, Team-focused and Collaborative, min 7 years in networking role, ideally has been a sr in the past. Secondary skills: Firewall, Cisco switches, Data center, Switches. Also technical stack details: Cisco Nexus and Catalyst switching, Cisco Meraki networking and Cisco WiFi environments, Advanced routing and enterprise networking fundamentals including BGP and CCNA/CCNP-level knowledge, LAN-to-LAN VPNs, Azure ExpressRoute, WAN connectivity, hybrid network connectivity, Firewall operations awareness, Cisco ISE operations, network analyzers, network monitoring tools, Some Data center infrastructure awareness including CRAC, UPS, PDU, ATS, rack/stack work, cabling, fiber standards, copper cabling standards.
Responsibilities: Lead day-to-day support, monitoring, configuration, repair, and lifecycle work for network equipment and connected devices. Support and troubleshoot WAN, LAN, WiFi, internet, VPN, firewall-related, and application connectivity issues. Serve as an escalation point and mentor for other network team members. Partner with internal IT teams, vendors, and suppliers to deliver network projects and resolve service issues. Support disaster planning, documentation, inventory tracking, budgeting, and standards development.
Job Type & Location: Permanent position based out of Lansing, MI.
Pay And Benefits: Pay range $99,000.00 - $127,000.00/yr. Individual compensation depends on many factors... Offers a competitive benefits package centered on health coverage, retirement savings, paid time off, parental leave, flexible work arrangements, career development, and a family-oriented culture that emphasizes community involvement and employee growth.
Workplace Type: This is a hybrid position in Lansing, MI.
Application Deadline: anticipated to close on Oct 8, 2026.
About TEKsystems: description.
About TEKsystems And TEKsystems Global Services: similar.
We need to avoid repeating job title as heading. The job title is "sr Network Engineer". Not to repeat.
We need to output only HTML fragment, no /, no markdown.
We need to decide which sections to include. Likely sections: About the role (maybe combine job description and responsibilities?), Responsibilities, Requirements (or Qualifications), Skills, Pay, Benefits, Schedule (maybe hybrid), Location? But we have location in Job Type & Location. Could embed location in a paragraph under About the role or separate.
We need to avoid filler like "commensurate with experience". Not present.
We need to include a section only when posting has real, specific content for it. So we can include sections: About the role (maybe short intro), Responsibilities, Requirements (or Qualifications), Skills, Pay, Benefits, Schedule (maybe hybrid), Location? But location could be part of About the role or Job Type.
Better to follow typical headings: About the role, Responsibilities, Requirements, Skills, Pay, Benefits, Schedule. We'll embed location in About the role or Requirements.
Let's extract content:
About the role: Could be a brief summary: "The sr Network Engineer will serve as a technical leader for enterprise network operations, data center connectivity, WAN, wireless, VPN, firewall-adjacent networking, and network reliability. This role needs someone who can lead complex troubleshooting, manage vendors, guide other team members, and support infrastructure planning over the next few years." Also mention permanent position based out of Lansing, MI, hybrid.
Responsibilities: list bullet points.
Requirements: maybe combine Technical Stack And Experience Needed plus top skills details. Could be "Requirements" heading.
Skills: list top skills and secondary skills.
Pay: pay range.
Benefits: benefits package.
Schedule: hybrid position.
We need to avoid duplication: Technical Stack details also include skills; but we can keep them under Requirements.
Let's craft HTML:
About the role
The sr Network Engineer will serve as a technical leader for enterprise network operations, data center connectivity, WAN, wireless, VPN, firewall-adjacent networking, and network reliability. This role needs someone who can lead complex troubleshooting, manage vendors, guide other team members, and support infrastructure planning over the next few years. This is a permanent position based out of Lansing, MI, with a hybrid work arrangement.
Responsibilities
- Lead day-to-day support, monitoring, configuration, repair, and lifecycle work for network equipment and connected devices.
- Support and troubleshoot WAN, LAN, WiFi, internet, VPN, firewall-related, and application connectivity issues.
- Serve as an escalation point and mentor for other network team members.
- Partner with internal IT teams, vendors, and suppliers to deliver network projects and resolve service issues.
- Support disaster planning, documentation, inventory tracking, budgeting, and standards development.
Requirements
- Minimum of 7 years in a networking role, ideally having been a senior engineer previously.
- Cisco Networking Expertise.
- Team-focused and collaborative.
- Cisco Nexus and Catalyst switching – configuration, monitoring, repair, lifecycle support.
- Cisco Meraki networking and Cisco WiFi environments.
- Advanced routing and enterprise networking fundamentals, including BGP and CCNA/CCNP-level knowledge.
- LAN-to-LAN VPNs, Azure ExpressRoute, WAN connectivity, hybrid network connectivity.
- Firewall operations awareness, Cisco ISE operations, network analyzers, network monitoring tools.
- Some data center infrastructure awareness, including CRAC, UPS, PDU, ATS, rack/stack work, cabling, fiber standards, copper cabling standards.
Skills
- Top Skills: Cisco Networking Expertise, Team-focused and Collaborative.
- Secondary Skills (Nice-to-Have): Firewall, Cisco switches, Data center, Switches.
Pay
The pay range for this position is $99,000.00 - $127,000.00 per year.
Benefits
Offers a competitive benefits package centered on health coverage, retirement savings, paid time off, parental leave, flexible work arrangements, career development, and a family‑oriented culture that emphasizes community involvement and employee growth.
Schedule
This is a hybrid position in Lansing, MI.
We omitted Application Deadline and About TEKsystems descriptions. Are those considered substantive? They are about company; maybe we can include a brief "About the company" section? But not in the list of suggested headings. Could we add a section "About the company"? The instruction says use