Network Engineer

• Take pre-prod handoffs from the AI Networking Squad and bring new PoPs into production — peering up, route policy, validation, and cutover
• Own and operate the backbone: BGP (eBGP/iBGP, communities, route reflection, traffic engineering), IS-IS or OSPF, MPLS, Segment Routing, and EVPN where applicable
• Manage transit and peering — Tier 1 relationships, IX sessions, prefix filtering, RPKI, route optimization
• Run capacity expansions — new ports, additional transit/transport circuits, link upgrades, optics swaps
• Troubleshoot production issues — packet captures, route analysis, transport diagnostics — and drive post-incident fixes
• Partner with the AI Networking Squad on automation: contribute to config generation, validation pipelines, network state checks, and agentic workflows

• Support architecture, scaling, and integration initiatives across the backbone
• Help roll out new services and features alongside Core Network and product engineering teams
• Contribute to improvement work: protocol tuning, observability, automation coverage, hardening

• 3–5 years of hands-on network engineering experience in a service provider, carrier, CDN, hyperscaler, or large-scale SP-style enterprise backbone
• Deep BGP — eBGP and iBGP, communities, local-pref / MED, route reflection, traffic engineering, dampening, RPKI; comfortable designing and debugging policy at scale
• IGP fluency — IS-IS or OSPF, including multi-area design and convergence behavior
• MPLS and Segment Routing — LDP, RSVP-TE, SR-MPLS / SRv6 awareness; familiarity with L3VPNs and EVPN/VXLAN
• Hands-on CLI on at least one of Juniper (Junos), Cisco (IOS-XR / NX-OS), Arista (EOS), Nokia (SR OS), or equivalent — including config, troubleshooting, and upgrades on production gear
• Transit, peering, and IX experience — how to bring up sessions, structure policy, and tune the routing table for performance and cost
• Optics and transport — knowledge of grey/coloured optics, DWDM basics, transport circuits, and how the physical layer feeds the routing layer
• Solid Linux fundamentals and a scripting language (Python preferred) — you're comfortable on the box, not just on the CLI
• AI-first mindset (required) — demonstrated experience building workflows, automations, or tools with AI (prompt engineering, AI-assisted coding, agentic frameworks). Concrete artifacts beat claims. AI adoption and tool-building is a key component of long-term performance evaluation in this role
• Strong written communication — clear runbooks, RFC-style proposals, incident write-ups, and async updates

• Network automation experience — Ansible, NAPALM, Nornir, Netbox, or similar
• Hands-on with infrastructure-as-code for network (YANG/NETCONF, gNMI, Terraform providers for network gear)
• Network validation and turn-up tooling (batfish, suzieq, custom validators)
• Out-of-band / console infrastructure (serial console servers, OpenGear, etc.)
• Experience with observability stacks for networks — streaming telemetry, Prometheus/Grafana, flow analytics
• CCIE / JNCIE / equivalent senior cert, or evidence of equivalent depth without the cert

• Production deployments land cleanly — pre-prod handoffs become live PoPs without rework
• The backbone runs hot but stable — your changes don't cause incidents, and your incident write-ups make the network better
• Peering and transit policy is tight, measurable, and improving — cost down, performance up
• You're shipping automation that the rest of the team adopts — not just running CLI
• Anyone on the squad can pick up your work because your docs, configs, and PRs explain themselves

#LI-REMOTE