Erik Kuefler
Staff Software Engineer at Google
Sunnyvale, California, United States
Summary
👤
Senior🎓
Top SchoolErik Kuefler is a Staff Software Engineer in Sunnyvale with 13 years of experience building large-scale systems at Google and earlier engineering work with NASA/JPL and research roles. He holds an MS in Computer Science from Stanford and a BS from Pomona College, and has progressed through multiple senior engineering roles at Google since 2008. Erik blends backend systems design with test automation expertise, exemplified by his notable open-source contributions to Bazel where he enhanced Groovy build rules and added Spock test support. He is comfortable navigating both product-grade engineering and developer tooling, improving reliability, dependency handling, and developer ergonomics. Colleagues describe him as a pragmatic problem-solver who surfaces subtle build-system issues before they reach users. Based in the Bay Area, he pairs deep technical rigor with a long track record of shipping maintainable infrastructure.
13 years of coding experience
9 years of employment as a software developer
BS, Computer Science, BS, Computer Science at Pomona CollegeMS, Computer Science, MS, Computer Science at Stanford University
English
Stackoverflow
188reputation
11kreached
4answers
3questions
Github Skills (19)
unit-testing10
groovy10
build-system10
bazel10
spock10
testing9
java9
junit9
javas9
istio6
google-compute-engine6
putty6
mocking6
gwt6
google-cloud-shell6
Programming languages (9)
Github contributions (5)
bazelbuild/bazel
Jun 2015 - Mar 2016
a fast, scalable, multi-language and extensible build system
Role in this project:
Back-end Developer & Test Automation Engineer
Back-end Developer & Test Automation EngineerContributions:23 commits, 2 PRs, 71 comments in 9 months
Contributions summary:Erik primarily contributed to the Groovy build system, specifically by developing and refining the Groovy rules within Bazel. They introduced support for Spock unit testing framework, implemented the `groovy_junit_test` rule, and made improvements to the existing Groovy rules regarding dependency handling, error reporting, and command line length limitations. These modifications enhanced the testing capabilities and build process of the project, making it more robust and user-friendly for Groovy-based projects.
scalablecorrectbazelmulti-languagebuild-system
google/gwtmockito
May 2013 - Oct 2019
Better GWT unit testing
Contributions:1 release, 139 commits, 16 PRs in 6 years 6 months
testingunitmockingtesting-toolsgwt
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.