> Markdown version of [/jobs/ext/4028598-software-engineer-networking](https://www.wearedevelopers.com/jobs/ext/4028598-software-engineer-networking). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Software Engineer, Networking

- **Company:** Fluidstack Ltd
- **Location:** Seattle, WA, United States
- **Contract:** Permanent contract
- **Skills:** Software Debugging, Network Layer, Network Monitoring, Network Routers
- **Published:** October 30, 2026
- **Apply:** https://www.dice.com/job-detail/cc807a11-39ba-4615-9214-1f1c009d2b0d

## About the Role

The below is a starting point. We always make space for exceptional people, so if you don't fit this role exactly, tell us where you would.

## Description

Examples of key exciting problems the team is working on

 * Turn every network fault from a mystery into a closed ticket: link diagnostics across router-router and NIC-to-router paths, remote command execution across the fleet, and repair visualization that shows exactly what's broken and why. At this scale, debugging has to be systematic, not artisanal.
 * Build the network repair pipeline that runs itself: from automated fault detection through RMA initiation, ticket integration, transceiver lifecycle tracking, and return to service, across DC fabric, edge, and host-to-network layers. When a new site comes online every six months, manual repair doesn't keep up.
 * Build the network monitoring platform for a fleet that never stops growing: define requirements, alerting lifecycle, and health dashboards from scratch, for infrastructure spanning multiple hyperscale sites today and 10s to 100s of GWs ahead. It doesn't exist yet. We're building it.

Role Scope

 * Own network fleet health end to end. Define the realtime monitoring requirements, build the alerting lifecycle, and ship the dashboards that give every on-call engineer a true picture of network state across all sites.
 * Build active debugging tooling. Link diagnostics, remote command execution across the fleet, and repair visualization - the tools that turn a network fault from a mystery into a solvable problem, fast.
 * Turn repair into a pipeline, not a procedure. Build the automation that takes a network failure from detection through parts management and return to service. Ticket integration, repair lifecycle pipelines, transceiver and optics tracking - owned, not improvised.
 * Own network qualification and validation. Build the frameworks that gate new sites and hardware into production. You define what a healthy network looks like before it carries traffic.
 * Own end-to-end reliability, scalability, and operation of the network at-scale. Fluidstack is building one of the largest datacenter networks in the world and that can only be accomplished with aggressive automation, tooling, and incident discipline.