You’ve spent hundreds of hours on open source. Your GitHub graph is a solid green wall. You’ve got pull requests merged into projects you barely use. And yet, you’re still not getting callbacks. Sound familiar?
That sinking feeling isn’t just you. It’s the entire industry waking up to a brutal truth: The industry told you to contribute to open source to get ahead. Then everyone did. Now you’re just another cog in the machine.
I’ve seen it firsthand. A friend of mine – let’s call him Jake – had a GitHub profile that looked like a Christmas tree. Over 500 contributions in the last year. He couldn’t get a single interview at a FAANG company. Why? Because his contributions were shallow: typo fixes, minor documentation updates, and a few one-line changes in popular repos. The recruiters saw right through it.
The dirty secret that nobody wants to admit: open source contribution as a career hack was always a self-defeating prophecy. When the industry started pushing everyone to ‘build a portfolio’ on GitHub, it turned a genuine signal of passion into a checkbox exercise. And once something becomes a checkbox, it stops differentiating anyone.
When everyone is a contributor, no one is.
Look at the top comments on the original article. One user says bluntly: ‘It really never was. Most people don’t contribute to open source, let alone donate to those projects. It was really just a labour of love… The resume padders were filtered out in the interview.’ That’s the cold truth. The people who actually got hired for their open source work were the ones who did it because they couldn’t stop themselves – not because they wanted a job.
So what changed? The signaling value collapsed. Economists call this ‘market for lemons’ – when quality becomes impossible to distinguish, the market punishes everyone. In the early days, a GitHub profile with 100 contributions said ‘this person is obsessed with code.’ Now, it says ‘this person followed the tutorial.’
But here’s the twist: contribution that still actually matters – that’s the real signal. The kind where you own a project, maintain it for years, fix real bugs, and build a community. That kind of work screams ‘I care about this craft’ louder than any resume bullet point. But let’s be honest – most people don’t have the time or the inclination for that. They want the shortcut.
And that’s the problem. The shortcut has been paved over by a thousand other people taking the same shortcut. Now it’s just a dirt road.
The best way to stand out in tech is to stop trying to stand out and start solving problems that matter.
Here’s what I mean: don’t contribute to a project just because it’s popular. Contribute because you use it every day and something about it drives you crazy. Fix that one thing. Write a detailed issue. Maintain a fork. Or better yet, build something small that solves a pain point you actually have. The developers who get noticed are the ones who can’t help but build – not the ones who check a box.
This isn’t about being anti-open source. It’s about being pro-reality. The reality is that your time is finite. If you’re spending it on low-effort PRs for the sake of a green graph, you’re burning hours that could go into deep, meaningful work – the kind that actually changes your career trajectory.
So stop treating GitHub like a video game. Treat it like a workshop. The people who hire based on open source aren’t looking for quantity – they’re looking for depth, for taste, for a mind that cannot leave a problem unsolved. That’s the signal. Everything else is noise.
Will you keep making noise, or will you make something that actually matters?
FAQ
Q: Are you saying open source contribution is completely useless for getting hired?
A: No. But the type of contribution matters. Shallow, one-off PRs to popular repos have lost their signaling value. Deep, sustained contributions to projects you actually use – or better yet, building your own – still carry weight because they demonstrate genuine passion and expertise.
Q: What should I do instead of contributing to open source?
A: Focus on depth over breadth. Pick one project you're passionate about – either your own or a small but active community – and invest real time: maintain it, triage issues, write documentation, fix hard bugs. Or build a tool that solves a specific problem you face. That kind of work is harder to fake and far more impressive to experienced recruiters.
Q: Isn't this just gatekeeping? Not everyone can afford to spend hours on open source for free.
A: Fair point. The article is a critique of the industry's hypocrisy, not a demand that everyone become a full-time maintainer. The real issue is that the system incentivized surface-level participation, which diluted the signal for everyone. If you can't afford deep open source work, then don't – focus on your day job, side projects that bring you joy, or learning. The point is that pretending to be 'passionate' by churning out trivial PRs is a waste of energy.