> Markdown version of [/jobs/ext/3457580-head-of-infrastructure](https://www.wearedevelopers.com/jobs/ext/3457580-head-of-infrastructure). 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).

---

# Head of Infrastructure

- **Company:** General Computing
- **Location:** San Francisco, CA, United States
- **Experience:** Expert
- **Contract:** Permanent contract
- **Skills:** Data Centers, Software Debugging, Firmware, Hardware Platform Interface, InfiniBand, Application Specific Integrated Circuits, Large Language Models, Kubernetes, TensorRT
- **Published:** September 2, 2026
- **Apply:** https://www.indeed.com/viewjob?jk=c18498618c69b580

## About the Role

* 7+ years in infrastructure, SRE, or platform engineering, with at least some of it at a serious inference, ML, or HPC shop.
 * Hands-on with Kubernetes at production scale - not just deploying, but debugging the weird stuff.
 * Strong instincts for tail latency. You think about p99 and utilization as the same problem, not different ones.
 * Comfortable owning a vendor relationship where the vendor's bugs are now your production issues.
 * Track record of building observability practices that actually catch problems, not just generate dashboards.
 * Have been on-call through real incidents and can talk about what you learned.
 * Want to be the first infra hire at something early, not the tenth at something big.

NIce-to-Haves:

 * Experience operating non-NVIDIA accelerators in production - TPUs, ASICs, or alternative GPU vendors.
 * Background with model-serving stacks (vLLM, TGI, TensorRT-LLM, SGLang).
 * Network fabric experience at data-center scale (RoCE, InfiniBand).
 * Have hired and managed an infra team before.
 * Comfort at the hardware boundary - firmware, drivers, thermals - for when the roadmap takes us there.

## Description

You'll own the infrastructure layer of our inference cloud end-to-end. Today that means the control plane, the gateway in front of our ASIC fleet, and the observability stack that tells us where every millisecond goes. Over the next 6-8 months, it will grow into a heterogeneous fleet: ASICs for decode, GPUs for pre-fill, and the physical-layer ownership that comes with it., * Own the inference control plane. At the moment, it's built on configuration provided by our ASIC partner; you'll be the person who understands it deeply enough to modify, extend, and eventually replace pieces of it.

 * Own the gateway and load balancer that fronts the fleet. Model placement, request routing, and tail-latency engineering live here, driven by live utilization and per-model SLOs.
 * Own observability end-to-end. Per-request tracing from OpenRouter ingress through to the accelerator, with p50/p95/p99 dashboards, SLOs, and alerting that wakes the right person.
 * Run capacity planning against a real, distributed traffic mix across the open-weight models we serve.
 * Own the operational side of the ASIC partnership. Most weird production issues route through their engineering team until we build that expertise in-house, and you'll be our technical face in those conversations.
 * Bring up the pre-fill side of our disaggregated architecture on a second hardware platform as it comes online. Different vendor, different fabric, different kernels.
 * Build the on-call and incident response practice from zero. Hire and grow the team underneath you.