Jeff Thompson
Engineer III at CrowdStrike
Fort Collins, Colorado, United States
Summary
🤩
Rockstar🎓
Top SchoolJeff Thompson is an experienced back-end engineer with 8+ years building reliable, testable systems and currently an Engineer III at CrowdStrike after leading impactful efforts at BillGO and CloudBees. He’s known for reducing release toil and costs by orders of magnitude, overhauling complex configurations and dependency management, and improving automated testing and observability across large codebases. His open-source contributions to core Jenkins and Jenkins Remoting demonstrate deep expertise in distributed systems, security hardening, and low-level channel/agent reliability. Comfortable across Java, C#, and microservice architectures, he excels at untangling legacy systems into maintainable, testable designs. Collected academic rigor (BS/MS in Electrical and Computer Engineering, ~3.8 GPA) and a habit of digging into background context let him quickly find pragmatic, durable solutions. A less obvious strength: he pairs hands-on refactoring with process changes that measurably boost team productivity and release cadence.
8 years of coding experience
24 years of employment as a software developer
Bachelor’s Degree, Electrical and Computer Engineering, 3.84 GPA, Bachelor’s Degree, Electrical and Computer Engineering, 3.84 GPA at Brigham Young University
English, Spanish
Github Skills (16)
javas10
jenkins10
remoting10
jenkins-ci10
java10
testing10
networking9
continuous-integration9
communications9
security9
multithreading9
continuous-delivery9
data-communication9
network9
net9
Programming languages (7)
Github contributions (5)
jenkinsci/remoting
May 2018 - May 2021
Jenkins Remoting module
Role in this project:
Back-end Developer
Back-end DeveloperContributions:2 releases, 94 reviews, 329 commits in 3 years
Contributions summary:Jeff primarily contributed to refactoring and improving the remoting module, focusing on core functionality. Their work involved addressing thread safety issues and updating the code to utilize more modern and efficient methods for command processing and channel management. They also made improvements to the handling of resources and the stability of the channel. The changes appear to be focused on the low-level communication between the Jenkins master and agents.
jenkinsremote-executionremoting-protocolsjenkins-pluginjenkins-api-plugin
jenkinsci/jenkins
Dec 2019 - Mar 2021
Jenkins automation server
Role in this project:Backend Developer
Backend DeveloperContributions:42 reviews, 103 commits, 89 PRs in 1 year 3 months
Contributions summary:Jeff primarily contributed to improving the Jenkins automation server by addressing issues related to the fingerprint logs, including reducing verbosity and converting inner classes to lambdas. The contributions involved modifications to core Java code, including testing and applying changes to support security and stability. The user demonstrated a focus on code quality, testability, and overall system performance, with additional contributions related to security updates.
continuous-deploymentjenkinscontinuous-testinggroovydevops
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.