Danny Mace
VP, IBM Storage Software Engineering
Raleigh, North Carolina, United States
Summary
🤩
Rockstar🎓
Top SchoolDanny Mace is a seasoned technology executive who blends deep engineering instincts with strategic business leadership, currently serving as VP of IBM Storage Software Engineering. With over 25 years in tech and a track record of launching more than ten commercially successful products, he has led organizations of 1,000+ people and managed businesses exceeding $1B in annual revenue. His career spans senior platform and cloud roles across IBM and Red Hat, where he focused on cloud-native platforms, application platforms, and hybrid cloud offerings. A hands-on contributor in open source, Danny has practical DevOps and backend experience across major OpenShift projects and tooling—work that includes installer, ingress, monitoring, and hyperscale control-plane efforts. He holds an M.S. and B.S. in Computer Science from Clemson and pairs academic rigor with pragmatic product-building instincts. Beyond executive strategy, he still digs into deployment, automation and API design, making him a rare leader equally comfortable in C-suite discussions and code-level fixes.
14 years of coding experience
7 years of employment as a software developer
Master of Science (M.S.), Computer Science, Master of Science (M.S.), Computer Science at Clemson University
English
Github Skills (60)
vs-extension10
debugging10
api-rest10
kubernetes10
debug10
visual-studio-code-extension10
javascript10
develop10
apidoc10
kubernetes-apiserver10
api-design10
restful-api10
testing10
configuration-management10
bash10
Programming languages (16)
Github contributions (5)
openshift/hypershift
Jan 2021 - May 2022
Hyperscale OpenShift - clusters with hosted control planes
Role in this project:
Back-end & DevOps Engineer
Back-end & DevOps EngineerContributions:507 reviews, 222 commits, 196 PRs in 1 year 3 months
Contributions summary:Danny contributed to the core functionality of the HyperShift operator by refactoring code, which included introducing the concept of the hosted cluster and ensuring the consistent application of immutability rules and configurations. Their work involved defining and managing API resources, including the creation of new resources like the cluster control plane and various supporting services. The user also made improvements in the area of testing, especially cluster teardown and upgrade assertions, for added reliability. The user has also contributed to the setup of OIDC (OpenID Connect) configuration within the hosted control plane and addressed deployment-related issues.
clustershostedopenshiftsdnk8s
openshift/api
May 2015 - May 2020
Canonical location of the OpenShift API definition.
Role in this project:Back-end Developer
Back-end DeveloperContributions:63 commits, 34 PRs, 358 comments in 5 years 1 month
Contributions summary:Danny primarily contributed to the OpenShift API definition, focusing on enhancements related to deployment strategies. Their work includes modifications to the rolling update mechanism, adding support for deployment hook volume inheritance, and refactoring the API to align with upstream changes. They also introduced the ingresscontroller API. These changes involve modifications to types and configuration files within the project.
apiopenshiftlocationkubernetesdefinition
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.