Mike Dougherty
Principal Automation Engineer
San Francisco, California, United States
Summary
🤩
Rockstar🎓
Top SchoolMike Dougherty is a Principal Automation Engineer in San Francisco with 13 years of experience building CI/CD, release, and DevOps tooling across startups and mid-size companies. He has a strong track record automating complex release processes—most notably contributing to Docker/Moby and Docker docs by improving build, signing, and S3 distribution scripts. At companies from dotSyntax to Tagged/if(we) and Docker, he has blended hands-on engineering with developer productivity work, shipping internal tools that let teams move faster. Currently leading automation at Mission Lane, he focuses on resilient, auditable pipelines and developer ergonomics. Mike brings deep familiarity with Python, Bash, release engineering patterns, and a habit of "coding himself out of a job" by removing operational friction. An early Digsby developer, he combines protocol-level experience with production release craftsmanship that often lives behind the scenes but powers reliable software delivery.
13 years of coding experience
13 years of employment as a software developer
BS Computer Science, BS Computer Science at Rochester Institute of Technology
Github Skills (18)
container10
docker10
scripting10
bash10
dockers10
cicd10
pg10
release-management10
automation10
amazon-s310
aws-s310
gnupg10
automations10
s3-bucket10
rep9
Programming languages (12)
Github contributions (5)
moby/moby
Aug 2015 - Feb 2016
The Moby Project - a collaborative project for the container ecosystem to assemble container-based systems
Role in this project:
DevOps Engineer & Automation Engineer
DevOps Engineer & Automation EngineerContributions:8 commits, 7 PRs, 68 comments in 6 months
Contributions summary:Mike primarily contributed to the automation and release processes of the Docker project. They implemented and refined build and release scripts, including adding support for different GPG key identifiers and S3 bucket configurations. Their work involved modifying the `hack/release.sh` and `hack/install.sh` scripts to support the distribution and installation of Docker packages. Additionally, they addressed various issues with repository creation and package conflicts.
containerscollaborative-projectgolangcontainer-ecosystemdocker
docker/docs
Dec 2016 - Dec 2016
Source repo for Docker's Documentation
Role in this project:DevOps Engineer & Automation Engineer
DevOps Engineer & Automation EngineerContributions:1 comment in 1 day
Contributions summary:Mike's contributions primarily focused on enhancing the Docker documentation repository's release and build processes. They added support for longer S3 bucket paths and different GPG key identifiers within the release scripts. Furthermore, they refactored the install script to support different domains and multiple keyservers. These changes involved modifying `hack/release.sh` and `hack/install.sh`, impacting how Docker packages are built, signed, and distributed.
docker
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.