DEV Community

Timmothy
Timmothy

Posted on

I Get Paid to Write Open Source Code. Here's How You Can Too.

Most developers write open source for free. I write it for money.

Not consulting. Not "exposure." Real bounties — $50 to $10,000 — posted on GitHub issues by companies that need code shipped.

Here's how the system works and how to get started.

What Are GitHub Bounties?

Companies and maintainers attach dollar amounts to GitHub issues. You solve the issue, submit a PR, it gets merged, you get paid.

Platforms like Algora and Opire handle the payment infrastructure. The bounty amount is visible on the issue, and payment is triggered on merge.

No interviews. No timesheets. Just code → cash.

Where to Find Bounties

Search Query #1: Algora Bounties

label:"💎 Bounty" state:open type:issue
Enter fullscreen mode Exit fullscreen mode

This finds ~264 open bounties across GitHub. Filter by dollar labels:

label:"💎 Bounty" label:"$100" state:open type:issue
Enter fullscreen mode Exit fullscreen mode

Search Query #2: General Bounties

label:bounty "$" state:open type:issue
Enter fullscreen mode Exit fullscreen mode

Active Repos with Bounties Right Now

Repo Range Tech Stack
tenstorrent/tt-metal $3,500–$10K C++/Metal
zio/zio $150–$1K Scala
rohitdash08/FinMind $200–$1K TypeScript
calcom/cal.com $50–$100 TypeScript/React
coollabsio/coolify $7–$100 PHP/Laravel

I maintain a curated list of bounty repos that I update regularly.

How to Actually Win a Bounty

1. Read the Entire Issue

70% of rejected PRs fail because they missed acceptance criteria. Read every checkbox.

2. Check Existing PRs First

If 8 people already submitted, your odds are low unless your solution is clearly better. Look for issues with <3 PRs.

3. Quality Beats Speed

Maintainers want the PR that works, has tests, and includes documentation.

My winning formula:

  • Clean, well-commented code
  • README with setup instructions
  • Example outputs or screenshots
  • Tests (even when not required)

4. Comment Before You Start

Some platforms require /attempt or /try commands. Even when they don't, a quick comment showing your approach prevents duplicate work.

5. Be Transparent About AI

If you use AI tools, say so. Nobody cares — they care that the code works.

The Math

I submitted 5 bounty PRs in 24 hours totaling $575 potential. Even at 40% merge rate, that's $230 for a day's work. Bounty hunting is a numbers game amplified by skill.

Get Started

  1. Star the awesome-bounties repo for updated lists
  2. Search GitHub with the queries above
  3. Pick an issue matching your skills
  4. Build something great, submit the PR
  5. Move to the next one while waiting

Every merged PR = portfolio piece + GitHub contribution + income. Triple value.


I also build free productivity tools and AI prompt packs when I'm not hunting bounties.

Top comments (0)