Résumé

Sunday, Jul 6, 2025 | 7 minute read | Updated at Sunday, Jul 6, 2025

My current résumé.

Download: pdf | rtf | txt

Doug Munsinger

e-mail: doug.munsinger@gmail.com

DevOps Engineer

SUMMARY: skilled senior DevOps/Infrastructure engineer with UNIX systems admin background, experienced in crafting automated Continuous Integration | Continuous Delivery structures using GitHub Enterprise, Gitlab CICD, Jenkins, Amazon Web Services (AWS) and physical servers and employing golang, python, ansible, terraform, packer and bash tooling.

TECHNICAL SKILLS AND EXPERTISE

OPERATING SYSTEMS: Linux (AmazonLinux 2023, CentOS, Ubuntu, Alpine), UNIX, Windows.

SECURITY: Iptables, Cloudflare, OpenSSH, IPSEC.

NETWORK APPLICATIONS AND PROTOCOLS: Postgresql and Mariadb/Mysql, Apache, Apache Tomcat and Nginx. SMTP (Sendmail, Postfix, Qmail), IMAP, DNS (Bind, TinyDNS), Icinga, Spacewalk, Wireshark, BGP and OSPF.

SOFTWARE: Puppet, Chef, Ansible, FUNC, golang, bash shell script, Python, MySQL. Postgresql, RPM and YUM, including custom package management, Github Enterprise, CVS, SVN, Python, Jenkins, AWS CLI & Boto3, powershell, cygwin, Go SDK.

PROFESSIONAL EXPERIENCE

Staff Infrastructure (DevOps) Engineer (DE4) Toast, Inc, Boston, MA February 2020 to Present

Create AWS SSM Doc using assumable IAM role to trigger Lambda using a docker image containing code to automate and make self-service for the Payments Team renewal and update of PGP/GPG keys and SFTP keys for auth and signing of financial transmissions. Develop and deploy automated service to examine docker images deployed into AWS ECS and built and stored in AWS ECR for CVE vulnerabilities and trigger an automated update and rebuild of any images found vulnerable, flagging any failed builds for further handling and allowing a grace period to be set for updates to be available. The tooling allowed using Prisma (Palo Alto Networks), Jfrog Xray or open source CVE scanners (Anchore). Develop and deploy service in AWS ECS to bridge between multiple Jenkins builders and a custom front end to build and deployment to allow immediate deployment of built images while the custom deployment tool added this functionality natively. Built and deployed Lambda function using a docker image containing golang code to perform pre- and post- postgresql upgrade sql and vacuumdb tasks to automate and ultimately make database upgrades self-service by the teams owning them. Make root level changes to infrastructure to remedy issues and then stabilize Toast infrastructure during outages and incidents. Principle DevOps Engineer Haven Life (Mass Mutual), Boston, MA June 2019 to February 2020

Instantiate kubernetes clusters in AWS using KOPS. Create CICD pipelines and scripting in gitlab to test, build and deploy. Create S3 + Cloudfront website distribution with reverse-proxy paths to server in kubernetes. Created ansible plays to distribute env vars from single source of truth for local, dev, uat and production in automated pipelines. Fixed dev ECS deployments. Created deployment environments for new annuity insurance product website. Senior DevOps Engineer Catapult Sports Inc., Wilmington, MA February 2019 to June 2019

Forklift applications into QA environment in AWS. Automate creating base AMI from CentOS original. Automate AMI create for windows base AMI and windows IIS webserver using cmd.exe and powershell plus Hashicorp packer. Move msbuild code out of Octopus + TFS, into Jenkins. Automate builds for Jenkins controller and goCD CICD server on Linux. Automate builds for Jenkins controller and goCD CICD server on Linux. Senior DevOps Engineer Verizon Media Group (as of Jan 2019 – formerly Oath, Inc., a Verizon Company and formerly AOL), Boston, MA June 2017 to February 2019

