From f084f4c312e02846d3a7424f3bb9096db61f9d3f Mon Sep 17 00:00:00 2001 From: Jeremy Kauffman Date: Thu, 6 May 2021 17:03:14 -0400 Subject: [PATCH] hiring improvements --- content/jobs/api-engineer.md | 11 +++++------ content/jobs/application-engineer-lead.md | 20 ++++++++++---------- content/jobs/project-manager.md | 12 ------------ content/jobs/protocol-engineer.md | 14 +++++++------- view/template/content/_job.php | 10 ++++++---- view/template/page/join-us.php | 13 ++++++------- 6 files changed, 34 insertions(+), 46 deletions(-) delete mode 100644 content/jobs/project-manager.md diff --git a/content/jobs/api-engineer.md b/content/jobs/api-engineer.md index 0497dbe5..7064c456 100644 --- a/content/jobs/api-engineer.md +++ b/content/jobs/api-engineer.md @@ -1,12 +1,11 @@ --- -title: API Engineer +title: Backend Engineer order: 5 status: active location: remote (global) --- -[odysee.com](https://odysee.com) is less than a year old, and already a million of people use it every day. -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, -working with SQL databases, managing a Kubernetes cluster, and writing lots of test. -Experience with video delivery (e.g. CDNs, livestreaming) and high-availability systems is a plus. \ No newline at end of file +Backend engineers deal with the server-side portion of software related to [odysee.com](https://odysee.com). + +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 tests. Experience with video delivery (e.g. CDNs, livestreaming) and high-availability systems is a plus. \ No newline at end of file diff --git a/content/jobs/application-engineer-lead.md b/content/jobs/application-engineer-lead.md index cf160ca0..14835999 100644 --- a/content/jobs/application-engineer-lead.md +++ b/content/jobs/application-engineer-lead.md @@ -1,18 +1,18 @@ --- -title: Lead Application Engineer -order: 2 -status: closed +title: Application Engineer +order: 3 +status: active 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-android](https://github.com/lbryio/lbry-android), a browser and wallet for Android, currently in alpha. -- [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. +- [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) (Java), a browser and wallet for Android. This codebase will also power a forthcoming Odysee Android app. +- [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. diff --git a/content/jobs/project-manager.md b/content/jobs/project-manager.md deleted file mode 100644 index 25e9e0cd..00000000 --- a/content/jobs/project-manager.md +++ /dev/null @@ -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. diff --git a/content/jobs/protocol-engineer.md b/content/jobs/protocol-engineer.md index 386667cb..bffb9bfa 100644 --- a/content/jobs/protocol-engineer.md +++ b/content/jobs/protocol-engineer.md @@ -1,15 +1,15 @@ --- title: Protocol Engineer -order: 4 +order: 2 status: active location: remote (global) --- -Protocol engineers are responsible for building and maintaining all the non-blockchain parts of LBRY, though they work closely with -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. +Protocol engineers are responsible for building and maintaining the code that powers the LBRY network. -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. diff --git a/view/template/content/_job.php b/view/template/content/_job.php index 8cc26f5a..8c8e61bc 100644 --- a/view/template/content/_job.php +++ b/view/template/content/_job.php @@ -1,3 +1,4 @@ +

@@ -8,9 +9,10 @@ /

- +
+ Apply +
+
- -Apply - +
\ No newline at end of file diff --git a/view/template/page/join-us.php b/view/template/page/join-us.php index d4c512f1..6b256d22 100644 --- a/view/template/page/join-us.php +++ b/view/template/page/join-us.php @@ -36,7 +36,7 @@

Who We're Looking For

-

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:

+

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: