Eric Williamson
Senior Principal Software Engineer at Puppet
Portland, Oregon, United States
Summary
👤
Senior🎓
Top SchoolEric Williamson is a Senior Principal Software Engineer in Portland, Oregon with over 17 years in software and 12 years of focused professional experience driving infrastructure and product engineering at Puppet. He architects scalable SaaS and microservice solutions, led rapid MVP deliveries, and integrated an acquisition stack into a top-earning product while automating complex scaling and CI processes. Deeply experienced in infrastructure-as-code and DevOps, he has contributed to well-known Puppet ecosystem projects (beaker and puppet_agent), improving EC2 provisioning, service startup verification, and cross-platform agent support. He combines hands-on coding with cross-functional leadership—mentoring engineers, shaping roadmaps, and partnering with executives to turn feasibility into shipped features. Notably, he reduced CI feedback loops from days to an hour and redesigned installers to cut support escalations, showing a knack for pragmatic, operationally impactful engineering.
13 years of coding experience
5 years of employment as a software developer
Bachelor of Science (BS), Computer Science, Bachelor of Science (BS), Computer Science at DeVry University PhoenixPeoria High School
Github Skills (27)
ec10
puppeteer10
puppet10
configuration-management10
automation10
amazon-ec210
aws10
automations10
sles10
devops10
linux9
bash9
aac9
infrastructure-as-code9
management8
Programming languages (7)
Github contributions (5)
voxpupuli/beaker
Oct 2014 - Feb 2018
Puppet Acceptance Testing Harness
Role in this project:
DevOps Engineer
DevOps EngineerContributions:12 commits, 7 PRs, 5 pushes in 3 years 4 months
Contributions summary:Eric made several contributions related to infrastructure and configuration management, particularly within an EC2 environment. They modified the system to explicitly open ports for various services like PostgreSQL, the node classifier, and the node classifier to improve functionality. The user also added helper functions for verifying the startup of key services like puppetserver and the node classifier and also made changes that allow the user to specify ports to open on EC2 instances, enhancing flexibility.
acceptance-testingpuppet
puppetlabs/puppetlabs-puppet_agent
Jun 2015 - Jul 2015
Module for managing Puppet-Agent
Role in this project:DevOps Engineer
DevOps EngineerContributions:13 commits, 7 PRs, 3 pushes in 27 days
Contributions summary:Eric primarily focused on enhancing and maintaining the Puppet Agent module within a Puppet Enterprise (PE) context. Their contributions involved extending platform support (specifically SLES 12 and SLES 11) and adapting the module to correctly configure repositories for both PE and FOSS environments. They updated the code to accommodate the agent's certificate usage and enabled SSL verification for PE users while removing outdated repository configurations. These changes indicate a strong focus on infrastructure as code and ensuring the Puppet Agent module functions correctly across different operating systems and deployment scenarios.
puppetsupported
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.