Infrastructure Engineer

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.

Our core mission at Railway is to make software engineers higher leverage. We believe that people should be given powerful tools so that they can spend less time setting up to do, and more time doing.

Building the infrastructure which powers the Railway engine is the most core problem at Railway. As a infrastructure engineer, you will be directly responsible for exposing the knobs, bells, and whistles that allow the users to build to the wildest dreams. The tools you build will be instrumental in not only scaling internal operations, but scaling the company to infinite and beyond!

For this role, you will:

• Build system-level software: our challenges aren't your usual kube-fits-all variety, so be prepared to build things from scratch based on first principles

• Have a strong understanding or curiosity of OS level primitives - our business hinges on efficiency, so that means being masters of CPU, Memory, Network and the Kernel that wields it

• Be a student of both distributed systems and simplicity - you know how to reach for the RAFT but you also know how far you can get with Postgres

• Roll with the boring: build Golang/Rust GRPC services from scratch to expose your complex capabilities to the wider company in a scalable and performant manner

• This is a high impact, high agency role with direct effect on company culture, trajectory, and outcome

• You may be oncall from time to time in this 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.

• A strong understanding of distributed systems. You enjoy building fault tolerant, resilient, and scalable services

• A solid intuition about how long your solutions will last. All systems age. In startups, we can hope for 2-3 orders of magnitude, or 12-18mo.

• The tact to implement your solution, creator monitors for it’s error boundaries, and document any requirements for when you’re not around

• A great sense of direction and prioritization when it comes to dealing with the ambiguity of an early stage startup

• A sense of grit to dive into a problem, implement a solution, scale that solution, and replace it when needed

• A great set of communication skills for getting your point across, solution implemented, and beyond

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

• We're distributed ALL across the globe, and that's only going to be more and more distributed. As a result, stuff is ALWAYS happening.

• We do NOT expect you to work all the time, but you'll have to be diligent about your boundaries because the end of your day may overlap with the start of someone else's.

• We're a small team, with high ownership, who are not only passionate about what we do, but seek to be exceptional as well. At the time of writing we're 21, serving hundreds of thousands of users. There's a lot of stuff going on, and a lot of ambiguity.

• We want you to own it. We believe that ownership is a key to growth, and part of that growth is not only being able to make the choices, but owning the success, or failure, that comes with those choices.

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

• Asynchronously implement the following:

• Pre-interview: Architect a Container Provisioning Engine to power something like Railway

1. 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.

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

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

#Global