Get paid to learn and do the stuff you love. Gain rep to get the sweet jobs.


Liquid Labs places bounties on many of it's issues (tracked in Github). Individuals who submit merges for open source issues can receive both cash, and in some cases, a share of certain future revenues. Subject to additional agreements, authorized developers can also pick up issues from private repositories which will typically pay more in cash, but lack the revenue sharing component.


Beginning in December, Liquid Labs will begin publicly posting bounty lists for open source bounties. If you are interested in participating in the program as a beta-tester, contact piecework@liquid-labs.com for early access, or just to let us know what you think about the program or how we could make it work for you.



Search for an issue that fits your skills or interests. Knocking out open source bounties is a great way to generate referencable work in a new skill, and get paid for it.


Contact piecework@liquid-labs.com. Once you receive confirmation of reservation, then you will have between 8 and 48 hours to submit a patch or ask for an extension.


Fulfillment is typically accomplished primarily through the implementaiton of one or more automated tests which will be included in the issue spec.


Once all tests are passing, the code can be submitted. We try and either accept or give feedback on every issue within 2 business days. If there is an issue, reference and remedies will always be provided.


If no issues are raised, then payment is renedred. Cash is paid by Venmo within 1 business day of review completion. Revenue share payments are also distrubuted via Venmo on a quarterly basis.



Every bounty comes with a cash component. Open source bounties generally range from $20-80 dollars. Much less, and it's not worth the overhead of posting the bounty; much more and we try and break it up into smaller chunks of work. Private or closed source bounties range much higer.

Revenue Sharing

Most of the open source components developed by Liquid Labs feed into closed source, commercial applications. When Liquid Labs uses the open source components in commercial code, a portion of the development fees Liquid Labs charges the commercial customer are shared with the developers who claimed bounties on the open source components used.
With a closed source bounty, the developer is working for a client as a standard sub-contractor (except, with very little overhead, the developer keeps 80%+ of the revenues). And so these bounties pay more in up-front cash, but don't have any profit sharing component.

Let's chat.