Ryan Maleki
San Francisco, California, United States
Summary
🤩
RockstarRyan Maleki is a Staff Software Engineer in San Francisco with 11 years building scalable, cloud-native systems across startups and hyperscale companies like Tesla and Amazon. He specializes in Go and Kubernetes, focusing on infrastructure, CI/CD, and automation—work that includes contributing to Karpenter (Kubernetes autoscaling) and maintaining Go error-handling libraries. His background spans hands-on platform engineering, SRE, and people leadership, having managed teams and shaped developer tooling and infrastructure at Fair.com and earlier companies. Ryan blends low-level systems debugging with system design and automation, frequently shipping production-ready improvements such as CI error checks and release bots. Notably, he pairs open-source maintenance work with pragmatic production delivery, surfacing a preference for concise, reliable tooling (his GitHub bio: "I tend to want to Go" hints at his Go-first approach).
11 years of coding experience
Github Skills (13)
golang10
release-management10
error-handling10
github-ci10
programming-language10
bash10
go10
aws10
githubaction-workflow10
cicd10
documentation10
code-formatting10
helm9
Programming languages (9)
Github contributions (5)
aws/karpenter-provider-aws
Feb 2022 - Jan 2023
Karpenter is a Kubernetes Node Autoscaler built for flexibility, performance, and simplicity.
Role in this project:
DevOps Engineer
DevOps EngineerContributions:221 reviews, 178 commits, 364 PRs in 11 months
Contributions summary:Ryan primarily focused on improving the build and release processes for the Karpenter project. They implemented error checking in the CI, separated and automated command-line instructions for the getting started guide. Furthermore, they worked on automating the release process by implementing a bot that periodically checks AWS APIs and updates auto-generated files. The user's contributions streamlined the deployment and documentation processes within the project.
karpenterkubernetes-node
juju/errors
Jun 2017 - Feb 2019
Common juju errors and functions to annotate errors. Based on juju/errgo
Role in this project:Back-end Developer
Back-end DeveloperContributions:6 commits, 3 PRs, 2 comments in 1 year 7 months
Contributions summary:Ryan's contributions primarily involve refactoring and improving the codebase of a Go project focused on error handling. They formatted code, improved comments, and enhanced documentation for clarity. The user also merged changes from the master branch, including bug fixes, and updated error types, showing a focus on maintaining and improving the project's core functionality.
javaannotatejuju
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.