David Wittman
Senior System Engineer at Wickr
Kansas City, Missouri, United States
Summary
🤩
Rockstar🎓
Top SchoolDavid Wittman is a Senior System Engineer with 15 years of experience building and hardening cloud-native infrastructure, currently working at AWS and serving as Principal Infrastructure Engineer at Wickr. He blends Dev, Ops, and security expertise—evident from substantive open-source contributions to widely used projects like Ansible and HashiCorp Vault—improving automation modules, secrets CLI robustness, and production-grade Ansible roles for Consul and Redis. David’s background spans private cloud, managed databases, and security-focused messaging platforms, with a strong track record of shipping reliable init/systemd integrations, service management fixes, and test-driven configuration changes. Based in Kansas City, he brings a pragmatic approach to complex systems: preferring clear automation, reproducible deployments, and thoughtful error handling. Colleagues rely on him for operational resilience and subtle improvements that reduce toil and surface hard-to-catch bugs.
15 years of coding experience
9 years of employment as a software developer
Robert Morris University
English, Spanish
Github Skills (31)
python10
redis10
testing10
secret-management10
configuration-management10
authentication10
user-authentication10
consul10
secrets-manager10
go10
ansible10
systemd10
ansible-galaxy10
devops10
admin9
Programming languages (23)
Github contributions (5)
DavidWittman/ansible-redis
Apr 2014 - Mar 2021
Highly-configurable Ansible role to install Redis and Redis Sentinel from source
Role in this project:
DevOps Engineer
DevOps EngineerContributions:6 releases, 191 commits, 143 PRs in 7 years
Contributions summary:David focused on improving the deployment and configuration of Redis using Ansible. They added support for Redis Sentinel, including the creation of init scripts and configuration files for Debian and RedHat-based systems. Major contributions include implementing systemd service files, setting ulimit for open files, and fixing issues with init scripts for consistent startup and status reporting.
ansible-roleredisredis-sentinel
mattfinlayson/ansible-consul
Jan 2016 - Feb 2016
Ansible role for consul
Role in this project:DevOps Engineer
DevOps EngineerContributions:7 commits, 6 PRs, 3 comments in 1 month
Contributions summary:David primarily focused on improving the configuration and testing of the Ansible role for Consul. They added variables for advanced Consul configuration like retry joins and WAN connectivity, enhancing the role's flexibility. Furthermore, they fixed issues with logging in systemd and implemented tests to verify log file permissions and content, increasing the role's reliability and maintainability. Finally, the user corrected a configuration error and added a new configuration variable to the templates.
ansible-roleconsul
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.