Software Engineer, Networking

What you need

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. https://jobs.ashbyhq.com/fluidstack/05c2e69c-42f9-4fcb-9cf0-a467aaf98f1c

You treat toil as a bug. If diagnosing a link failure requires SSHing into boxes and running commands by hand, you build the tool that does it for you.
You think in systems. You understand how a transceiver fault, a misconfigured route, and a power event each propagate differently — and you build tooling that can tell them apart.
You move toward ambiguity, not away from it. You walk into the fog, build the map, and explain it to everyone else.
You learn at a steep slope. You reach real competence in an unfamiliar domain fast. We value this over existing expertise.
You carry a pager without flinching. You run the incident, write the postmortem, fix the systemic cause, and move on.
You're fluent with AI tooling. LLM APIs, MCP servers, and agentic frameworks, and you drive Claude Code, Cursor, or similar every day.

You treat toil as a bug. If diagnosing a link failure requires SSHing into boxes and running commands by hand, you build the tool that does it for you.
You think in systems. You understand how a transceiver fault, a misconfigured route, and a power event each propagate differently — and you build tooling that can tell them apart.
You move toward ambiguity, not away from it. You walk into the fog, build the map, and explain it to everyone else.
You learn at a steep slope. You reach real competence in an unfamiliar domain fast. We value this over existing expertise.
You carry a pager without flinching. You run the incident, write the postmortem, fix the systemic cause, and move on.
You're fluent with AI tooling. LLM APIs, MCP servers, and agentic frameworks, and you drive Claude Code, Cursor, or similar every day.