Built tooling to allow Jenkins to configure itself at boot and to be stateless as part of a CICD build farm behind ELB+ASG Cloud Formation stack in AWS. Simplified devops tooling builds and reduced duplicate code by pulling in blocks of coding using git submodules. Designed and coded installer module to allow pulling in specific ansible roles in pipeline builds. Extended and maintained spin_cloud, a python tool allowing AWS testing clouds to be spun up with a simple yaml configuration file Architected, built and maintained a complete CICD system using GitHub, python, java, ruby, Jenkins, AWS, Hashicorp vault, and console, ansible, and shell, which from commit to testing to deploy required only approvals by humans. Crafted Nebula-in-a-Box, collapsing enterprise CICD functionality onto a single instance DevOps Engineer AOL, Inc., a Verizon Company (acquired Millennial Media), Boston, MA November 2015 to June 2017

Crafted and extended CICD Discover Jenkins Plugin, allowing Jenkins to automatically configure and execute pipeline jobs from a git commit without human involvement. Created and extended hiedra_on_rails, to read and parse HiedraDB (arbitrary yaml data injected by etcd into AWS AMIs by ansible). Developed Jenkins server ansible playbook and Vagrant dev environment and integrated packer and ansible to standardly spin up AWS AMI images. Converted existing puppet3 playbooks to ansible roles. DevOps Engineer Millennial Media, Inc. (acquired Jumptap), Boston, MA October 2014 to November 2015

Wrote Puppet3 modules for deploying & managing new enhanced adserver application. AWS Disaster Recovery POC implemented DR in AWS using autoscaling groups, canary listener application and ansible playbooks to bring up Elastic Load Balancer and Autoscaling Groups to duplicate production in AWS on the fly. System Administrator Jumptap, Inc., Boston, MA September 2013 to October 2014

Created QA/Dev VMWare Infrastructure, VMWare Infrastructure for Teamcity build/test development. Developed and implemented Puppet 3 system, application and application server management modules. Implement and develop beaker rspec testing framework for automated testing and validation of Puppet modules. Network Engineer Paytronix, Inc., Waltham, MA September 2012 to September 2013

Configure and deploy second internet feed, router and external switch into DR datacenter. Work with DR site provider to re-engineer BGP and network design to accommodate automated failover to 2nd feed. Sr. Application Operations Specialist Constant Contact, Inc., Waltham, MA October 2009 to September 2012

Developed automation scripting in Python (core) and Javascript (presentation) using FUNC and Puppet to deploy and manage jBoss and Java applications across 1136 Linux servers in three environments (QA, Prod, DR). Senior Software Engineer, System Services
Evergreen Investments (Wells Fargo), Boston, MA January 2008 to October 2009

Implemented and supported IBM Websphere MQ on Solaris 10, tying directly to custodial services for high value application messaging. Tied Websphere MQ into Sonic Enterprise Service Bus, providing troubleshooting, maintenance and ongoing support 24 x 7. Compiled, installed, piloted, and rolled out to production Subversion replacing CVS. Senior Customer Support Engineer Crossbeam Systems, Inc., Waltham, MA May 2006 to January 2008

Hardware, software application and network support for Linux-based Security Appliance. Troubleshooting and resolution of Check Point firewall application issues, Linux kernel, memory and hardware driver issues, network traffic and routing issues in large-scale critical networks. Senior UNIX Systems Admin and Network Engineer Egenera, Inc., Marlborough, MA September 2000 to May 2006

Architected and implemented security and services on Red Hat Enterprise Linux for corporate network – firewalls, apache2, VPN, file and print services, DHCP, DNS, Samba, NFS, all internal and external connectivity and monitoring. Architecture, proof-of concept engineering, implementation and documentation for corporate network services and access. Firewall Systems Engineer Fidelity Investments Systems Company, Marlborough, MA March 1998 to September 2000

Implement and maintain the Internet firewall structure for Fidelity Investments, 842 SUN Solaris enterprise servers providing proxies, gateways, ipfilter, webservers and relays, across three data centers and two remote hosting facilities. BIG IP load balancers. On-call 24 x 7. Automated system reporting and tracking using perl + mysql. Network Administrator Silverplatter, Inc., Norwood, MA January 1998 to March 1998

Network services on Linux (DNS, DHCP, silverplatter.com, FTP, monitoring) Repaired DNS structure, backups, maintained environment Unix and NT Systems Administrator Inforonics, Inc., Littleton, MA SUN-oriented Database development company December 1996 to December 1998

Solaris – UNIX systems administration and SUN Server build and deploy. Developed custom Solaris packaging. Scripted monitoring tools. Automated Windows desktop support and deployment.

