Josh Steadmon
Software Engineer at Google
Mountain View, California, United States
Summary
🤩
Rockstar🎓
Top SchoolJosh Steadmon is a software engineer in Mountain View with 13 years of experience building and hardening developer tools and infrastructure at Google. He has deep expertise in source control and fuzzing, contributing significant back-end and automation work to the Git codebase (including libFuzzer entry points, memory-leak fixes, and performance optimizations) and integrating Git fuzzers into Google’s OSS-Fuzz. Previously a site reliability/systems engineer, he brings systems-level rigor to build/release automation and security-focused testing. Currently working on the Jujutsu version control project, he blends low-level C/C++ systems work with large-scale CI automation, and holds an MS in Computer Science from the University of Tennessee.
13 years of coding experience
21 years of employment as a software developer
MS, Computer Science, MS, Computer Science at University of Tennessee-Knoxville
Stackoverflow
101reputation
0reached
0answers
0questions
Github Skills (20)
git10
c-language10
bash10
internals10
c1110
git-branch10
makefile10
c1710
branches10
build-automation10
fuzzing10
cprogramming-language10
fuzzer10
fuzz-testing10
configuration-management9
Programming languages (8)
Github contributions (5)
google/oss-fuzz
Nov 2018 - Jul 2022
OSS-Fuzz - continuous fuzzing for open source software.
Role in this project:
Automation Engineer / Build & Release Engineer
Automation Engineer / Build & Release EngineerContributions:9 commits, 10 PRs, 5 comments in 3 years 8 months
Contributions summary:Josh primarily focused on modifying build scripts and the Makefile to integrate and maintain the fuzzing infrastructure for the git project within OSS-Fuzz. Their contributions include adding new fuzzers, updating build configurations to accommodate upstream changes in Git, and resolving build issues. They also addressed build warnings and ensured compatibility with different build options, specifically in the context of using fuzzing engines like libfuzzer and AFL.
fuzzingsecuritystabilityoss-fuzzfuzz-testing
git/git
Jun 2018 - Aug 2022
Git Source Code Mirror - This is a publish-only repository but pull requests can be turned into patches to the mailing list via GitGitGadget (https://gitgitgadget.github.io/). Please follow Documentation/SubmittingPatches procedure for any of your improvements.
Role in this project:Back-end Developer & Automation Engineer
Back-end Developer & Automation EngineerContributions:55 commits in 4 years 2 months
Contributions summary:Josh primarily contributed to improving the Git source code by adding fuzz testing targets to identify vulnerabilities. They implemented fuzz testing for `packfile` and `commit-graph` indices, creating new entry points compatible with `libFuzzer`. The user also addressed several issues related to Git's internal structure and build configuration, fixing memory leaks and buffer overflow issues, alongside optimizations such as speeding up object checks for partial clones. They also added instrumentation for trace2 to monitor various operations.
codemirrorcshell
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.