Network Operations

We need to output only HTML fragment, with sections for headings where content exists. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections that have real specific content. The posting includes: Position description (some prose), Required Experience, Technical Skills, Communication and Stakeholder Engagement, Federal Knowledge, Responsibilities (with subparts), About Valiant Solutions, Benefits Snapshot, Salary range (Pay), Remote Work Policy (maybe schedule? Not exactly schedule but remote work details). Also there is mention of work hours: "The engineer opens the operational day at 7:00 AM Eastern", "Work the East Coast shift, typically 7:00 AM to 3:30 PM Eastern". That's schedule info. So we can include Schedule section. We need to avoid repeating job title as heading. No Job ID. Remove boilerplate: EEO, legal, etc. Also remove application instructions like "apply now", "apply online today". Also remove duplicated lines. We need to preserve all substantive info. Let's extract content. We'll create sections: - About the role: maybe a brief description of role? The posting starts: "Position Description Valiant Solutions is seeking a Network Operations to join our rapidly growing and innovative cybersecurity team! Valiant Solutions is seeking a Network Operations engineer based in Silver Spring, MD to deliver Tier 1 through Tier 3 network operations for the headquarters campus and the East Coast footprint of a federal enterprise network." That's about role. We'll put that in

. - Responsibilities: we have a detailed list under "Responsibilities" with subheadings Daily Network Operations, Carrier Coordination, Headquarters On-Premise Support. We'll output as

