Director, Cloud Infrastructure

At Sanity.io , we’re building the future of AI-powered Content Operations. Our AI Content Operating System gives teams the freedom to model, create, and automate content the way their business works, accelerating digital development and supercharging content operations efficiency. Companies like SKIMS , Figma , Riot Games , Anthropic , COMPLEX , Nordstrom , and Morningbrew are using Sanity to power and automate their content operations. Sanity's infrastructure is entering a new stage. The next layer is clearer ownership, stronger platform foundations, better operational discipline, and an architecture that can carry the company through the next few stages of growth. We're looking for a Director of Cloud Infrastructure to lead that work. This person will own the platform foundations Sanity engineers build on every day: cloud infrastructure, Kubernetes, networking, routing, observability, CI/CD, deployment paths, incident response, and the standards that make production ownership work across product teams. The scale is real. Content Lake alone handles around 75,000 requests a second, about 4.5m requests a minute. Sanity also runs critical paths across CDN, edge, gateway, caching, object storage, and GCP infrastructure. Some of the work is already in motion: moving Varnish and Mead onto Fastly, tightening observability, finishing our developer on-call rollout, and making production readiness a normal part of shipping. This is a leadership role for someone who can still go deep technically. You should be able to spar with strong infrastructure engineers, make hard architectural calls, and build the operating model around them: what Platform owns centrally, what SRE enables through teams, and how product teams deploy and run their services with confidence. What you will do Set the infrastructure strategy for Sanity's next stage of scale, with a clear roadmap across cloud infrastructure, reliability, deployment, observability, security, cost, and developer experience. Lead the teams responsible for the shared foundations behind Sanity's engineering velocity: GCP projects and clusters, Kubernetes, networking, service discovery, routing, gateways, CI/CD, infrastructure as code, and observability. Draw a clean line between Platform and SRE. Platform should own the shared foundations. SRE should help product teams run services well, with strong tooling, standards, and incident support. Raise the reliability bar across Sanity's production systems, including dashboards, alert severity, paging standards, service ownership, on-call readiness, and incident response. Make deployment boring in the best way: clear golden paths, production readiness checks, safe rollouts, useful automation, and fewer places engineers need to look before they can ship. Partner with Product, Engineering, Security, Support, Sales, and Customer Success on the infrastructure work that matters to customers: uptime, latency, scale, compliance, trust, and cost. Own cloud cost discipline without slowing the business down. You will need to understand where the money goes, make tradeoffs visible, and help teams build with cost in mind. Shape Sanity's longer-term architecture for multi-region scale, disaster recovery, data residency, and trust requirements like SOC 2, ISO 27001, PCI, HIPAA, or similar customer expectations. Hire, coach, and stretch infrastructure leaders and engineers. The team needs direction, high standards, and someone who can make strong technical people better. About you You have led Infrastructure, Platform, SRE, Cloud, or Developer Platform teams in a scaling SaaS, cloud, infrastructure, API, data, or developer-tools company. You have operated systems with high request volume, multi-region production, strict uptime expectations, large cloud bills, customer-facing incidents, and trust requirements that made engineering quality visible. You have built or run production platforms with Kubernetes, GCP or AWS, Terraform or similar infrastructure as code, service discovery, networking, API gateways, CDNs, observability, CI/CD, and incident response. You are technically deep enough to debate architecture with senior infrastructure engineers and practical enough to make the call when the perfect answer is wasting time. You know how to split central platform ownership from product-team service ownership without creating a ticket queue that everyone resents. You improve on-call and reliability by building systems, standards, and feedback loops that make production healthier over time. You can turn messy infrastructure work into a strategy people can follow, then keep pushing until the work ships. You communicate clearly with executives, product leaders, engineers, and customer-facing teams. You can explain tradeoffs without sanding off the technical truth. You have managed managers or senior technical leads, and you know when to coach, when to set the bar, and when to get directly involved. You are based in Europe or North America, with str