Sally Omalley is a Principal Software Engineer and OpenClaw maintainer with 11 years of experience building and hardening cloud-native tooling, primarily around Kubernetes and OpenShift. She combines backend engineering and DevOps expertise—contributing to high-profile projects like kubectl, kubelet/OpenTelemetry integrations, and the OpenShift conformance and installer stacks—to improve reliability, testing, and observability at scale. Her work spans API design, leader election and controller robustness, CI/test automation, and packaging for edge-optimized distributions like MicroShift. Based in Westford, MA, she brings a pragmatic, test-driven approach, often focusing on edge cases (empty-name routes, kubeadmin login tests) that prevent production surprises. Before moving fully into platform engineering she drew on a varied background from teaching to lab research, which informs her clear documentation and mentoring style.
11 years of coding experience
10 years of employment as a software developer
UMass Lowell
Bachelor's degree, Chemical Engineering & Biology, Bachelor's degree, Chemical Engineering & Biology at Northeastern University
A small form factor OpenShift/Kubernetes optimized for edge computing
Role in this project:
Backend & DevOps Engineer
Contributions:61 reviews, 41 commits, 46 PRs in 1 year 2 months
Contributions summary:Sally contributed to the `kube-controller-manager` component, porting it to the service manager framework and modifying related configuration files. They also made changes to the build process by adding and renaming packaging folders to consolidate systemd, build, and RPM files and adding an aio image build script. Furthermore, the user updated scripts to include a bindata script and performed various code rebase operations.
Helpers for going from apis and clients to useful runtime constructs
Role in this project:
Back-end Developer
Contributions:83 reviews, 5 commits, 11 PRs in 2 years 1 month
Contributions summary:Sally contributed to the `openshift/library-go` repository by addressing leader election configurations, resolving issues in the ClusterOperatorStatusController related to operator upgrades, and implementing helper functions for Prometheus query execution. They modified code to increase default lease durations and retry periods in the leader election, preventing potential service disruptions. The user's work also involved refactoring the status controller and providing tools for interacting with Prometheus for performance monitoring and metrics gathering, demonstrating their focus on the core functionality of the repository.
apiruntimehelpersrestconstructs
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.