In my extensive career, I have accumulated expertise in designing and maintaining complex, high-capacity, highly available platforms. Most recently, my teammates and I managed a WebRTC platform that logged millions of call minutes daily of video conferencing, broadcasts, and media archives. Many environments I have worked in have required rigorous adherence to SOC2, HIPAA, SOX, GDPR, and CFIUS. • Extensive experience crafting high-volume, high-availability solutions in the AWS ecosystems leveraging EC2, EC2 Load Balancing, RDS, ElastiCache, S3, CloudFront, Route53, VPC, VPC Peering, Transit Gateway, Lambda, EKS, MSK, and others. • Managed AWS EKS clusters, deployed applications with ArgoCD, and managed resources with the AWS upbound provider library (Terraform under the hood). Wrote Helm charts and various tools in Bash and Python to interface with AWS and k8s APIs. • Managed AWS resources with Terraform, Ansible, and, as mentioned above, by directly calling APIs. • Managed server configurations with Chef, SaltStack, and numerous code-complete internal tools (at Yahoo!, Danger, and Microsoft as examples). • Critical incident management, blameless post-mortems, and creating and publishing customer-facing and internal RFOs • An emphasis on observability in all environments (using tools like Prometheus, Grafana, or Nagios).I have worked with platforms where blameless post-mortems were a key part of gaining learnings from each incident and applying that knowledge to mitigate or prevent future incidents. I have found that the key indicator of a successful, healthy incident management paradigm acknowledges that the response, communication, post-mortem, and corrective actions are transparent and a collaborative effort.