Charlie Robbins
Principal Engineer at Chainguard
New York, New York, United States
Summary
🤩
Rockstar🎓
Top SchoolCharlie Robbins is a Principal Engineer and entrepreneurial technologist with 17 years of experience building developer-first systems, currently shaping supply-chain security for open source at Chainguard while advising and investing across startups. A longtime Node.js ecosystem leader and early "npm" contributor, Charlie has hands-on pedigree in server tooling, proxies, CLI utilities and cloud APIs—work that helped power widely used projects like node-http-proxy, jsdom, nconf, forever and flatiron. He blends product-focused engineering with HCI training from Columbia, driving user-centered platforms and measurable business KPIs while navigating board-level strategy (OpenJS/Node.js). Known for refactoring messy internals into testable, maintainable systems, he combines pragmatic execution with community stewardship and a keen interest in governance and consensus-building.
17 years of coding experience
19 years of employment as a software developer
Master of Science (M.Sc.) Human Computer Interaction, Master of Science (M.Sc.) Human Computer Interaction at Columbia EngineeringBachelor of Engineering Software Engineering, Bachelor of Engineering Software Engineering at McGill University
French
Github Skills (46)
asynchronous10
url-routing10
javascript10
jquery10
back-end-development10
apidoc10
api-design10
async10
testing10
command-line-interface10
configuration-management10
http10
process-management10
dom-manipulation10
api10
Programming languages (14)
Github contributions (5)
flatiron/flatiron
Aug 2011 - Jun 2013
framework components for node.js and the browser
Role in this project:
Full-stack Developer
Full-stack DeveloperContributions:118 commits, 2 PRs, 2 comments in 1 year 10 months
Contributions summary:Charlie primarily contributed to the core flatiron framework, focusing on expanding its CLI capabilities. This included adding the CLI plugin, integrating `optimist` for argument parsing, and incorporating `director` for command routing. They also refactored the CLI plugins to use the new `this` context in broadway. In addition, the user created example applications.
browsernode-jsjavascriptframeworkcomponents-framework
foreversd/forever-monitor
Jul 2012 - Jan 2020
The core monitoring functionality of forever without the CLI
Role in this project:Back-end Developer
Back-end DeveloperContributions:72 commits, 10 PRs, 18 pushes in 7 years 7 months
Contributions summary:Charlie primarily refactored and added core functionality, along with tests, to the project. This included changes to the `monitor.js` file, suggesting work on the core monitoring logic. The user also performed API and test refactoring, further indicating contributions to the project's internal structure and functionality. The contributions demonstrate a focus on improving the underlying code and ensuring its reliability through testing.
monitoringmonitorcli
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.