Originally a member of a 2-person team, I was responsible for all things Cloud Infrastructure, including CI/CD, infra for the Skydio Cloud product, developer/build tooling, analytics, and more. As the company grew, I specialized more on the Skydio Cloud product infrastructure, maintaining and scaling our Kubernetes clusters, S3 storage capabilities (including cost optimizations), networking, and livestreaming infrastructure.I was the lead architect/sole engineer on a handful of important projects, including custom VPN infrastructure for a security-sensitive client, the migration to infra-as-code for our deployment pipelines, and even a couple that touched the entire software stack, from the drone to the cloud.As one of the senior members of a growing team, I was also responsible for the onboarding and education of a number of new team members, helping improve documentation and processes to enable broader self-service updates to our cloud infrastructure.

As a Staff Software Engineer, I was largely responsible for all things infrastructure at Outlier. This included not only the underlying AWS/GCP resources, the Kubernetes layer, and some small amounts of database management; but also a complete rewrite of our workload management tooling to allow it to be extended beyond just the data analysis pipeline. This allowed us to greatly increase our throughput in several other areas that required asynchronous job management, while minimizing our spend on the underlying compute resources.I was frequently consulted for architecture across the entire stack, to help maintain a unified approach across all teams, and to prevent any issues arising from siloed development across geographically disparate teams. In addition, I spent a portion of my time maintaining legacy parts of the stack that were not being actively developed.

In this role, I was responsible for leading or implementing a large number of technical changes to the stack. Primarily focusing on the backend, I worked in Ruby/NodeJS on Kubernetes in both AWS and GCP environments. One of my major projects during this time was the migration of all data from our RethinkDB clusters into Postgres, including the migration of several tables with many billions of documents without introducing any customer-facing downtime. This required learning about and implementing a partition management strategy for Postgres, in addition to writing highly-performant migration tools in Go, all while ensuring that a system approaching the limits of its capacity continued to function in a useable way.I focused heavily on infrastructure and build/deploy tooling, backend optimization, dynamic resourcing for workloads, and workload management on Kubernetes.

As the Head of Infrastructure at AltSchool, I was responsible for both the infrastructure (AWS with Kubernetes), as well as the roadmap to ensure that AltSchool met its long-term scaling goals. As with any scaling challenge, managing complexity was easily the hardest part. There were many competing priorities, requiring tradeoffs and careful implementations to pursue the best path forward. With only a small team, I had to accommodate the increasing scale, while also being mindful that our resources were being spent in the most efficient way possible.My other responsibilities included maintaining and upgrading our build and deployment tooling, to ensure that it stayed out of the way instead of getting in the way. Enabling peak developer velocity was always a high priority, and a clean, effective build system was a key component of that. Another important component was the ability to build and demonstrate prototypes, which required a deployment system that was flexible enough to accommodate new tools and methods.

As a Staff Engineer at AltSchool, I continued to work in very cross-functional manner, switching between Infrastructure, Product, and even DevOps-ish engineering roles. Over time, this became more focused on the Infrastructure side of things, due to my continued interest in Kubernetes, in particular. I worked closely with a small team of other engineers to enhance our deployment architecture to take better advantages of the resources available to us. Over time, we formalized and improved our testing and deployment infrastructure, making a more holistic shift towards a proper CI/CD environment.As I transitioned my mix of responsibilities more towards the Infrastructure side of things, I also began assume more leadership responsibilities, including making important decisions on our scaling strategy from the Infrastructure side of things.I built and maintained the tooling we use to provision new environments for new customers, recently shepherding it through a second iteration to take better advantage of tools available to us (Cloudformation, autoscaling, etc). Through this exercise, I learned a great many things about infrastructure on AWS in particular, allowing me to build a much more streamlined provisioning process.A key result of working in a role that has traces of both DevOps and SRE responsibilities is a strong understanding of how to implement large changes without disruption. My philosophy can be summarized with a quote: "When you do things right, people won't be sure you've done anything at all."

As a Senior Engineer at AltSchool, I began to take on some of the more gritty problems in our tech stack. These generally revolved around testing, performance, build tooling, and occasional forays into infrastructure. Taking on these tasks allowed me to build an even deeper understanding of the tools we use on a daily basis. Whether it was chasing memory leaks, profiling Javascript, or fixing flaky tests, I used each of these challenges to shape an understanding of the frameworks used across our stack. This enabled me to better guide and influence my fellow developers towards decisions that made the most sense given the capabilities we had at our disposal.During this time, I also spent a considerable amount of time working on product features, as well. Being able to work on our stack from "both sides", so to speak, has given me a breadth of knowledge of our applications that is mostly unrivaled. This breadth of knowledge across our codebases also allowed me to have valuable input on our build, deploy, and infrastructure decisions.Also during this period, I wrote and maintained a handful of internal tools used to monitor, document, and diagnose performance issues across the stack. Examples include: a simple tool to run benchmarks of api endpoints across different deployments; a plugin for our frontend testing infrastructure that collects and aggregates memory usage over time; contributions to an open-source tool for doing visual diffing (Percy.io); and a custom plugin for existing Ember build pipelines that is responsible for monitoring for new versions of the frontend and reacting accordingly (either injecting a page refresh on navigation, or simply notifying the end user that a new version is available.

Though hired on as a Frontend Engineer, my first role at AltSchool was closer to that of a Full Stack Engineer. I quickly adopted the technologies in the stack (Ember and Django), despite having no prior experience with them. During this time, I was the lead engineer on designing and building the parent-facing tuition tools. This featured a Stripe integration to enable parents to pay tuition directly in the parent-facing part of our tools. This included features such as automatic payments, split billing, and more.From this starting point, I began to branch out into more areas of both the frontend and the backend, diving deep into the frameworks and learning their intricacies to diagnose and fix performance issues, testing issues, and much more.

Full stack engineer (LAMP stack), with added responsibilities in the areas of database administration and systems administration. As part of a very small team of engineers, I helped build and maintain large portions of the website architecture, from server configuration to front-end design

Handled all analysis of machine performance for the QA department. By leveraging the raw data submitted by maintenance engineers in the field, I was able to help set the priorities (primarily) for the hardware side of the QA department. I managed the entire data analytics process, from data collection, to data storage, to reporting. By importing the data into a MySQL database, I was able to utilize the business intelligence tools (Cognos) already in use by the other departments to provide automated and custom reporting.