Jeff Grafton
Software Engineer at Google
San Francisco Bay Area United States
Summary
🤩
Rockstar🎓
Top School
Top expert inKubernetes and Cloud-Native Technologies
Jeff Grafton is a software engineer with 11 years of experience focused on cloud-native build, test, and release infrastructure, currently contributing to ChromeOS privacy work at Google. He has deep DevOps and automation expertise demonstrated by sustained contributions to high-profile open-source projects like Kubernetes (test-infra, release, k8s.io) and Bazel's rules_docker, improving CI/CD, GCS interactions, and image build workflows. Based in the San Francisco Bay Area and trained at Carnegie Mellon, he blends hands-on scripting and tooling improvements with attention to reliability and permissions/edge cases in large distributed systems. An underappreciated strength is his background in stage management and sound for live theater, reflecting operational rigor, fast problem-solving under pressure, and strong cross-team coordination.
11 years of coding experience
Bachelor's degree, Bachelor's degree at Carnegie Mellon University
Stackoverflow
1reputation
0reached
0answers
0questions
Github Skills (36)
bosh10
kubernetes10
google-cloud-platform10
docker10
cloud-computing10
python10
scripting10
image10
testing10
bash10
dockers10
cicd10
gcp10
google-cloud-storage10
automation10
Programming languages (11)
Github contributions (5)
kubernetes-retired/contrib
Sep 2015 - Jun 2017
[EOL] This is a place for various components in the Kubernetes ecosystem that aren't part of the Kubernetes core.
Role in this project:
DevOps Engineer
DevOps EngineerContributions:22 commits, 23 PRs, 5 pushes in 1 year 9 months
Contributions summary:Jeff primarily contributed to improving the CI/CD processes and tooling within the repository. They implemented changes to the `mungegithub` tool, specifically modifying the "shame" reporting to better control email domains and output. Additionally, the user made updates to the docker build process to ensure recent base images and adjusted the build configuration to improve reliability. Furthermore, they corrected links in the submit queue interface and implemented adjustments within the continuous delivery scripts.
placeeolk8skubernetesecosystem
bazelbuild/rules_docker
May 2017 - Jan 2019
Rules for building and handling Docker images with Bazel
Role in this project:DevOps Engineer & Automation Engineer
DevOps Engineer & Automation EngineerContributions:6 commits, 5 PRs, 53 comments in 1 year 8 months
Contributions summary:Jeff primarily focused on improving the `rules_docker` project's build and deployment capabilities. Their commits involved refactoring and enhancing the `docker_bundle` rule by adding a stamping option for incorporating workspace status information into image tags. They also addressed issues related to image pulling and platform overrides. These changes demonstrate an effort to automate and streamline the image building and publishing workflow.
docker-imagebazelgooglestarlarkdocker
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.