<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
  <channel>
    <title>L3 Network Engineer - Claranet RSS Feed</title>
    <link>https://jobs.co.uk/job/l3-network-engineer-claranet--3e491cf7-c853-4b90-99bc-ac6bfeda6b17</link>
    <description>RSS feed for L3 Network Engineer at Claranet.</description>
    <language>en-gb</language>
    <lastBuildDate>Wed, 19 Aug 2026 19:11:28 GMT</lastBuildDate>
    <item>
      <title>L3 Network Engineer - Claranet</title>
      <link>https://jobs.co.uk/job/l3-network-engineer-claranet--3e491cf7-c853-4b90-99bc-ac6bfeda6b17</link>
      <guid>https://jobs.co.uk/job/l3-network-engineer-claranet--3e491cf7-c853-4b90-99bc-ac6bfeda6b17</guid>
      <pubDate>Tue, 18 Aug 2026 23:00:00 GMT</pubDate>
      <description>Location: Covent Garden | Salary: Negotiable | Type: Permanent | Position Summary   The Level 3 Network Operations Engineer delivers advanced operational support, configuration management, and lifecycle maintenance across the network estate for financial services clients. The role focuses on complex incident resolution, change execution, and performance optimisation for SDWAN, WAN, LAN/WLAN, VPN/SASE, and load-balancing environments, ensuring all activities meet stringent regulatory, security, and compliance standards.  Please note this role requires strong Netskope experience, involving migrations/transformations/implementations at Engineering level.    Primary Purpose   Provide expert technical leadership for diagnosing, resolving, and optimising complex network issues. Lead configuration management and compliance, support onboarding and automation initiatives, and drive continuous improvement within regulated environments.   Duties and Responsibilities    Essential Roles &amp; Responsibilities   	 Diagnose and resolve complex incidents across SDWAN, WAN, LAN/WLAN, VPN/SASE, and load-balancing platforms, ensuring compliance with financial services regulations 	 Implement network configuration changes using approved templates and security baselines...</description>
      <category>Permanent</category>
    </item>
  </channel>
</rss>