Network Engineer, Capacity and Efficiency
Network Engineer role at Anthropic, focusing on capacity and efficiency, utilizing Python and AWS technologies to optimize network performance and cost.
About Anthropic
Anthropic’s mission is to create reliable, interpretable, and steerable AI systems. We want AI to be safe and beneficial for our users and for society as a whole. Our team is a quickly growing group of committed researchers, engineers, policy experts, and business leaders working together to build beneficial AI systems.
About the team
The Capacity & Efficiency team sits inside Anthropic’s Compute organization and owns the cost, utilization, and attribution story for non-accelerator infrastructure — the network, compute, and storage backbone that moves petabytes between training clusters, inference fleets, and object storage across clouds and regions. The scale is real, the spend is large, and the efficiency levers are still mostly unpulled.
We work alongside the Systems Networking team (who build and operate the fabric) and the Observability team. This role lives at the intersection: you’ll use deep networking knowledge and rigorous measurement to figure out where and how bandwidth, latency, and dollars are being used, find optimization opportunities and land them.
About the role
We’re looking for a network engineer who thinks in metrics first. You understand spine-leaf fabrics, BGP, SDN overlays, and cloud interconnect products well enough to build them. You will instrument them, model their cost-per-bit, and squeeze out the inefficiency, while ensuring we can move the bits to the right places in the most efficient manner. You’ll own the observability and efficiency surface for Anthropic’s network: building intelligence using telemetry, to understanding how workloads use the network, to cost attribution that tells a research team exactly what their checkpoint sync is costing.
This is a hands-on IC role. You’ll write code (Python, Go), build dashboards, model capacity, and work with networking teams to help meet the needs of the workload owners. You’ll also influence architecture: when the data says a traffic pattern is pathological, you’ll be in the room root causing it and fixing it. You will be working across multiple areas: network telemetry and observability, and cost modeling and attribution. We expect you to be strong in at least two and willing to grow into the third. If you're a telemetry-first engineer who's never built a chargeback model, or a traffic engineer who hasn't shipped eBPF probes, apply anyway and tell us which axis you want to grow on.
What you’ll do
Posted June 5, 2026