My team focuses on writing software that provides observability into Slack performance, builds context quickly during incidents, and generates signal for how to quickly debug and solve issues.My main focus has been an SLO-adjacent project using a custom build of the OpenTelemetry collector project. The project consumes billions of envoy logs per day from a Kafka topic and generates live reliability numbers with only minutes of latency, broken down by feature and subfeature of Slack.

I work on a small distributed team that supports the rest of engineering by developing tools, debugging production systems, removing friction, and otherwise improving visibility and usability of the overall platform at Eaze.I led a rework of our network architecture built on AWS Transit Gateway and AWS Client VPN that vastly improved engineer access while also providing better security controls. As part of this work, I helped identify and eliminate a number of gaps in network security and data protection.I'm also in the middle of improvements to tracking, monitoring, and managing the lifecycle of our development clusters using a mix of DynamoDB, tooling in bash and Rust, and AWS Lambdas built on TypeScript. This work is part of an effort to improve visibility into the system and reducing costs.Some of the other technologies I frequently use and interact with include Terraform, Ansible, MSSQL, Cloudflare, and a number of AWS services including EC2, VPC, S3, RDS, Redshift, CloudWatch, and Lambda.

I worked on our platform and performed a variety of SRE-adjacent functions for five years at Simple. I was part of a small team that primarily wrote software in Ruby, Python, and Go to provide a solid experience for customers and other engineers. I have written production code in all three of those languages as well as Clojure.We completed a large infrastructure migration to Amazon VPC that introduced orchestration using an in-house Python interface to CloudFormation (similar to Amazon CDK), static AMIs baked using Packer, and a variety of automation around deploys. Part of this work included a full rewrite of our deployment software in Go to reduce deploy times from 30+ minutes to a matter of seconds with increased reliability. I was key to responding to new business, security, and engineering needs by adding new features to the platform and made it a point to be accessible, responsive, and empathetic in my work.I also worked on our monitoring and on-call systems, based on Sensu and Pagerduty. I spent a lot of time thinking about how to make the experience of using our platform better and believe I achieved that across logging, monitoring, deployments, and other domains. Overall, I learned tons in this position and think I was an effective member of a great team.

This was an internship-of-sorts that introduced me to operations, SRE, and distributed systems problems. I worked on a distributed consultant team focused on automation and provisioning infrastructure primarily using Ruby and Chef. I wrote a few Chef cookbooks and helped deploy them for customers, including cookbooks for Jenkins and Sensu.I helped transition customer infrastructure to a new Jenkins cluster fronted by nginx that improved security and maintainability.