Software Engineer, Networking

Responsibilities

• Own network fleet health end to end: define realtime monitoring requirements, build alerting lifecycle, and ship dashboards for network state across all sites.
• Build active debugging tooling including link diagnostics, remote command execution across the fleet, and repair visualization.
• Turn repair into a pipeline: build automation from detection through parts management, return to service, ticket integration, repair lifecycle pipelines, transceiver and optics tracking.
• Own network qualification and validation: build frameworks that gate new sites and hardware into production; define what a healthy network looks like.
• Own end-to-end reliability, scalability, and operation of the network at-scale through aggressive automation, tooling, and incident discipline.

Requirements

• Treat toil as a bug and build tools to eliminate manual work (e.g., instead of manual SSH and commands).
• Think in systems: understand how faults (transceiver, route, power) propagate and build tooling to distinguish them.
• Move toward ambiguity, build the map, and explain it to others.
• Learn at a steep slope and reach competence in unfamiliar domains quickly.
• Comfortable carrying a pager, running incidents, writing postmortems, and fixing systemic causes.
• Fluent with AI tooling: LLM APIs, MCP servers, agentic frameworks; drive Claude Code, Cursor, or similar daily.
• Shipped production network tooling or automation that other teams depend on; comfortable in any language using AI coding tools.
• Developed automation tools in Go and Python.
• Experienced in link diagnostics, optical networks, and network monitoring (gNMI, gRPC, NETCONF, SONiC).

Nice-to-Haves

• RMA and repair lifecycle automation.
• Large-scale datacenter fabric (BGP, ECMP, spine-leaf).
• Out-of-band network management.