Alexander Greene
Senior System Software Engineer at NVIDIA
Seattle, Washington, United States
Summary
🤩
Rockstar🎓
Top SchoolAlexander Greene is a Senior System Software Engineer with 11 years of experience building and operating containerized microservices and Kubernetes-native platforms, currently contributing at NVIDIA after leading the Operator Lifecycle Manager team at Red Hat. He combines deep backend and DevOps expertise with a track record of improving critical open-source projects such as Hypershift and the Operator Framework, where he fixed OLM reconciliation bugs, added metrics and Prometheus support, and introduced secure guest-cluster connectivity via a Konnectivity SOCKS5 proxy. Comfortable shipping production-grade Go code and bumping Kubernetes stacks, he focuses on reliability, observability, and maintainability in distributed control-plane software. A Northeastern Computer Engineering graduate based in Seattle, he pairs enterprise experience from IBM and GE with open-source leadership, bridging product needs and developer ergonomics. Colleagues rely on him for pragmatic technical direction and for turning complex operator lifecycle problems into testable, measurable solutions.
11 years of coding experience
9 years of employment as a software developer
Bachelor of Science (B.S.) Computer Engineering, Bachelor of Science (B.S.) Computer Engineering at Northeastern University
Github Skills (20)
kubernetes10
lm10
kubernetes-operator10
cicd10
operator-lifecycle-manager10
go10
openshift10
kubernetes-pods10
devops10
metric10
operator10
testing9
yaml9
crt9
grpc9
Programming languages (13)
Github contributions (5)
operator-framework/operator-registry
Jun 2019 - Jan 2023
Operator Registry runs in a Kubernetes or OpenShift cluster to provide operator catalog data to Operator Lifecycle Manager.
Role in this project:
Back-end Developer
Back-end DeveloperContributions:2 releases, 38 reviews, 7 commits in 3 years 7 months
Contributions summary:Alexander made several commits focused on improving the functionality and maintainability of the operator registry. They fixed a bug in the package list sanitization, introduced the ability to stream bundles, bumped Kubernetes dependencies to newer versions, and updated the Go version. These changes indicate a focus on core backend logic and the project's interaction with Kubernetes.
lifecycleoperator-lifecycle-managergrpcopenshiftoperator
operator-framework/operator-lifecycle-manager
Dec 2018 - Jan 2023
A management framework for extending Kubernetes with Operators
Role in this project:Back-end & DevOps Engineer
Back-end & DevOps EngineerContributions:2 releases, 357 reviews, 142 commits in 4 years 1 month
Contributions summary:Alexander primarily focused on enhancing the operator-lifecycle-manager project by adding features and resolving bugs. Their work involved implementing and exposing metrics for CSV sync events and configuring the global catalog namespace. The user also made changes to the installation scripts and refactored parts of the code base by renaming the envVar package to overrides. Furthermore, the user added support for Prometheus custom resources.
kubernetes-operatorsoperator-sdkkubernetes-applicationsk8s-operatoroperator
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.