Nicholas Mitchell is an adaptable software engineer with 11 years of hands-on experience, currently on Spectrum’s National Field Support Team and studying cyber security at SUNY Brockport. He combines back-end and DevOps skills—demonstrated by meaningful contributions to Apache OpenWhisk’s controller and performance optimizations—with full-stack work improving the Kubernetes-focused Kui CLI/UI. Known for practical problem-solving and a continual learning mindset (active on TryHackMe), he focuses on reliability, efficient resource use, and clear integration examples for external services like Watson and Slack. Based in rural New York, he brings a blend of field support practicality and open-source engineering that helps bridge operational needs with scalable cloud-native solutions.
Associate of Arts and Sciences - AAS, Liberal Arts and Sciences/Liberal Studies, Associate of Arts and Sciences - AAS, Liberal Arts and Sciences/Liberal Studies at Monroe Community College
A hybrid command-line/UI development experience for cloud-native development
Role in this project:
Full-stack Developer
Contributions:144 releases, 109 reviews, 8530 commits in 4 years 2 months
Contributions summary:Nicholas made various changes to the Kui command-line/UI development experience, specifically focusing on the kubectl plugin. Their contributions include fixing bugs in both the UI and command-line interactions with Kubernetes resources, such as deployments and pods, and introducing new UI features like displaying annotations and labels. They also worked on improving code block styling and adding a feature for users to enable the display of the Kubernetes Dashboard through the Kui UI.
Apache OpenWhisk is an open source serverless cloud platform
Role in this project:
Back-end Developer & DevOps Engineer
Contributions:15 commits, 33 PRs, 1 push in 2 years 7 months
Contributions summary:Nicholas primarily focused on enhancing the OpenWhisk platform by improving catalog annotations, including sample inputs/outputs for various system and external integrations (e.g., Watson, Slack). They also corrected JSON issues within installation scripts and updated tests. Furthermore, the user modified the core controller, contributing to rule management, sequence action optimization, and improving the handling of timeouts and memory consumption. The contributions involve code changes in various files, including core controller components and test suites.
serverless-cloudfunctionsserverlessapachedocker
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.