Kevin Ingelman
Engineer at Sierra
San Francisco, California, United States
Summary
🤩
Rockstar🎓
Top SchoolKevin Ingelman is a seasoned engineer with 11+ years designing and operating production distributed systems, currently based in San Francisco. He led Buoyant’s cloud team and served as a super-maintainer for Linkerd, contributing substantial Go backend and DevOps work to the widely-used Linkerd service mesh and its example apps. His expertise spans Kubernetes, gRPC, GraphQL, CI/CD, container security, and observability stacks—building pipelines that include vulnerability scanning and cluster health monitoring across customer environments. Prior roles at Twitter and Microsoft show deep experience modernizing legacy platforms, reducing infrastructure cost, and delivering high-throughput backend services. Notably, he combines hands-on systems programming with practical deployment engineering—implementing features from API error handling and path stats to TLS and tracing integrations.
10 years of coding experience
19 years of employment as a software developer
BS Computer Science Economics, BS Computer Science Economics at University of Richmond
Stackoverflow
165reputation
7kreached
8answers
0questions
Github Skills (34)
service-mesh10
kubernetes10
docker10
apidoc10
sbt10
finagle10
dockers10
cicd10
scala10
go10
api10
prometheus10
kubernetes-pods10
linkerd10
grpc10
Programming languages (8)
Github contributions (5)
linkerd/linkerd-examples
May 2016 - Aug 2018
Examples of how to configure and run linkerd
Role in this project:
Backend & DevOps Engineer
Backend & DevOps EngineerContributions:44 commits, 74 PRs, 108 pushes in 2 years 3 months
Contributions summary:Kevin contributed to the development and configuration of example applications for the `linkerd` service mesh, primarily focused on Kubernetes deployments. Their work included setting up and configuring services, such as hello world examples, with both HTTP and gRPC protocols. The user also implemented a failure accrual demo project and updated the repository to use newer versions of dependencies, demonstrating expertise in both backend service development and DevOps practices. Furthermore, they prepared the repository for a move to the linkerd organization.
dockerkubernetesconfigureservice-discoverylinkerd
linkerd/linkerd
Jan 2016 - Feb 2018
Old repo for Linkerd 1.x. See the linkerd2 repo for Linkerd 2.x.
Role in this project:Backend Developer
Backend DeveloperContributions:1 release, 95 commits, 122 PRs in 2 years 1 month
Contributions summary:Kevin primarily focused on configuring and maintaining the build process of the Linkerd 1.x codebase, as seen by modifying sbt configuration files. They also made changes to project dependencies and added code for tracing and the handling of request IDs within the HTTP protocol, which suggests work on core service functionality. Furthermore, the user contributed to improvements in error handling, particularly within the Kubernetes integration, and added tooling for Zipkin tracing.
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.