Why I Still Contribute to Open Source After Landing a Full-Time Job
Aman Kumar
Full Stack Engineer @ StartupCoaching
“The projects that got me hired were self-directed. It would be easy to let that stop the moment a job fills the same hours. I've tried not to let that happen.”
The projects that got me a foot in the door were self-directed — no ticket, no sprint, no one waiting on the PR. It would be easy to let that stop the moment a full-time job fills the same hours a side project used to. I've tried not to let that happen.
Open-source work forces a different kind of discipline than client work does: your code has to make sense to a stranger with zero onboarding, your commit messages have to stand alone, and nobody is going to walk over to your desk to ask what you meant.
It's also the only place I get to pick the stack without a client's legacy codebase deciding it for me — which is where most of what I know about newer tooling actually comes from, well before it shows up in paid work.
It doesn't have to be a big project. A cleanly written bug fix on someone else's repo has taught me more some weeks than a full sprint at work.
Written by Aman Kumar
Full Stack Engineer — React, Node.js & Next.js
Building scalable web applications, developer tools, and AI products. Currently shipping full-stack features at StartupCoaching.
Full Stack Development in Production: Lessons from Ninepages Techsolutions
Building TomatoAI: Wiring Up Multiple AI APIs Without Losing Your Mind
More Thoughts
Why I Built SnippetsX Instead of Just Using Pastebin
Every time I paired with someone on a bug, we ended up in the same loop — screenshots, zipped folders, or a screen-share nobody could type into. SnippetsX started as a fix for that one annoyance.
11 Months In: What Full-Time at StartupCoaching Taught Me About Shipping
Freelance and self-taught projects reward polish. A product team rewards throughput. Ten months into a full-time Full Stack Engineer role, that's the biggest recalibration I've had to make.