Sr. OT Network Engineer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to extract content from posting. We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, legal, application instructions, etc. Also remove duplicated lines. We need to preserve all substantive info. Let's parse posting: Title: SENIOR NETWORK ENGINEER-OT Onsite-JACKSON, TN OT-Operations TechnologyManufacturingNetworkingEngineerFirewallTroubleshootingAutomationCMBDICSSCADACiscoData Center Description: Our manufacturing client is hiring a SENIOR NETWORK ENGINEER-OT to support Operational Technologies. The SENIOR NETWORK ENGINEER-OT will lead the design, deployment, and sustainment of secure and scalable Operational Technology (OT) networks across manufacturing environments. The SENIOR NETWORK ENGINEER-OT is a hands-on leadership role bridging the gap between Operational Technology and Information Technology. Together, the SENIOR NETWORK ENGINEER-OT will enable automation, secure connectivity, and digital transformation across production sites. DUTIES: list of duties. Then Qualifications: bullet list. Then WORK ENVIRONMENT: 10% Travel to support local sites Manufacturing Operation Technology Cisco Onsite 24/7 Support INTERVIEWS & START DATE: Interviews September 21-25 Start Date October 5, 2026 Job Type & Location: This is a Contract to Hire position based out of Jackson, TN. Pay And Benefits: The pay range for this position is $65.00 - $72.00/hr. Individual compensation offered for this position within this range will depend on many factors, including qualifications, skills, relevant experience, job knowledge, geographic location, internal equity, and other pertinent job-related factors. Eligibility requirements apply to some benefits and may depend on your job classification and length of employment. Benefits are subject to change and may be subject to specific elections, plan, or program terms. If eligible, the benefits available for this temporary role may include the following: Medical, dental & vision Critical Illness, Accident, and Hospital 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available Life Insurance (Voluntary Life & AD&D for the employee and dependents) Short and long-term disability Health Spending Account (HSA) Transportation benefits Employee Assistance Program Time Off/Leave (PTO, Vacation or Sick Leave) Workplace Type This is a fully onsite position in Jackson,TN. Application Deadline: This position is anticipated to close on Sep 16, 2026. About TEKsystems: paragraphs. We need to remove boilerplate: EEO, equal opportunity, legal, etc. Also remove duplicated lines like "About TEKsystems" repeated. We need to include sections only if real content. Potential sections: - About the role: we have description paragraph(s) about role. Could be "About the role". Use that heading. - Responsibilities: duties list. - Requirements: maybe qualifications? There's "Qualifications" heading already. Could map to Requirements or Qualifications. The instruction: use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have qualifications bullet list: Bachelor’s in Computer Science, Engineering, IT, or equivalent experience; 5+ years in network engineering; Experience working in cross-functional teams across Operations, IT, and Security; Strong Cisco networking background; Strong OT security experience: segmentation, firewalls, secure remote access; Wireless deployment and troubleshooting in industrial environments; Experience with CMDB, change control, and network monitoring tools; Excellent communication and documentation skills across technical and non-technical teams. We also have "Skills" maybe could be extracted from duties? But we can keep Skills section if we have specific skill list. Could combine some of qualifications into Skills? But better to follow headings: Qualifications for those bullet points. Skills maybe for specific technical skills like Cisco, OT security, wireless, CMDB, etc. However we already have those in qualifications. Might be redundant. But we can still include Skills if we have distinct content. The posting doesn't have a separate "Skills" section besides qualifications. Could omit Skills if no distinct content. - Benefits: we have benefits list. - Pay: we have pay range. - Schedule: we have workplace type (fully onsite) and maybe 24/7 support, 10% travel. Could be schedule info. The schedule could be "Workplace Type: fully onsite" and "10% Travel". Also "24/7 Support". We'll include schedule. - Requirements: maybe we can put some of the qualifications under Requirements? But we already have Qualifications heading. The instruction says use those headings if content exists. We can have both Requirements and Qualifications if we split content. But we need to avoid filler. Let's decide: Use "Requirements" for mandatory experience/education (Bachelor’s, 5+ years, cross-functional teams). Use "Qualifications" for preferred or additional qualifications (Strong Cisco networking background, OT security experience, wireless, CMDB, communication). Or we could just use Qualifications for all and skip Requirements. But better to use both if we can split meaningfully. Let's extract: Requirements (mandatory): - Bachelor’s in Computer Science, Engineering, IT, or equivalent experience - 5+ years in network engineering - Experience working in cross-functional teams across Operations, IT, and Security Qualifications (preferred/additional): - Strong Cisco networking background - Strong OT security experience: segmentation, firewalls, secure remote access - Wireless deployment and troubleshooting in industrial environments - Experience with CMDB, change control, and network monitoring tools - Excellent communication and documentation skills across technical and non-technical teams Skills: maybe we could list specific technical skills: Cisco IE switches, firewalls, routers, Cisco DNA Center, Industrial Network Director, Cyber Vision, ICS, SCADA, IIoT, smart devices, network segmentation/zoning aligned to Purdue Model, ISA/IEC 62443, NIST, patching OT networking hardware. But those are in duties. Could create Skills section from duties. However we already have Responsibilities covering duties. Skills could be separate but might be redundant. The instruction says prefer a few substantive sections over many thin ones. So maybe we skip Skills if not distinct. Benefits: list as given. Pay: pay range. Schedule: we have workplace type (fully onsite), 10% travel, 24/7 support. Also maybe start date and interviews? Those are not schedule but could be under Schedule? The instruction says Schedule section for schedule info. Could include "Workplace Type: fully onsite", "10% Travel to support local sites", "24/7 Support". Also maybe "Interviews September 21-25" and "Start Date October 5, 2026" but those are more about hiring process, not schedule. Might be better to omit or include under Schedule? The instruction says include section only when posting has real, specific content for it. The posting does have schedule info (onsite, travel, 24/7). So we can include Schedule. We also have "Job Type & Location": Contract to Hire position based out of Jackson, TN. That's location info. Could be part of Schedule? Or maybe we could include location under Schedule? But schedule is about work schedule, not location. However we have no separate heading for Location. Could we include location under Schedule? Might be okay but not ideal. Could we create a separate section? Not in allowed headings. So we might fold location into Schedule or maybe into About the role? The location is Jackson, TN. Could be included in Schedule as "Location: Jackson, TN (onsite)". Or we could add a short paragraph under About the role? But better to include location in Schedule. Also we have "Application Deadline" Sep 16, 2026. That's not schedule but could be omitted as it's application instruction? It's not application instructions but deadline. Might be considered metadata; we could drop as minor metadata. The instruction says do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short

