Architecture and Design Design cross-cutting platform solutions spanning multiple services, and record the decisions and trade-offs
Design for failure: bounded retries, backpressure, circuit breaking, honest health checks, tested failover — and contain blast radius to one tenant, region or subsystem
Plan upgrades and migrations that complete without user-facing downtime
Establish shared defaults, libraries and patterns that other engineering teams adopt
Kubernetes and Infrastructure Own the Kubernetes platform across multiple production regions — cluster architecture, upgrades, add-ons, RBAC and network policy
Develop and maintain infrastructure-as-code using Terraform, Helm and GitOps workflows (Flux, Argo)
Own the shared components everything depends on — databases, caches, message brokers, workflow engine — including upgrades, patching, replica topology, capacity and disruption budgets
Execute storage, instance class and engine version migrations with rollback plans
Reliability, Monitoring and Incident Response Lead investigation and resolution of complex production issues spanning services, infrastructure layers and technology stacks — eliminating the class of problem rather than the instance
Establish monitoring and alerting so that failures are detected before customers report them
Define service level indicators and objectives with error budgets, measured at the user-visible boundary
Keep alerting focused on user-visible symptoms rather than resource noise, and the paging tier small and trustworthy
Participate in the on-call rotation, and convert post-incident reviews into work that gets completed
Linked-in
Google