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.
Linked-in
Google