Oliver Gould
Co-Founder & CTO at Buoyant, Inc
San Francisco, California, United States
Summary
🤩
Rockstar🎓
Top SchoolOliver Gould is a seasoned software leader and Co-Founder & CTO based in San Francisco with 13 years of experience building production-grade distributed systems and observability tooling. As creator of Linkerd and longtime Buoyant CTO, he blends hands-on Rust and Scala development with product and release leadership for a CNCF-hosted service mesh. His career includes senior roles at Twitter and Yahoo!, where he led traffic and observability efforts and helped mature operations and large-scale infrastructure. An active open-source contributor, he has made deep backend contributions to projects like linkerd2-proxy, tower, h2, kube-rs and finagle—often focusing on reliability, performance, and API ergonomics. He brings a pragmatic systems-thinking approach, evidenced by low-level work such as DNS resolver improvements in Rust and TLS/metrics hardening in proxy transports. Comfortable toggling between code and strategy, he’s known for shipping resilient infrastructure that keeps cloud-native services observable and secure.
13 years of coding experience
8 years of employment as a software developer
Bachelor of Science (B.S.) Computer Science, Bachelor of Science (B.S.) Computer Science at Stevens Institute of Technology
Stackoverflow
101reputation
4kreached
4answers
0questions
Github Skills (56)
asynchronous10
service-mesh10
kubernetes10
tower10
client-library10
middleware10
tls1210
back-end-development10
apidoc10
async10
dns-resolver10
http10
finagle10
distributed-systems10
load-balancing10
Programming languages (19)
Github contributions (5)
linkerd/linkerd2-proxy
Dec 2017 - Jan 2023
A purpose-built proxy for the Linkerd service mesh. Written in Rust.
Role in this project:
Back-end Developer
Back-end DeveloperContributions:1573 reviews, 1243 commits, 2921 PRs in 5 years 2 months
Contributions summary:Oliver focused on back-end development tasks, including refactoring code related to service profiles, improving error handling by introducing specific types and labels, and refining the overall architecture. Contributions also involved the implementation of a new gRPC route filter to support the Gateway API and the refactoring of the proxy's transport. The code changes also indicate a focus on ensuring the robustness of the proxy by addressing TLS-related issues and enhancing various metrics, including improving logging and debugging capabilities.
meshproxyrustpurposekubernetes
linkerd/linkerd
Jan 2016 - Jul 2020
Old repo for Linkerd 1.x. See the linkerd2 repo for Linkerd 2.x.
Role in this project:Back-end & DevOps Engineer
Back-end & DevOps EngineerContributions:6 releases, 3 reviews, 498 commits in 4 years 6 months
Contributions summary:Oliver primarily contributed to the core functionality and operational aspects of the Linkerd project. Their work included bumping version numbers and modifying configuration files, indicating a focus on build and release engineering. They also addressed runtime errors in the Kubernetes namer configuration and added code for managing weights in the fs namer.
2-xkuberneteslinkerdservice-discoverylinkerd2
Find and Hire Top DevelopersWe’ve analyzed the programming source code of over 60 million software developers on GitHub and scored them by 50,000 skills. Sign-up on Prog,AI to search for software developers.