- Manages the Dev Spaces team, focused on the Inner Development Loop: the tight, iterative cycle of writing, building, and validating code.- Our team is designing and building a batteries-included development workspace product for Netflix engineers.- Our scope spans from the IDE, to language-agnostic dev tooling, to the local and remote development environments themselves.

- Managed the Compute Platform org, containing a pair of teams focused on different workload shapes (realtime serving workloads and Data/ML workloads).- Responsible for equipping Twitter's +3,000 engineers with an approachable, scalable, and secure compute platform (based on Kubernetes).- Built our products to work within a hybrid datacenter/public cloud model.

- Managed two teams: Infrastructure Systems Engineering and Release engineering team.- Infrastructure Systems Engineering: Provided foundational services like DBs, caches, queues, core AWS infrastructure, and the CDN.- Release Engineering: Development of InfraRed, our internal Kubernetes-based PaaS.

- Managed the Infrastructure Release Engineering team, responsible for making the path from concept to production as safe, efficient, and painless as possible.- Grew the team from just me to 6+.- Collaboratively designed and released InfraRed, our internal Kubernetes-based PaaS.- Rolled out a company-wide CI offering.

- Part of the team that scales, secures, and ensures the availability of one of the top 5 busiest sites in the world.- Maintained, operated, and improved Reddit's supporting infrastructure.- Supported and advised other service teams on building, operating, and deploying services.- Initiated and led the engineering organization's adoption of Kubernetes.- Transitioned to management as the Kubernetes adoption effort continued.

- Designed and operated systems that ingested and queried many TB of high-resolution sensor data.- Identified, diagnosed, and resolved performance and scalability issues.- Responsible for the availability and general health of the entire VM fleet on GCP.- Introduced detailed monitoring/alerting and incident response.- Introduced Continuous Integration and kickstarted a culture of testing.- Led the charge in transitioning workloads to Kubernetes.

- One of three co-founders, primarily focused on Infrastructure and Backend Engineering.- Bootstrapped and grew Pathwright from a proof of concept to a profitable, sustainable business. It's still humming along today!- Built out most of the backend in our Python/Django codebase.- Profiled, optimized, and scaled as we saw steadily increasing adoption.- In addition to my engineering responsibilities, I: recruited, jumped into sales calls, participated in roadmapping, and did lots of customer support.

- One of two engineering contributors to the replacement of a legacy mission-critical workflow management system. Finished ahead of schedule and with positive user reception.- Wrote a press-side application that checked the spectral accuracy of printed proofs.- Automated where possible.

- Incorporated with some Graphic Communications professors and colleagues in the print industry.- Handled most of the day to day operations, as well as all development of our product (ColorSentry).- Developed intelligence to suggest ways to improve printing press color accuracy, driven by analysis of spectral readings.- After graduation, we successfully navigated an exit.

- Worked in Clemson's Geographic Information Science lab part-time while a full-time student at Clemson University.- Assisted with the design of enclosures for our custom sensor nodes (TelosB motes).- Wrote tooling and support utils for the lab's computer/electrical engineers.- Wrote software that received sensor data from the field (over cell modem).- Deployed and maintained the sensor network in the field (Gumstix, cell antennas, solar panels/batteries, sensors).- Assisted in writing the method section of the resulting publication "Fine Scale Environmental sensor networks for water quality monitoring".