Data Center Network Operations Lead (Aiken, SC)

We need to output HTML fragment with sections: About the role? Actually the posting includes "OUR COMPANY:" description, "WHAT YOU WILL DO:", "KEY RESPONSIBILITIES:", "ESSENTIAL CRITERIA:", "DESIRABLE CRITERIA:", "PHYSICAL REQUIREMENTS:", "EOS BENEFITS:". Also mention pay? It says "The EOS pay range for this job is a general guideline only and not a guarantee of compensation or salary." That's not specific numbers, so we should NOT create Pay section because no specific pay. Schedule? It mentions rotational shifts to support 24/7/365 operations. That's schedule info. So we can include a Schedule section with that detail. Benefits we have specifics. Also we need to include About the role? The "WHAT YOU WILL DO:" could be considered About the role or Responsibilities. But we already have KEY RESPONSIBILITIES separate. We could have About the role as a brief summary from OUR COMPANY and WHAT YOU WILL DO? But instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. We have: - About the role: could be the company overview and what you will do (summary). We'll combine OUR COMPANY and WHAT YOU WILL DO into About the role. - Responsibilities: KEY RESPONSIBILITIES. - Requirements: ESSENTIAL CRITERIA (maybe also DESIRABLE CRITERIA could be Qualifications or Skills). But we have separate headings: Requirements, Qualifications, Skills. We need to decide where to put essential vs desirable. Could put essential under Requirements, desirable under Qualifications or Skills. But we must only include sections when posting has real specific content. We have both essential and desirable criteria. We could make Requirements = Essential Criteria, Qualifications = Desirable Criteria (certifications, experience). Skills could be maybe technical skills list? But we already have technical details in responsibilities. Might be redundant. Better to have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Schedule. Avoid Skills if not specific. We must not repeat job title as heading. No Job ID. We must remove boilerplate: EEO etc. Also remove "The EOS pay range for this job is a general guideline only..." because it's not specific pay; we should not create Pay section. Also remove "EOS is committed to creating a diverse..." etc. We need to preserve all substantive information. So we need to include details from OUR COMPANY, WHAT YOU WILL DO, KEY RESPONSIBILITIES (bulleted), ESSENTIAL CRITERIA, DESIRABLE CRITERIA, PHYSICAL REQUIREMENTS, EOS BENEFITS, and schedule note (rotational shifts 24/7/365, up to 10% travel). Also mention travel domestically up to 10%. We need to format lists with

• . For prose use

  . We need to ensure we don't include filler like "commensurate with experience". Not present. Let's craft. Section About the role: combine OUR COMPANY paragraph and WHAT YOU WILL DO paragraph (first two paragraphs). We'll put as

  maybe multiple paragraphs. Section Responsibilities: KEY RESPONSIBILITIES content. It's a long list with many bullet-like sentences. We'll turn each sentence into

