Changing the landscape of content distribution is no easy task. LBRY is growing rapidly, and we're looking for great people to join us. If you want a challenging and rewarding pursuit on a team that shares your passion and curiosity, you've come to the right place.
Some things to know about working at LBRY:
There's no one kind of LBRYan. We value people who can bring new perspectives to our team. Here are some traits that are important to us:
Click "Apply" below any job listed above to begin the process. We use a 3-step hiring process:
A brief (30 minute max), non-technical, introductory phone call with either the CEO, CTO, CMO, and/or appropriate lead. We'll discuss what kind of work you want to do, what we're looking for, deal breakers on both sides, and any questions you have.
Non-technical hires will be asked to complete a compensated trial task after they apply and complete step 1.
Technical hires are required to complete a (compensated) code contribution to the repository they'd be working on. Issues tagged "good first issue" are suitable for this purpose, though you are welcome to work on another issue or even something that's not filed at all. You can work at your own pace -- there's no time limit. Successful candidates usually spend 4 to 16 hours doing this.
Steps 1 and 2 may be completed in either order. Engineers are welcome to contribute a pull request before the introductory call.
Project(s) | Position | Issues |
---|---|---|
lbrycrd | Blockchain Engineer | good first issues |
lbry-sdk (client) | Protocol Engineer | good first issues |
lbry-desktop lbry-android |
Application Engineer | good first issues |
lbrytv chainquery |
API Engineer | good first issues |
The issue you choose does not necessarily need to be fully completed, and we don't expect a perfect first contribution. Open a pull request as soon as you'd like any feedback from one of our developers. We offer cryptocurrency for accepted and good-faith attempts at a pull request.
For questions or problems with a particular issue, please comment directly on the GitHub issue. For setup or environment trouble,
open a separate issue or email the contact listed in the project README
. You can also join
#developers
in the chat to interact with other community members.
A longer meeting with the team members you'd be working directly with, as well as at least one of the CEO, CTO, or CMO. We'll go deeper into the specific role, how you can best fit with the team, and what expectations we have for each other. We may also ask you about your code contribution and your knowledge of key skills and technologies.
After this we'll make a hiring decision.
Know someone who'd be a great fit? Tell them about us, send them a link to this page, or show up at their house unexpectedly with a box of candy and a persuasive pitch. If we hire them, we'll pay you $5,000. That's what we call a win-win.
Interested in contributing but not ready for commitment? We have a guide for contributors to help you find other ways to get involved. If none of that suits your fancy, join the Discord chat and we'll help you find something you'll love.