mirror of
https://github.com/LBRYFoundation/lbry.com.git
synced 2025-08-23 17:47:26 +00:00
hiring improvements
This commit is contained in:
Jeremy Kauffman
parent
4f232d9379
commit
f084f4c312
6 changed files with 34 additions and 46 deletions
|
|
@ -1,12 +1,11 @@
|
||||||
---
|
---
|
||||||
title: API Engineer
|
title: Backend Engineer
|
||||||
order: 5
|
order: 5
|
||||||
status: active
|
status: active
|
||||||
location: remote (global)
|
location: remote (global)
|
||||||
---
|
---
|
||||||
|
|
||||||
[odysee.com](https://odysee.com) is less than a year old, and already a million of people use it every day.
|
Backend engineers deal with the server-side portion of software related to [odysee.com](https://odysee.com).
|
||||||
Help us scale our backend infrastructure to meet this ever-growing demand and prepare for the next 10x increase
|
|
||||||
(and the 10x after that, and the one after that). This involves designing and implementing APIs in Go,
|
This position involves developing Odysee's backend infrastructure to serve tens of millions of active users. It involves designing and implementing APIs in Go,
|
||||||
working with SQL databases, managing a Kubernetes cluster, and writing lots of test.
|
working with SQL databases, managing a Kubernetes cluster, and writing lots of tests. Experience with video delivery (e.g. CDNs, livestreaming) and high-availability systems is a plus.
|
||||||
Experience with video delivery (e.g. CDNs, livestreaming) and high-availability systems is a plus.
|
|
||||||
|
|
@ -1,18 +1,18 @@
|
||||||
---
|
---
|
||||||
title: Lead Application Engineer
|
title: Application Engineer
|
||||||
order: 2
|
order: 3
|
||||||
status: closed
|
status: active
|
||||||
location: remote (global)
|
location: remote (global)
|
||||||
---
|
---
|
||||||
|
|
||||||
As the touch and interaction point for the vast majority of LBRY users, applications play a tremendous role in the success of the LBRY protocol.
|
Applications play a tremendous role in the success of the LBRY protocol and are how almost everyone uses the LBRY network.
|
||||||
|
|
||||||
LBRY maintains three applications. All three use either ReactJS or React Native.
|
LBRY maintains three applications:
|
||||||
|
|
||||||
- [lbry-desktop](http://github.com/lbryio/lbry-desktop), an Electron based desktop browser and wallet.
|
- [lbry-desktop](http://github.com/lbryio/lbry-desktop) (JS/React), an Electron based desktop browser and wallet. This codebase also powers [odysee.com](https://odysee.com).
|
||||||
- [lbry-android](https://github.com/lbryio/lbry-android), a browser and wallet for Android, currently in alpha.
|
- [lbry-android](https://github.com/lbryio/lbry-android) (Java), a browser and wallet for Android. This codebase will also power a forthcoming Odysee Android app.
|
||||||
- [spee.ch](https://github.com/lbryio/spee.ch), a web-based image and video sharing and self-hosting tool that syncs to the LBRY network.
|
- [odysee-ios](https://github.com/lbryio/odysee-ios) (Swift), the Odysee mobile app.
|
||||||
|
|
||||||
This position would involve becoming the team leader of all three projects, which each currently have a single full-time engineer working on them.
|
Success at this position involves strength at both user-experience and programming. Application engineers are expected to play a substantial role in product vision and design.
|
||||||
|
|
||||||
Success at this position involves strength at both product vision and user-experience as well as code architecture and standards. Being able to showcase previous experience building an engaging and delightful application is a requirement for this position.
|
Being able to showcase previous experience creating delightful, engaging applications is beneficial for obtaining this position.
|
||||||
|
|
|
||||||
|
|
@ -1,12 +0,0 @@
|
||||||
---
|
|
||||||
title: Project Manager
|
|
||||||
order: 3
|
|
||||||
status: closed
|
|
||||||
location: remote (global)
|
|
||||||
---
|
|
||||||
|
|
||||||
Being a project manager at LBRY requires skillful facilitation and coaching of a menagerie of full-time engineers and community contributors. It demands the ability to break down big goals into practical plans and keep track of a wide variety of tasks and small details.
|
|
||||||
|
|
||||||
This isn't a typical project management position. LBRY is an open-source, community driven company with few externally driven deadlines and a big focus on transparency.
|
|
||||||
|
|
||||||
This role is not to act as a boss of our engineers, but as a facilitator, administrator, and coach. Experience as a project manager in an open-source community is encouraged but not required. Great communication skills, coupled with flexibility and a detail-oriented mindset is necessary.
|
|
||||||
|
|
@ -1,15 +1,15 @@
|
||||||
---
|
---
|
||||||
title: Protocol Engineer
|
title: Protocol Engineer
|
||||||
order: 4
|
order: 2
|
||||||
status: active
|
status: active
|
||||||
location: remote (global)
|
location: remote (global)
|
||||||
---
|
---
|
||||||
|
|
||||||
Protocol engineers are responsible for building and maintaining all the non-blockchain parts of LBRY, though they work closely with
|
Protocol engineers are responsible for building and maintaining the code that powers the LBRY network.
|
||||||
the blockchain team and there's a lot of cross-pollination. Protocol work involves deeply technical things like networking
|
|
||||||
(DHT, TCP, UDP), databases (key-value and SQL), filesystems. It also involves maintaining an open-source project: communicating
|
|
||||||
clearly in writing, reviewing code contributions, and interacting with the wider LBRY community. You can be a great protocol engineer
|
|
||||||
by excelling at either half of the equation or by showing a strong ability to bridge the two halves.
|
|
||||||
|
|
||||||
Our [code](https://github.com/lbryio/lbry-sdk) is currently in Python, but we're migrating to Go.
|
Protocol work involves deeply technical things like networking (DHT, TCP, UDP), databases (key-value and SQL), filesystems.
|
||||||
|
It also involves maintaining an open-source project: communicating clearly in writing, reviewing code contributions, and
|
||||||
|
interacting with the wider LBRY community. You can be a great protocol engineer by excelling at either half of the equation or by showing a strong ability to bridge the two halves.
|
||||||
|
|
||||||
|
The [primary codebase](https://github.com/lbryio/lbry-sdk) is currently in Python, but we're migrating to Go.
|
||||||
Experience with either language, or with blockchain or peer-to-peer technology, is beneficial but not required.
|
Experience with either language, or with blockchain or peer-to-peer technology, is beneficial but not required.
|
||||||
|
|
|
||||||
|
|
@ -1,3 +1,4 @@
|
||||||
|
<section>
|
||||||
<h3 id="<?php echo trim(str_replace(' ', '-', strtolower($metadata['title']))) ?>">
|
<h3 id="<?php echo trim(str_replace(' ', '-', strtolower($metadata['title']))) ?>">
|
||||||
<?php echo $metadata['title'] ?>
|
<?php echo $metadata['title'] ?>
|
||||||
<?php if (isset($metadata['status'])): ?>
|
<?php if (isset($metadata['status'])): ?>
|
||||||
|
|
@ -8,9 +9,10 @@
|
||||||
<small class="meta">/ <?php echo $metadata['location'] ?></small>
|
<small class="meta">/ <?php echo $metadata['location'] ?></small>
|
||||||
<?php endif ?>
|
<?php endif ?>
|
||||||
</h3>
|
</h3>
|
||||||
|
<br/>
|
||||||
|
<a class="button button--primary" href="https://docs.google.com/forms/d/e/1FAIpQLSdotoPPQcTiWGct640IildtWg_Fh68Z5KgUwYFO7rtlZPBHJw/viewform?usp=sf_link">Apply</a>
|
||||||
|
<br/>
|
||||||
|
<br/>
|
||||||
<?php echo $jobHtml ?>
|
<?php echo $jobHtml ?>
|
||||||
|
|
||||||
<?php if (isset($metadata['url'])): ?>
|
</section>
|
||||||
<a class="button button--primary" href="<?php echo $metadata['url']?>">Apply</a>
|
|
||||||
<?php endif ?>
|
|
||||||
|
|
@ -36,7 +36,7 @@
|
||||||
|
|
||||||
<h2 id="looking">Who We're Looking For</h2>
|
<h2 id="looking">Who We're Looking For</h2>
|
||||||
|
|
||||||
<p>There's no one kind of LBRYian. We value people who can bring new perspectives to our team. Here are some traits that are important to us:</p>
|
<p>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:</p>
|
||||||
|
|
||||||
<ul>
|
<ul>
|
||||||
<li>Ability to solve complex problems in simple ways. LBRY has many moving parts, but we try our hardest to power it with simple code. Your job is not just to solve problems, but to solve problems in a way that will last and can easily be picked up by other people.</li>
|
<li>Ability to solve complex problems in simple ways. LBRY has many moving parts, but we try our hardest to power it with simple code. Your job is not just to solve problems, but to solve problems in a way that will last and can easily be picked up by other people.</li>
|
||||||
|
|
@ -115,12 +115,11 @@
|
||||||
</table>
|
</table>
|
||||||
|
|
||||||
<p>The issue you choose does not necessarily need to be fully completed, and we don't expect a perfect first contribution. Open a
|
<p>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 compensate at or above market rates for all
|
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.</p>
|
||||||
accepted pull requests.</p>
|
|
||||||
|
|
||||||
<p>For questions or problems with a particular issue, please comment directly on the GitHub issue. For setup or environment trouble,
|
<p>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 <code>README</code>. You can also join
|
open a separate issue or email the contact listed in the project <code>README</code>. You can also join
|
||||||
<code>#developers</code> in <a href="https://chat.lbry.com">our chat</a> to interact with other community members.</p>
|
<code>#developers</code> in <a href="https://chat.lbry.org">the chat</a> to interact with other community members.</p>
|
||||||
|
|
||||||
<h3>3. Meet the Team</h3>
|
<h3>3. Meet the Team</h3>
|
||||||
|
|
||||||
|
|
@ -151,9 +150,9 @@
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
<h2 id="other-work">Other Work</h2>
|
<h2 id="other-work">Other Work</h2>
|
||||||
<p>Interested in contributing but not ready for commitment? We have a <a href="/faq/contributing">guide for contributors</a>
|
<p>Interested in contributing but not ready for commitment? We have a <a href="https://lbry.tech/contribute">guide for contributors</a>
|
||||||
to help you find other ways to get involved. If none of that suits your fancy, join our
|
to help you find other ways to get involved. If none of that suits your fancy, join the
|
||||||
<a href="https://chat.lbry.com">Discord chat</a> and we'll help you find something you'll love.</p>
|
<a href="https://chat.lbry.org">Discord chat</a> and we'll help you find something you'll love.</p>
|
||||||
</div>
|
</div>
|
||||||
</section>
|
</section>
|
||||||
</main>
|
</main>
|
||||||
|
|
|
||||||
Loading…
Add table
Reference in a new issue