or drop it. So we can drop application deadline or fold into a short p maybe under About the role? Probably drop. Also "Interviews & START DATE" could be folded into Schedule? Might be considered schedule? Not exactly. Could be minor metadata; we could drop. We need to preserve all substantive information. The interview dates and start date are substantive for candidate. Might be worth keeping. Could we put them under Schedule? Schedule usually refers to work schedule, not hiring timeline. But we could create a separate section? Not allowed. Could we put them under About the role? Might be okay as additional info. But the instruction says prefer few substantive sections over many thin ones. So we could include a short paragraph under About the role that includes start date and interview window. Or we could create a separate section "Schedule" and include both work schedule and hiring timeline? Might be confusing. Better: Keep Schedule for work schedule (onsite, travel, 24/7). Keep location maybe also there. For hiring timeline (interviews, start date) we could drop as minor metadata? But it's substantive. However the instruction says "fold minor metadata into a short

or drop it." Interview dates and start date might be considered minor metadata? Not sure. But they are important for candidate. I'd keep them maybe under About the role as a note. Let's see if any other sections: "About TEKsystems" is boilerplate about the company; we should remove as per instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About TEKsystems" is company description, likely boilerplate. Should remove. Thus final HTML will have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title as heading. So no

  for the title. We need to preserve all substantive information: duties list, qualifications, benefits, pay, schedule, location, etc. Let's craft content. About the role: combine description paragraphs: "Our manufacturing client is hiring a SENIOR NETWORK ENGINEER-OT to support Operational Technologies. The SENIOR NETWORK ENGINEER-OT will lead the design, deployment, and sustainment of secure and scalable Operational Technology (OT) networks across manufacturing environments. The SENIOR NETWORK ENGINEER-OT is a hands-on leadership role bridging the gap between Operational Technology and Information Technology. Together, the SENIOR NETWORK ENGINEER-OT will enable automation, secure connectivity, and digital transformation across production sites." Also maybe include location? We'll keep location in Schedule. Responsibilities: list duties from DUTIES section. Let's extract each bullet: - Bridge the gap between IT and OT with high-impact technical leadership - Build secure, resilient industrial networks that enable Industry 4.0 - Shape OT standards, architecture, and cybersecure design practices - Make a tangible impact on uptime, safety, and connectivity across plants - Collaborate closely with Process/Automation Engineers, IT, and InfoSec teams to architect and support robust industrial networking solutions that are critical to our success in modern manufacturing. - Design, configure, and deploy OT wired/wireless network infrastructure in production environments - Maintain and optimize industrial network performance, uptime, and security - Lead Tier 3 troubleshooting and root cause analysis of OT network incidents - Contribute to network architecture decisions, standards, and design blueprints - Partner with engineering teams to integrate ICS, SCADA, IIoT, and smart devices