Site Reliability Engineer (Full remote)

Slite

Saint Louis Missouri

United States

None
(No Timezone Provided)

You'll join the Core Squad and support the ongoing work here, to make developers life easier, and support our users growth. The mission is to support developer toolchain, testing environments, release scripts, infrastructure configuration and monitoring for live features.

Because examples are better than a thousands words, here are some:

  • Developers to have an outstanding platform to develop, close to production, and as simple as running a local Webpack. (We use Kubernetes and Garden.io)
  • Reduce our CI time to be able to merge and release features and fixes faster (at 20 minutes today, should be under 10 minutes).
  • We have our services and release process defined as code. But our platform is still configured via the Google interface. We want to automate and clarify its definition.
  • We want to benchmark our platform with 3x active users. We have currently 10 000 users using our platform simultaneously, but with our growth, this number increases every month. What actions we'll need to take in the year to come to support this?

We understand that the role of a Site Reliability Engineer is to support a solid plan, and executing is done via pairing with a team of engineers.

Eventually as one of the early member of Slite, you'll be be able to shape the future of it. We share as much ownership on the way we work and on the product itself as we can as we're convinced our success is 99% due to our team.

Few words on infrastructure today

We're today a team of 16 engineers, and our tooling has been developed by a few of them, and sometimes with the help of consultancy agency. We've always invested in having a high quality toolchain. We are running on Google Cloud Platform, Kubernetes, JavaScript for everything from our API services, React for our front-end and React Native for our mobile apps.

We like simple but performant tools. For instance, by just running yarn release-branch, we are able to test you ongoing code in a production environment. It gives great confidence at iterating faster on features, help with QA on real data, and also we can experiment new things faster.

But we're at a stage where our services grew, and maintaining the development pipeline is a job in itself. Also, no-one in our team has background in DevOps or Site Reliability.

Who will I be working with?

You'll be part of the Core Squad at Slite. It's a 6 engineers team, with a technical engineering manager to support and challenge you.
  • Charley - Engineering Manager: Previously lead our editor at Slite.
  • Florian - Security engineer: He's organising a security conference, and he is splitting his time between developing back-end features and being responsible for the security at Slite.
  • Alexandre - Back-end Engineer: He joined Slite as the third engineer and supported our back-end since then.
  • Antoine - Back-end Engineer: He transitioned our real-time synchronisation system for docs to support complex blocks like sketches, tables, etc..
  • Jason - Lead Editor Engineer: He works on pushing Slite editing experience and features to the top
  • Eric - Editor Engineer: He's the one that made Slite Editor on mobile a way more pleasant experience

We're organised as small squad of ~5 engineers, working in cycles: One week to stop coding and reflect on a solid plan. Three weeks to actually execute the plan.

A few words on Slite

On what we do, check out slite.com and if you're not a Slite user yet, give it a spin ??

More importantly, why we re building Slite: we help teams work in more thoughtful manners, based on written culture, information transparency, asynchronous collaboration. And because of that we unlock remote for them.

We work by these principles and evangelize on them.

Why join Slite?
  • Work with talented & passionate people with diverse experiences and backgrounds
  • Make a dent: we strive to shift the way people collaborate and organize at a large scale, potentially impacting millions of people
  • Feel your impact: Slite is still early stage, everything we do matters and your impact is critical

Requirements
  • Previous experience as a Site Reliability Engineer or DevOps
  • Knowledge around JavaScript
  • Handled a site with heavy traffic already
  • Go for simple solutions first, propose complex ones as the needs evolve
  • Curious mindset, and can drive topics on their own

Benefits

?? Competitive salary and equity

?? 5 Weeks PTO + Public Holidays

?? Buy any book policy

??? Remote setup: co-working or at-home setup, your pick. Slite covers your expenses.

?? We go on team OffSlites every 4 months.

?? Macbook: a new laptop for a new job

Site Reliability Engineer (Full remote)

Slite

Saint Louis Missouri

United States

None

(No Timezone Provided)

You'll join the Core Squad and support the ongoing work here, to make developers life easier, and support our users growth. The mission is to support developer toolchain, testing environments, release scripts, infrastructure configuration and monitoring for live features.

Because examples are better than a thousands words, here are some:

  • Developers to have an outstanding platform to develop, close to production, and as simple as running a local Webpack. (We use Kubernetes and Garden.io)
  • Reduce our CI time to be able to merge and release features and fixes faster (at 20 minutes today, should be under 10 minutes).
  • We have our services and release process defined as code. But our platform is still configured via the Google interface. We want to automate and clarify its definition.
  • We want to benchmark our platform with 3x active users. We have currently 10 000 users using our platform simultaneously, but with our growth, this number increases every month. What actions we'll need to take in the year to come to support this?

We understand that the role of a Site Reliability Engineer is to support a solid plan, and executing is done via pairing with a team of engineers.

Eventually as one of the early member of Slite, you'll be be able to shape the future of it. We share as much ownership on the way we work and on the product itself as we can as we're convinced our success is 99% due to our team.

Few words on infrastructure today

We're today a team of 16 engineers, and our tooling has been developed by a few of them, and sometimes with the help of consultancy agency. We've always invested in having a high quality toolchain. We are running on Google Cloud Platform, Kubernetes, JavaScript for everything from our API services, React for our front-end and React Native for our mobile apps.

We like simple but performant tools. For instance, by just running yarn release-branch, we are able to test you ongoing code in a production environment. It gives great confidence at iterating faster on features, help with QA on real data, and also we can experiment new things faster.

But we're at a stage where our services grew, and maintaining the development pipeline is a job in itself. Also, no-one in our team has background in DevOps or Site Reliability.

Who will I be working with?

You'll be part of the Core Squad at Slite. It's a 6 engineers team, with a technical engineering manager to support and challenge you.
  • Charley - Engineering Manager: Previously lead our editor at Slite.
  • Florian - Security engineer: He's organising a security conference, and he is splitting his time between developing back-end features and being responsible for the security at Slite.
  • Alexandre - Back-end Engineer: He joined Slite as the third engineer and supported our back-end since then.
  • Antoine - Back-end Engineer: He transitioned our real-time synchronisation system for docs to support complex blocks like sketches, tables, etc..
  • Jason - Lead Editor Engineer: He works on pushing Slite editing experience and features to the top
  • Eric - Editor Engineer: He's the one that made Slite Editor on mobile a way more pleasant experience

We're organised as small squad of ~5 engineers, working in cycles: One week to stop coding and reflect on a solid plan. Three weeks to actually execute the plan.

A few words on Slite

On what we do, check out slite.com and if you're not a Slite user yet, give it a spin ??

More importantly, why we re building Slite: we help teams work in more thoughtful manners, based on written culture, information transparency, asynchronous collaboration. And because of that we unlock remote for them.

We work by these principles and evangelize on them.

Why join Slite?
  • Work with talented & passionate people with diverse experiences and backgrounds
  • Make a dent: we strive to shift the way people collaborate and organize at a large scale, potentially impacting millions of people
  • Feel your impact: Slite is still early stage, everything we do matters and your impact is critical

Requirements
  • Previous experience as a Site Reliability Engineer or DevOps
  • Knowledge around JavaScript
  • Handled a site with heavy traffic already
  • Go for simple solutions first, propose complex ones as the needs evolve
  • Curious mindset, and can drive topics on their own

Benefits

?? Competitive salary and equity

?? 5 Weeks PTO + Public Holidays

?? Buy any book policy

??? Remote setup: co-working or at-home setup, your pick. Slite covers your expenses.

?? We go on team OffSlites every 4 months.

?? Macbook: a new laptop for a new job