Network Engineer

Doublezero

Where
Remote

Posted 11 months ago· Checked live at Doublezero 2 hours ago

Stale: open 357 daysUp for more than two weeks. It may already be filled.

See how you score for this job

One sentence and your resume. We score it against what Doublezero asks for, line by line.

See my score
Is this job still open?
Yes. We checked it live on Doublezero's own hiring page 2 hours ago.
What is the job?
We’re looking for a network engineer with a true CCIE-level routing & switching background who is equally comfortable writing production code. This is not a traditional NOC role — it’s for someone who treats networks as software systems. Design and operate large-scale, high-availability, low-latency networks
What does it pay?
The posting doesn't say.
Our verdict
Stale. Up for more than two weeks. It may already be filled.

What the job is

We’re looking for a network engineer with a true CCIE-level routing & switching background who is equally comfortable writing production code. This is not a traditional NOC role — it’s for someone who treats networks as software systems.

Design and operate large-scale, high-availability, low-latency networks

Work on BGP, EVPN, MPLS, segment routing, and carrier-grade routing architectures

What you’ll do

  • Design and operate large-scale, high-availability, low-latency networks
  • Work on BGP, EVPN, MPLS, segment routing, and carrier-grade routing architectures
  • Build automation frameworks in Go and Python to manage network config, deployment, and monitoring
  • Partner with hardware, protocol, and systems engineers to optimize for latency, reliability, and scale
  • Debug real-world production network failures across physical and virtual layers

What we’re looking for

  • CCIE or equivalent hands-on routing & switching expertise
  • Strong experience in ISP / carrier / backbone network environments
  • Solid production Go + Python experience (not just scripts)
  • Deep understanding of routing protocols, convergence, and network failure modes
  • Experience treating infrastructure as code and systems as software
  • Preference for telecom / ISP / infrastructure backgrounds over HFT