Karl Shultz
Senior Quality Assurance Engineer at Tanium
Wake Forest, North Carolina, United States
Summary
🤩
Rockstar🎓
Top SchoolKarl Shultz is a Senior Quality Assurance Engineer with nine years focused on building robust QA processes and test automation for large-scale, multi-OS endpoint and CI/CD systems. He’s a longtime contributor to Jenkins-related open source at CloudBees, improving Pipeline, SCM plugins, and the Blue Ocean UX through a mix of backend fixes, acceptance tests, and reliability work. At Tanium he built QA engineering practices from scratch, authored release gates and test plans, and drove high throughput issue triage—opening 250+ bugs/improvements in a year with a >70% take rate. Karl blends clever automation (TestCafe, Selenium, Jenkins Pipelines) with pragmatic manual testing and advocacy for shifting left, documentation, and end-user outcomes. He also has hands-on experience creating internal CI clusters and performance harnesses to validate plugin and pipeline behavior, showing a rare combination of tooling, test infrastructure, and product-focused QA.
9 years of coding experience
22 years of employment as a software developer
High SchoolBA Psychology, BA Psychology at University of North Carolina at Chapel Hill
Github Skills (18)
javascript10
webdriver10
selenium10
github10
testing10
selenium-ide10
acceptance-testing10
cicd10
java10
javas10
junit10
jenkins10
jenkins-ci10
workflow-engine9
pipeline9
Programming languages (6)
Github contributions (5)
jenkinsci/github-branch-source-plugin
Oct 2018 - Feb 2020
GitHub Branch Source Plugin
Role in this project:
Back-end Developer & Test Automation Engineer
Back-end Developer & Test Automation EngineerContributions:23 commits, 10 PRs, 3 pushes in 1 year 4 months
Contributions summary:Karl primarily focused on enhancing the functionality and stability of the GitHub Branch Source Plugin. Their contributions involved disabling caching on Windows systems, modifying the on-disk cache configuration, and addressing issues related to multi-branch pipelines configured by URL. The user also made several changes in the test suite, indicating a strong focus on test coverage and ensuring the robustness of the plugin. These tests involved different credential types.
jenkinsjenkins-pipelinejenkins-pluginjenkins-api-plugin
kshultzCB/plugin-compat-tester
Nov 2017 - Jul 2020
Contributions:15 pushes, 9 branches in 2 years 7 months
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.