Jeremy Whitlock
Senior Software Engineer at Google
Villa Rica, Georgia, United States
Summary
🤩
Rockstar🎓
Top SchoolJeremy Whitlock is a senior software engineer with 22 years of experience building both open-source and enterprise systems, currently contributing to multiple areas of Google Cloud. He has deep practical expertise in API design, microservices on Kubernetes, and large-scale data platforms from roles at Apigee and Nodeable, and has helped shape tooling around OpenAPI/Swagger and Node.js. A prolific open-source contributor, Jeremy has improved widely used projects such as psutil and swagger-js and has made platform-level contributions to Apache Subversion, demonstrating fluency across C, Python, Java, and JavaScript. He blends architect-level design with hands-on implementation—having built ERP, trading systems, CI tooling, and lightweight PaaS frameworks—and often tackles cross-platform build and integration challenges that are easy to miss. Based in Villa Rica, GA, he pairs a long history of community stewardship with practical production engineering at scale.
22 years of coding experience
11 years of employment as a software developer
BS, Computer Science, BS, Computer Science at University of West Georgia
English
Stackoverflow
3,818reputation
1.2mreached
71answers
1question
package
top-5%
svn
top-5%
python
top-5%
linux
top-5%
Github Skills (45)
unit-testing10
javascript10
schema-validation10
json-schema10
python10
swagger10
c1110
validation10
networking10
java10
system-monitoring10
c1710
javas10
json-validation10
subversion10
Programming languages (23)
Github contributions (5)
apigee-127/swagger-tools
Jun 2014 - Aug 2021
A Node.js and browser module that provides tooling around Swagger.
Role in this project:
Back-end Developer
Back-end DeveloperContributions:476 commits, 68 PRs, 263 pushes in 7 years 3 months
Contributions summary:Jeremy's commits indicate a focus on enhancing the Swagger Tools project's backend functionality. Specifically, the user implemented features for handling missing model references, identifying cyclic models, and detecting duplicate model definitions. This involved modifications to the core specification validation logic, including adding new validation checks and error handling to the codebase. The work suggests a focus on improving the robustness and accuracy of the OpenAPI (Swagger) specification validation process.
nodejsswagger
jclouds/legacy-jclouds
May 2011 - Apr 2013
Role in this project:Back-end Developer
Back-end DeveloperContributions:38 commits in 1 year 11 months
Contributions summary:Jeremy focused on refactoring the provider plugin system within the jclouds core. Their primary contribution was adding the necessary plumbing to support the refactoring of the provider plugin system, particularly for object metadata related to cloud providers. This work involved adding interfaces and utility classes for providers, including predicates and methods to find providers based on criteria. Additionally, the user added unit tests to validate the changes.
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.