EDUCATION

CONTINUING PROFESSIONAL EDUCATION AWS Cloud. 2016 – Present Puppet Training 2013 Python 2009 BigIP F3 Network Architecture and Implementation 2000 RedHat Certified Engineer course 1999

Worcester Polytechnic, UNIX Network and Systems Administration 1996 UCLA, Physics Major

REFERENCES – Available on Request

© 2025 by Doug Munsinger

About Me

About Cover

I build tools. I write scripts, plugins, compiled Go code binaries, terraform .tf files, APIs, hacks (a lot of these…). Glue that makes automation happen by connecting together open source projects like terraform, ansible packer, Jenkins, Docker, Kubernetes, Github and so on.

I do a lot of note taking and documentation. Mostly this is to let me pick back up where I left off on code or infrastructure when it has issues or needs to be upgraded or replaced a year or two down the road. Some of those notes & docs might be useful to someone other than myself. If that might be the case, they go here.

intuitive engineering describes taking physical structure and system design out of the lego or erector set viewpoint — where you piece things together one-by-one — and into an understanding of the art of engineering.

Watch really complex systems, say a network, for awhile and you find unexpected interactions become normal as complexity increases. The same is true for CICD systems and Devops/Infrastructure Engineering tools. There are gremlins in the dark corners.

Totems:

  • Avoid wherever possible, complexity, and where you find complexity, work toward a simpler design as a goal.
  • The elegant, aesthetically pleasing solution is also in most cases the least effort and personnel to support in the long run.
  • Expect and deal with missteps as they show up – complex designs can present opportunities as you work through them that are NOT visible at the start of the project. This is true in building construction. It is also true in network and system design, in software design.
  • Make that discovery part of the process, take advantage of those simplified and elegant changes as they present themselves.
  • Look for the consequences several steps ahead for each decision.
    • How locked into a design does it make you?
    • Can you live with that?
    • Is there a less restrictive/simpler/better/more elegant decision in design that can be made that doesn’t block off avenues?
    • Can you solve a problem once and reuse that solution?
    • Is there a modular or plugin design that would keep a flexibility?
  • Use open source tooling where that is practical.
  • Use best of breed. Build the interconnections and tooling passing from one system to another.
  • Customize as little as possible. Write bespoke code as little as possible.

I live in the Northeast and I am currently employed by Toast, Inc., as a Staff Devops/Infrastructure/Cloud Engineer (the titles keep changing).

—doug

Toolbelt

Toolbelt Image

I was a cabinetmaker and finish carpenter in Los Angeles for 17 years before working as a UNIX Systems Administrator.

I used an IBM 386 clone desktop with a green monochrome terminal monitor and a dot matrix printer to manage contracts, correspondence, and write promotional letters to prospective clients. I kept diving under the hood to tweak and optimize the system, adding a whopping 1 MB RAM and editing himem.sys in DOS to get it used.

The clone had a 20 MB hard drive. It backed up onto 5-1/2" floppy disks. It needed to be physically reformatted and rebuilt from backups about every six months. More often as it aged.

I fell in love with the command line, and only reluctantly installed Windows 3.1 when an application, I think it was a dog-slow CAD program, required it.

From there I went to an x86 Linux machine, back when Linux was a university play toy and no one expected it to become a serious operating system, except a few of us. From there, Solaris and Sun machines, IBM mainframes and IRIS, and eventually back to Linux, Ubuntu, Gentoo, Debian, Redhat, Amazonlinux.

I completed a UNIX & Systems Admin course, a one year certificate program at WPI that could be done in 8 weeks full time if you were committed to learning. I was.

From that point I’ve been employed as a systems administrator, firewall engineer (Fidelity Investments), network engineer (Egenera), hardware support engineer (Crossbeam Systems), devops engineer (the title most used since), and recently cloud and infrastructure engineer (Toast).

It used to be I actually saw physical hardware. At this point, it’s been maybe 7 years since I’ve been in a datacenter.

I still love the command line…

Command Line

License

MIT License

This covers any and all code snippets I’ve authored and included here.

MIT License Logo

© 2025 by Doug Munsinger

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.

Good luck  ;^)

Images

All images are excluded and are “All rights reserved.”

They are not licensed for reuse or redistribution unless explicitly stated.