• items, maybe grouping. - Requirements: maybe "Required Experience" and education etc. Could be under Requirements. - Qualifications: maybe preferred certifications? Could be Qualifications. - Skills: Technical Skills, Communication and Stakeholder Engagement, Federal Knowledge. - Benefits: Benefits Snapshot. - Pay: Salary range. - Schedule: work hours and shift, remote work policy maybe. We must not create sections with filler like "commensurate with experience". We have actual content. We need to ensure we don't include boilerplate like EEO, Physical Demands, Authorization to Share Resume, etc. Remove those. Also remove "Remote Work Policy" details? It's substantive about remote work expectations; could be part of Schedule or maybe separate but we only have allowed headings; we could put remote work details under Schedule or Benefits? Probably Schedule includes remote work expectations. We'll include schedule info: typical shift 7:00 AM to 3:30 PM Eastern, on-call rotation, remote work allowed with policy details. We must not repeat job title as heading. So no

  Network Operations engineer. Now produce HTML fragment. Let's craft:

  About the role

  Valiant Solutions is seeking a Network Operations engineer based in Silver Spring, MD to deliver Tier 1 through Tier 3 network operations for the headquarters campus and the East Coast footprint of a federal enterprise network. The engineer opens the operational day at 7:00 AM Eastern, monitors LAN, WAN, and carrier MPLS circuit health across roughly 50 sites nationwide, and provides the on‑premise hands that headquarters infrastructure requires. The headquarters campus supports approximately 700 staff and serves as the East Coast anchor of a consolidated Network Operations Center. Availability standards are strict: 99.99 percent core network uptime, a 15‑minute response to Priority 1 incidents, and service restored within 4 hours. Named one of the Best Places to Work in the Washington DC area for 12 consecutive years, Valiant is proud of our employee‑centric culture and commitment to excellence.

  Responsibilities

  • Daily Network Operations – Provide Tier 1 through Tier 3 support, from triage, connectivity checks, and port resets through routing protocol troubleshooting, VLAN changes, and firewall rule analysis. Work the East Coast shift, typically 7:00 AM to 3:30 PM Eastern, so that the enterprise operational window opens on time. Participate in the 24×7×365 on‑call rotation and respond to Priority 1 incidents within 15 minutes. Prepare Methods of Procedure for every configuration change, including rollback plans and risk assessments, and carry them through the Change Control Board. Maintain topology diagrams, asset inventories, and knowledge base articles that shorten mean time to resolution. Record all activity in ServiceNow ITSM and report ticket status, overage tickets, and service level performance monthly.
  • Carrier Coordination – Monitor customer edge routers and the circuits they terminate, tracking latency, jitter, packet loss, and availability across the nationwide site footprint. Open and manage trouble tickets with the MPLS carrier and transport providers, escalate through vendor management chains, and schedule intrusive testing windows. Own the overall incident and internal communications during a circuit outage, providing hourly status updates to government stakeholders until service is restored. Apply Quality of Service markings and policy on customer edge routers so that mission data and VoIP traffic receive priority.
  • Headquarters On‑Premise Support – Perform on‑premise hardware work at the headquarters campus, including rack and stack, structured cabling, and hardware replacement with RMA processing. Serve as the on‑site technical presence when remote access is unavailable or when a task cannot be delegated to smart hands. Support access layer readiness for 802.1X enforcement as the Network Access Control rollout reaches each switch. Support failover testing of internet, DMZ, and cloud access paths in coordination with the security team. Travel to data center and regional sites as directed for physical infrastructure work.

  Requirements

  • 4 years of experience in network operations, data center management, or systems administration.
  • Bachelor’s degree in Information Technology, Network Engineering, Computer Science, or a related field. In lieu of the Bachelor’s degree, an Associate’s degree (or a high school diploma or GED) plus two additional years of relevant experience, for 6 years in total.
  • Experience operating against defined service level agreements in a monitored ticketing environment.

  Skills

  • Technical Skills – Cisco routing and switching operations across Catalyst and Nexus platforms, including VLAN changes, port configuration, and interface troubleshooting. OSPF and BGP troubleshooting, with awareness that the carrier runs EIGRP on its managed devices. Network monitoring and alarm triage using SolarWinds or an equivalent enterprise monitoring platform. Incident, problem, and change management in ServiceNow ITSM. Firewall rule analysis at the Tier 2 level on Cisco Firepower Threat Defense. Physical infrastructure work, including rack and stack, fiber and copper structured cabling, labeling, and hardware RMA processing. Reading and maintaining topology diagrams and asset inventories.
  • Communication and Stakeholder Engagement – Written and verbal communication skills sufficient to explain network and security concepts to both engineers and non‑technical government stakeholders. Ability to brief senior government leadership, including the Contracting Officer's Representative and Technical Lead, on incident root cause, risk, and remediation. Clear technical writing for Methods of Procedure, topology diagrams, standard operating procedures, and monthly status report inputs. Ability to work as a contractor employee in a non‑personal services environment, identifying as contractor staff in all meetings, correspondence, and system records.
  • Federal Knowledge – Working knowledge of federal network security direction, including Zero Trust Architecture (NIST SP 800‑207), Trusted Internet Connection (TIC) 3.0 reference architectures, and the IPv6 mandate under OMB M‑21‑07. Familiarity with NIST SP 800‑53 Rev. 5 security and privacy controls as they apply to network and boundary protection. Understanding of HSPD‑12 identity credentialing and its enforcement in network access decisions. Awareness of Section 508 accessibility requirements (WCAG 2.0 AA) as they apply to contract deliverables. Experience operating inside a federal change control process, with government‑approved documentation and deliverable acceptance criteria. Willingness to complete required customer training, including annual cybersecurity awareness, records management, privacy, safety, and harassment prevention training.

  Benefits

  • Valiant pays 99 % of the Medical, Dental, and Vision Coverage for Full‑time Employees
  • Valiant contributes 25 % towards Health Coverage for Family and Dependents
  • 100 % Paid Short Term Disability and Life Insurance Policy for Full‑time Employees
  • 100 % Paid Certifications
  • 401K Matching up to 4 %
  • Paid Time Off
  • Paid Federal Holidays
  • Wellness & Fitness Program
  • Valiant University – Online Education and Training Portal
  • FSA programs for: Medical Costs, Dependent Care, Transit, and Parking
  • Referral Bonuses

  Pay

  The salary range for this position is expected to be in the $90,500‑$95,750 range. The salary is a general guideline and not a guarantee of compensation.

  Schedule

  The engineer opens the operational day at 7:00 AM Eastern and works the East Coast shift, typically 7:00 AM to 3:30 PM Eastern. The role includes participation in a 24×7×365 on‑call rotation with a 15‑minute response to Priority 1 incidents. Remote work is allowed (partial remote) subject to Valiant’s Remote Work Policy, which requires a quiet, distraction‑free workspace, adequate internet, full attention during working hours, alignment of schedule with coworkers and clients, cameras encouraged for virtual conferences, and disclosure of any outside employment.

  We need to ensure we didn't include any boilerplate like EEO, Physical Demands, Authorization to Share Resume, etc. We removed those. Check for any repeated content: we included the shift description in Responsibilities and also in Schedule; that's okay as it's substantive but could be considered duplication. However the instruction says remove duplicated lines. We might want to avoid duplicating the same sentence. We could keep shift details only in Schedule and not repeat in Responsibilities. But the Responsibilities section originally includes that shift detail; we could keep it there but maybe it's okay. To be safe, we could remove the shift sentence from Responsibilities to avoid duplication. Let's adjust Responsibilities bullet: remove "Work the East Coast shift, typically 7:00 AM to 3:30 PM Eastern, so that the enterprise operational window opens on time." Keep that in Schedule only. Similarly, the on-call rotation and 15-minute response appears in Responsibilities and also Schedule; we could keep in Responsibilities and maybe not duplicate in Schedule. But Schedule also mentions on-call rotation. Might be okay but to avoid duplication we could keep on-call in Responsibilities and not repeat in Schedule. However Schedule also needs to mention shift and remote work policy. Let's keep shift and remote work in Schedule, and keep on-call and 15-min response in Responsibilities. Let's edit. Responsibilities bullet for Daily Network Operations: remove shift sentence. Keep rest. Schedule paragraph: mention shift, on-call rotation? We could mention on-call rotation there as part of schedule but we already have it in Responsibilities. Might be okay to mention again but risk duplication. I'd rather keep on-call in Responsibilities only, and Schedule just about