Thomas Stringer
Senior Software Engineer at NVIDIA
New Hampshire, United States
Summary
🤩
Rockstar🎓
Top SchoolThomas Stringer is a Senior Software Engineer with 11+ years of experience building cloud-native, Linux-first infrastructure and reliability tooling, currently at NVIDIA after leadership roles at Freenome and Microsoft. He specializes in containers and Kubernetes, Go/Python/Bash development, and production-grade observability and automation, with deep hands-on expertise in PostgreSQL and other RDBMS. A pragmatic DevOps practitioner, he has contributed notable fixes and features to high-profile open-source projects such as cloud-init, Azure agent tooling, ACS/AKS engine, and Open Service Mesh—often improving Azure integration, security, and monitoring. Thomas combines systems-level troubleshooting from his RDBMS and field engineering background with software delivery and SRE practices, and he frequently implements pragmatic automation (including GitHub Actions workflows) to bridge development and operations.
11 years of coding experience
13 years of employment as a software developer
Bachelor of Science - BS, Systems Engineering, Bachelor of Science - BS, Systems Engineering at United States Naval Academy
Stackoverflow
5,792reputation
564kreached
125answers
18questions
github
top-5%
git
top-5%
merge
top-5%
Github Skills (55)
service-mesh10
kubernetes10
github-ci10
cloud-computing10
cloud-init10
apidoc10
python10
testing10
configuration-management10
linux10
bash10
workflow-engine10
grafana10
microsoft-azure10
cicd10
Programming languages (17)
Github contributions (5)
trstringer/manual-approval
Mar 2022 - Nov 2022
Pause your GitHub Actions workflow and request manual approval from set approvers before continuing
Role in this project:
DevOps Engineer
DevOps EngineerContributions:15 releases, 19 reviews, 73 commits in 7 months
Contributions summary:Thomas primarily contributed to the automation and management of the GitHub Actions workflow for manual approval within the repository. Their work involved implementing approval mechanisms, including setting up issue creation and comment processing. They also made improvements for handling different approval keywords (e.g., "approve", "lgtm") and fixed bugs related to handling newlines in approval comments. Further contributions included logging improvements and enabling team-based approvers.
github-actions-workflowpausedevopsdeploymentrelease-management
openservicemesh/osm
Jul 2021 - Nov 2022
Open Service Mesh (OSM) is a lightweight, extensible, cloud native service mesh that allows users to uniformly manage, secure, and get out-of-the-box observability features for highly dynamic microservice environments.
Role in this project:Back-end Developer & DevOps Engineer
Back-end Developer & DevOps EngineerContributions:206 reviews, 41 commits, 68 PRs in 1 year 4 months
Contributions summary:Thomas focused on enhancing the Open Service Mesh (OSM) project by implementing features and addressing various issues. Contributions include making certificate key sizes configurable, adding a demo book app watcher, integrating tracing options with Jaeger, and improving bug reporting capabilities, including adding ingress information. They also addressed vulnerabilities and updated dependencies to improve the project's security and stability.
observabilitymicroservicesecuremicroservicesextensible
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.