Storage infrastructure

Networking

Member of core networking team, which is responsible for the data plane and much of the control plane of Lyft’s server side architecture. Worked on multiple aspects of Lyft’s deployment of Envoy, including primary development of an Envoy xDS configuration server; improving development/production parity for engineers; and oncall responsibilities. Contributed to mainline OSS Envoy as well as Lyft’s core Go libraries and toolchains.

Core Libraries

Responsible for overall health of Facebook’s core C++ libraries, including folly, fbthrift, and other internal components, with an emphasis on both performance and developer friendliness. Free reign to analyze their usage across the codebase, identifying and fixing problems with or gaps in available abstractions. Additionally, building out tooling to enable Facebook engineers to easily leverage the dynamic tracing abilities provided by the new Linux eBPF framework.

Asynchronous C++ APIs

Co-author of folly::futures and wangle (see Open Source below). Designed, implemented, promulgated, and supported these libraries. folly::futures is now the default mechanism for writing asynchronous C++ at Facebook, and wangle components are critical to building concurrent and asynchronous client/server components, including in the open source projects hhvm, fbthrift, and proxygen.

Messages Infrastructure

Designed, implemented, and deployed the C++ backend for a new caching service for Facebook Messages, tailored to the balanced read/write ratio of messaging workloads, reducing both message read latency and load on the backing persistent message store.

Containerized Deployment

Collaborated on support for service identity and authentication to Facebook’s containerized deployment infrastructure (think Amazon ECS). Refactored legacy components to bring them up to speed with modern C++. Contributed to upgrade from cgroups to cgroups2, towards a future of effective resource control.