Developer Relations

Railway · Remote (United States) · FullTime

Apply on company site

This is a remote position available anywhere in the world! Linkedin makes us show a country, but we hire the best people wherever they are.

At Railway, we make it extremely simple for engineers to deploy logic without thinking about servers. Our goal is to make developers orders of magnitude more efficient by becoming the operating system for modern development.

Dev Rel is an often misunderstood role, we see it as a hybrid of being able to make cool stuff and talking about it, but also being the tip of the spear in getting feedback from the market. You should be knowledgeable about modern DevOps practices, the state of the cloud infra world, while being opinionated about how the next 10 years of Dev Tools should look like.

This is a high impact, high agency role where you are given a high degree of autonomy to work with any function you desire while receiving any support from the team you need. As our first hire in this area, we expect you to wear a lot of hats while setting the strategy.

Want to learn about our work culture? Here is a three-part blog series that will help you see the unique ways our team works (Parts 1, 2, 3, and 4).

About the role

For this role, you will:

About you

We value and love to work with diverse persons from all backgrounds

Things to Know

For better or worse, we're a startup; our team dynamics are different from companies of different sizes and stages.

Benefits and Perks

At Railway, we provide best in class benefits. Great salary, full health benefits including dependents, strong equity grants, equipment stipend, and much more. For more details, check back on the main careers page.

Beyond compensation, there are a few things that we believe that make working at Railway truly unique:

How We Hire

No tricks. No surprises. Here's the entire process.

  1. Talk with us about the role

    • This is completely open ended and we're just trying to see who you are, what you want to do, and where you wanna go.

  2. Work on a small project to discuss in the interview

    • Asynchronously implement the following:

    • Build something and deploy it on Railway using as many features as possible

    • You will submit your solution before the interview, and you'll sit down with a member of the team and go over the above. We'll poke into your solution, as well as get you acquainted with a member of the team.

    • You can, and SHOULD ask us questions ahead of time if you have them.

  3. Review your solution with the Team

    • You'll sit down with someone on the team and go over the above. We'll poke into your solution, as well as get you acquainted with two more members of the team.

    • Looking for: Learn about your problem solving skills. How you break down a problem and how you present a solution.

    • Interview Structure (60 Minutes):

      • Pre-work (submitted before your interview): Build and deploy your project

      • 0-5 minutes: Introduction

      • 5-20 minutes: Walking through the project

      • 20-50 minutes: Walking through how you think about content, relations, intersection with other roles

      • 50-60 minutes: Time for you to ask your interviewers questions

  4. Meet the Team

    • You'll meet the Team, which will be comprised of 4 people from vastly different sections of the company.

    • Looking for: How you work with the rest of the team and communicate.

  5. Offer and Details Chat with CEO

    1. Finally, we will go over the process, the role, and hammer out the details about your position, onboarding, and all the deets.

Final Note: The interview goes both ways. Once again, please ask us things. Many things! Hard things. That's what we're here for.

#Global

Job alert

Get new jobs by email

Save this search and get relevant new jobs when they appear.