• . Might be many; okay. Section Requirements: ESSENTIAL CRITERIA list. Section Qualifications: DESIRABLE CRITERIA list. Section Benefits: EOS BENEFITS list. Section Schedule: mention rotational shifts to support 24/7/365 operations and up to 10% travel domestically. We might also include Physical Requirements? Not in given headings list; but we could include under Requirements or maybe as a separate section like "Physical Requirements". However headings list didn't include Physical Requirements; but we could still include if we think it's substantive. The instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not exhaustive. So we can add other headings if needed, but better to stick to those. Physical requirements could be placed under Requirements or maybe as a separate section "Physical Requirements". Since not in examples but allowed, we could add a section. However to keep to few substantive sections, we could incorporate physical requirements into Requirements (maybe as a sub-list). But the instruction: Prefer a few substantive sections over many thin ones. So maybe we incorporate physical requirements into Requirements as part of essential criteria? But they are separate. Could add a section "Physical Requirements". That's okay. But we need to avoid too many sections. Let's count: About the role, Responsibilities, Requirements, Qualifications, Benefits, Schedule, Physical Requirements = 7 sections. Might be okay. Alternatively we could merge Physical Requirements into Requirements. Let's do that: Requirements section includes essential criteria and physical requirements. That keeps sections fewer. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Schedule. Now we need to ensure we don't include any boilerplate like EEO etc. Let's extract text. OUR COMPANY: "OUR COMPANY: EOS IT Solutions is a Global Technology and Logistics company, providing Collaboration and Business IT Support services to some of the world’s largest industry leaders, delivering forward-thinking solutions based on multi-domain architecture. Customer satisfaction and commitment to superior quality of service are our top business priorities, along with investing in and supporting our partners and employees. We are a true International IT provider and are proud to deliver our services through global simplicity with trusted transparency." WHAT YOU WILL DO: "We are seeking a highly skilled and hands-on Data Center Network Operations Lead to oversee and support hardware repair and troubleshooting operations of fiber optic deployment, splicing, testing, and maintenance activities across large-scale and mission-critical environments. . This role requires deep technical expertise in diagnosing and resolving hardware and network issues, executing repairs, and leading a team of technicians in delivering high-quality, SLA-driven support. The ideal candidate will be proficient in using Command Line Interfaces (CLI) for diagnostics, managing escalations, and ensuring the consistent delivery of network services across a range of server, storage, and network hardware platforms. This position involves rotational shifts to support 24/7/365 operations. This role may require up to 10% travel domestically" Note there is a double period after environments. We'll clean. KEY RESPONSIBILITIES: list of bullet points. We'll extract each sentence as bullet. Let's list them: - People Management Experience leading or coordinating field-based technical teams in fast-paced operational environments. - Ability to monitor productivity, manage workloads, and drive teams toward defined deliverables and operational targets. - Maintain and update documentation for incident resolution, root cause analysis, and repair procedures. - Manage ticket queues and ensure SLA adherence through effective prioritization and escalation. - Provide technical leadership and mentorship to junior technicians, ensuring adherence to best practices and safety protocols. - Collaborate with cross-functional teams to support infrastructure upgrades, migrations, and maintenance windows. - Ensure compliance with MOPs and CMOPs, and contribute to their development and continuous improvement. - Provide operational continuity and leadership coverage in the absence of the Site Supervisor. - Lead and coordinate teams of technicians on a day-to-day basis. Assign workloads, oversee daily activities, and ensure all field personnel remain aligned with project priorities and productivity expectations. - Closely monitor technician output and performance against defined daily and weekly targets. - Ensure all team members are actively engaged, productive, and operating in compliance with safety and quality standards. - Provide hands-on technical guidance, mentorship, and support to field personnel where required. - Escalate performance concerns, operational risks, or resource issues to the Site Supervisor in a timely manner. - Promote a culture of accountability, professionalism, teamwork, and operational excellence across all site activities. - Technical Experience & Oversight Lead operations across server, storage, and network hardware platforms, ensuring timely and effective resolution of hardware failures. - Perform advanced diagnostics using CLI tools (e.g., Cisco IOS, NX-OS, Linux shell) to identify and resolve system and network issues. - Oversee physical hardware repair, including component-level replacements (e.g., drives, memory, NICs, PSUs, fans, motherboards). - Troubleshoot Layer 1–3 network issues, including port failures, fiber optic cabling, link flaps, and misconfigurations. - Provide technical support and guidance for fiber splicing activities, including single-mode, multi-mode, and ribbon fiber applications. - Support testing and validation activities using OTDR, OLTS, power meters, and visual fault locators. Assist in the review and interpretation of OTDR traces, loss budgets, and certification results. - Support troubleshooting and resolution of fiber infrastructure issues and network faults. Note some bullets have multiple sentences; we can keep as one

  with the sentences. ESSENTIAL CRITERIA: - Associate degree or higher in a technical discipline or equivalent hands-on experience in data center operations or IT support. - 5+ years of experience in IT support, hardware diagnostics, and repair in enterprise environments. - 2+ years of people management, supervisory, team lead, mentoring, or equivalent experience demonstrating increasing responsibility. (Required) - Strong proficiency with CLI-based tools and environments (e.g., Cisco CLI, Linux/Unix shell, iDRAC, iLO). - Demonstrated experience in troubleshooting and repairing fiber, server, storage, and network hardware. - Familiarity with network protocols and tools (e.g., ping, traceroute, netstat, SNMP, syslog). - Excellent problem-solving skills and ability to work under pressure in high-availability environments. - Strong communication and leadership skills with a customer-focused mindset. - Valid driver’s license and ability to travel between data center sites as needed. DESIRABLE CRITERIA: - Experience managing a technical support team in a multi-site environment. (Preferred) - Industry certifications such as CompTIA Server+, Cisco CCNA, Dell EMC, or equivalent vendor-specific credentials. - Experience with ticketing systems (e.g., ServiceNow, Remedy) and asset management platforms. - Familiarity with scripting for automation (e.g., Bash, Python) is a plus. - Experience working in a 24/7 operational environment with on-call responsibilities. PHYSICAL REQUIREMENTS: - Ability to frequently exert force equivalent to lifting up to approximately 50 pounds and occasionally up to 100 pounds. - Clarity of vision at 20 inches or less and more than 20 inches, and ability to adjust focus. - Three-dimensional vision, ability to judge distances and spatial relationships. - Ability to identify colors and give and receive information through speaking and listening skills. - Regular requirements to sit, use hands and fingers, handle objects, tools, or controls; and reach with hands and arms. - Frequent need to stand and walk; occasional need to climb, balance, stoop, kneel, crouch, or bend. EOS BENEFITS: - Health, Vision, and Dental Insurance starting the 1st of the month after your start date. - Meals, snacks, drinks, and desserts provided - 10 Days of Paid Time Off (PTO) annually - 12 Paid Holidays - 6 Sick Days (available after 90 days of employment) - 401(k) Retirement Plan with a $2,500 company match (available after 90 days of employment) Schedule note: rotational shifts to support 24/7/365 operations; up to 10% travel domestically. Now craft HTML. We'll start with maybe not needed; just output headings and content. We'll use

  About the role

  then