Job description
Our core mission at Railway is to let developers create, ship and operate software with minimal friction. Fundamental to that mission is an array of rock-solid and composable primitives, principal among these - storage.
As a Storage Engineer you will build, evolve and operate the systems that allow Railway to host stateful workloads. Railway operates across multiple colocation datacenters and large fleets of cloud VMs. This demands we build high-availability primitives that “work anywhere” and that can migrate between different environments with minimal (ideally zero) downtime. Moving storage is the hardest challenge in this task, and it has required us to invest in building custom systems from first-principles.
You will principally be working on our new log structured block-storage system that is designed for performance, high-density and high-availability across cloud and baremetal environments.
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).
Curious? Here are 3 blog posts that dive into exciting projects this team has worked on: 1, 2, 3
For this role, you will:
Lead the development of Railway's block storage systems
Support the operation of storage systems and participate in on-call rotations
Drive the specification of storage server hardware
Build systems to support capacity planning
Design and build interfaces with orchestration services to support coordinated workflows such as on-line backups and zero-downtime/live workload migration
Write Engineering Requirement Documents to take something from idea, to defined tasks, to implementation, to monitoring its success
Set the longer-term architectural direction to scale the platform
This is a high impact, high agency role with direct effect on company culture, trajectory, and outcome.
You should meet one or more of the following requirements:
You've built and operated distributed storage systems and have a strong grasp of first-principles.
You have strong systems engineering experience in one or more of: filesystems, block devices, kernel I/O paths, SPDK, io_uring, vhost-user-blk, ublk or virtualization
You have a deep understanding of the algorithms and techniques behind building fast, performant and reliable storage systems.
You have experience building large distributed systems where consistency and availability was critical.
You have a strong background in performance engineering at the I/O layer on Linux.
You have strong foundation in systems programming with Rust.
You're comfortable owning a problem alone at a small company.
You have 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-18 months.
You have the grit to dive into a problem, implement a solution, scale that solution, and replace it when needed.
You communicate well enough to get your point across, your solution implemented, and documented for when you're not around.
If your background is in adjacent infrastructure (hypervisor I/O, kernel development, distributed systems, persistent memory) and you want to apply that depth to storage, we want to hear from 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.
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.
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:
Autonomy: We have very few meetings. Just a Monday and a Friday to go over the Company Board. We think your time is sacred, whether it's at work, or outside of work.
Ownership: We're a company with a high ownership, high autonomy culture. We hope that you'll come in, help us, and over the course of many years do the best work of your life. When we bring you onboard, we expect you to change the company.
Novel problems/solutions: We're a startup that's well funded, with cool problems, which lets us implement novel solutions! We abhor “busywork” and think, whether it's community, engineering, operations, etc there's always opportunity for creative and high leverage solutions.
Growth: We want you to grow with us, but we know that talent is loaned, so when you figure out what area you want to grow in next, whether it's at Railway or outside, we'll make sure you land there.
How we hire
No tricks. No surprises. Here's the entire process:
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.
Work on a small project to discuss in the interview
Asynchronously implement the following:
Pre-interview: Design a Storage Engine to power something like Railway's Volume
You can, and SHOULD! ask us questions ahead of time.
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):
Prework (submitted before your interview): Complete your solution
0-5m: introduction
5-50m: Building (or expanding) your solution
50-60m: Questions on Railway/Tech/etc
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.
Offer and Details Chat with CEO
Finally, we will go over the process, the role, and hammer out the details about your position, onboarding, and all the deets.
#Global
","descriptionPlain":"Job description\n\nOur core mission at Railway is to let developers create, ship and operate software with minimal friction. Fundamental to that mission is an array of rock-solid and composable primitives, principal among these - storage.\n\nAs a Storage Engineer you will build, evolve and operate the systems that allow Railway to host stateful workloads. Railway operates across multiple colocation datacenters and large fleets of cloud VMs. This demands we build high-availability primitives that “work anywhere” and that can migrate between different environments with minimal (ideally zero) downtime. Moving storage is the hardest challenge in this task, and it has required us to invest in building custom systems from first-principles.\n\nYou will principally be working on our new log structured block-storage system that is designed for performance, high-density and high-availability across cloud and baremetal environments.\n\nWant 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 https://blog.railway.app/p/how-we-work, 2 https://blog.railway.app/p/how-we-work-volume-ii, 3 https://blog.railway.app/p/how-we-work-volume-iii, and 4 https://blog.railway.com/p/how-we-work-volume-iv).\n\nCurious? Here are 3 blog posts that dive into exciting projects this team has worked on: 1 https://blog.railway.com/p/launch-week-01-scale-to-zero, 2 https://blog.railway.com/p/data-center-build-part-one, 3 https://blog.railway.com/p/data-center-build-part-two\n\n\n\n\nABOUT THE ROLE\n\nFor this role, you will:\n\n - Lead the development of Railway's block storage systems\n\n - Support the operation of storage systems and participate in on-call rotations\n\n - Drive the specification of storage server hardware\n\n - Build systems to support capacity planning\n\n - Design and build interfaces with orchestration services to support coordinated workflows such as on-line backups and zero-downtime/live workload migration\n\n - Write Engineering Requirement Documents to take something from idea, to defined tasks, to implementation, to monitoring its success\n\n - Set the longer-term architectural direction to scale the platform\n\nThis is a high impact, high agency role with direct effect on company culture, trajectory, and outcome.\n\n\n\n\nABOUT YOU\n\nYou should meet one or more of the following requirements:\n\n - You've built and operated distributed storage systems and have a strong grasp of first-principles.\n\n - You have strong systems engineering experience in one or more of: filesystems, block devices, kernel I/O paths, SPDK, io_uring, vhost-user-blk, ublk or virtualization\n\n - You have a deep understanding of the algorithms and techniques behind building fast, performant and reliable storage systems.\n\n - You have experience building large distributed systems where consistency and availability was critical.\n\n - You have a strong background in performance engineering at the I/O layer on Linux.\n\n - You have strong foundation in systems programming with Rust.\n\n - You're comfortable owning a problem alone at a small company.\n\n - You have 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-18 months.\n\n - You have the grit to dive into a problem, implement a solution, scale that solution, and replace it when needed.\n\n - You communicate well enough to get your point across, your solution implemented, and documented for when you're not around.\n\nIf your background is in adjacent infrastructure (hypervisor I/O, kernel development, distributed systems, persistent memory) and you want to apply that depth to storage, we want to hear from you.\n\nWe value and love to work with diverse persons from all backgrounds\n\nThings to know\n\nFor better or worse, we're a startup; our team dynamics are different from companies of different sizes and stages.\n\n - 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.\n\n - 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.\n\n - 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.\n\n - 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.\n\nBenefits and perks\n\nAt 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 https://railway.app/careers/full-stack.\n\nBeyond compensation, there are a few things that we believe that make working at Railway truly unique:\n\n - Autonomy: We have very few meetings. Just a Monday and a Friday to go over the Company Board. We think your time is sacred, whether it's at work, or outside of work.\n\n - Ownership: We're a company with a high ownership, high autonomy culture. We hope that you'll come in, help us, and over the course of many years do the best work of your life. When we bring you onboard, we expect you to change the company.\n\n - Novel problems/solutions: We're a startup that's well funded, with cool problems, which lets us implement novel solutions! We abhor “busywork” and think, whether it's community, engineering, operations, etc there's always opportunity for creative and high leverage solutions.\n\n - Growth: We want you to grow with us, but we know that talent is loaned, so when you figure out what area you want to grow in next, whether it's at Railway or outside, we'll make sure you land there.\n\nHow we hire\n\nNo tricks. No surprises. Here's the entire process:\n\n 1. Talk with us about the role\n \n - 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.\n\n 2. Work on a small project to discuss in the interview\n \n - Asynchronously implement the following:\n \n - Pre-interview: Design a Storage Engine to power something like Railway's Volume\n \n - You can, and SHOULD! ask us questions ahead of time.\n\n 3. Review your solution with the Team\n \n 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.\n \n 1. Looking for: Learn about your problem solving skills. How you break down a problem and how you present a solution.\n \n 2. Interview Structure (60 Minutes):\n \n 1. Prework (submitted before your interview): Complete your solution\n \n 2. 0-5m: introduction\n \n 3. 5-50m: Building (or expanding) your solution\n \n 4. 50-60m: Questions on Railway/Tech/etc\n\n 4. Meet the Team\n \n 1. You'll meet the Team, which will be comprised of 4 people from vastly different sections of the company.\n \n 1. Looking for: How you work with the rest of the team and communicate.\n\n 5. Offer and Details Chat with CEO\n \n 1. Finally, we will go over the process, the role, and hammer out the details about your position, onboarding, and all the deets.\n\n#Global"},{"id":"4856389c-44d8-4635-ba51-5fc1b8a49ca8","title":"Senior Infra Engineer: Observability","department":"Platform","team":"Engineering","employmentType":"FullTime","location":"Global","secondaryLocations":[],"publishedAt":"2026-05-01T22:29:07.525+00:00","isListed":true,"isRemote":true,"workplaceType":"Remote","address":{"postalAddress":{"addressRegion":"California ","addressCountry":"USA","addressLocality":"San Francisco"}},"jobUrl":"https://jobs.ashbyhq.com/railway/4856389c-44d8-4635-ba51-5fc1b8a49ca8","applyUrl":"https://jobs.ashbyhq.com/railway/4856389c-44d8-4635-ba51-5fc1b8a49ca8/application","descriptionHtml":"Job description
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.
Many infrastructure platforms simply focus on how you deploy your singular application, and now how these applications function in concert. Questions like “How do you build systems for zero downtime deployment”, “How do you do service-to-service communications”, etc are usually left up to the engineers to define.
At Railway, our goal is to be an all encompassing solution to all these problems. As such, we take special care as we define our networking infrastructure.
Note: Networking falls under the platform engineering umbrella. If you’re specialized, we’d love to chat! That said, we’d also like it noted you’re probably going to do a lot of non-networking + platform things
“But the world would be a better place if more engineers, like me, hated technology. The stuff I design, if I'm successful, nobody will ever notice. Things will just work, and will be self-managing”
- Radia Perlman
For this role, you will:
Build ingestion pipelines to consume 1M+ RPS streams of logs, metrics, and other telemetry
Build scalable, fault tolerant alerting engines for notifying users, in real-time, of threshold breaches
Craft rich backend observability APIs, working with product to build amazing experiences for instantly grokking their application
Provide APIs to access realtime log/metrics streams to be consumed by the Dashboard and Product Teams
Build Golang/Rust GRPC services from scratch capable of supporting tens of thousands of users, and the million+ to come.
Define infrastructure that can be torn down, failed over, and reconstituted from scratch using principle of immutable infrastructure using Terraform and Ansible.
Write Engineering Requirement Documents to take something from idea, to defined tasks, to implementation, to monitoring it’s success.
Interface with our TypeScript and GraphQL edge to expose your microservice APIs for both internal and potentially external consumption
This is a high impact, high agency role with direct effect on company culture, trajectory, and outcome.
A strong understanding of distributed systems. You enjoy building fault tolerant, resilient, and scalable services
Interests in VictoriaMetrics, ClickHouse, and other systems for building observability stacks from the ground up
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
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.
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.
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:
Autonomy: We have very few meetings. Just a Monday and a Friday to go over the Company Board. We think your time is sacred, whether it's at work, or outside of work.
Ownership: We're a company with a high ownership, high autonomy culture. We hope that you'll come in, help us, and over the course of many years do the best work of your life. When we bring you onboard, we expect you to change the company.
Novel problems/solutions: We're a startup that's well funded, with cool problems, which lets us implement novel solutions! We abhor “busywork” and think, whether it's community, engineering, operations, etc there's always opportunity for creative and high leverage solutions.
Growth: We want you to grow with us, but we know that talent is loaned, so when you figure out what area you want to grow in next, whether it's at Railway or outside, we'll make sure you land there.
How we hire
No tricks. No surprises. Here's the entire process:
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.
Work on a small project to discuss in the interview
Asynchronously implement the following:
Imagine a theoretical or actual system like Railway which can manage stateless and stateful compute workloads. Design the engine for managing observability
Interview Structure (60 Minutes):
Pre-work (before your interview): Complete your solution (advised)
0-5m: introduction
5-50m: Building (or expanding) your solution
50-60m: Questions on Railway/Tech/etc.
You can, and SHOULD! ask us questions ahead of time. Ask away!
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):
Prework (submitted before your interview): Complete your solution
0-5m: introduction
5-50m: Building (or expanding) your solution
50-60m: Questions on Railway/Tech/etc
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.
Offer and Details Chat with CEO
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.
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 simple to ship anything. A lot goes into that. This role bridges the universe of atoms, to the universe of bits.
We’ve built ground up infrastructure to deliver better-than-best-in-class experience to all of our users, by building datacenters all over the world.
They’re designed for performance of course, but also for resilience and reliability. Doesn’t matter how good your stuff is if it doesn’t stay up right?
“The person who says it cannot be done, should not interrupt the person doing it”
- Confucius
Curious? Learn more in our blog post about this team and the great work they’re doing: So You Want to Build Your Own Data Center
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 (1 and 2 and 3).
Expect to need all of these, day to day, to excel at Railway
Built application level code (Golang, GRPC, Postgres, etc)
Made use of OS primitives (syscalls, cgroups, etc)
Delivered projects 0→N. Lead it, scaled it, seen your “brilliant solutions” become tech debt, etc
Operated with agency and urgency (bonus points if remotely!)
Had enough foresight to ship for today, design for 10x, and engineer for 100x in 18mo
Communicated clearly using RFCs/Docs/etc to break up + deliver large, nebulous tasks
Been oncall and know that you will be 1-2 weeks per quarter
Constructed monitoring, alerts, and dashboards to notify you before things break
Built the confidence to say no to 99% of things, and the grit to deliver the 1% that matter
At Railway, we make it simple to ship anything. A lot goes into that. This role bridges the universe of atoms, to the universe of bits.
We’ve built ground up infrastructure to deliver better-than-best-in-class experience to all of our users, by building datacenters all over the world.
They’re designed for performance of course, but also for resilience and reliability. Doesn’t matter how good your stuff is if it doesn’t stay up right?
“The person who says it cannot be done, should not interrupt the person doing it”
- Confucius
Curious? Learn more in our blog post about this team and the great work they’re doing: So You Want to Build Your Own Data Center
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 (1 and 2 and 3).
Required Qualifications/Experience
Expect to need all of these, day to day, to excel at Railway
Built application level code (Golang, GRPC, Postgres, etc)
Made use of OS primitives (syscalls, cgroups, etc)
Delivered projects 0→N. Lead it, scaled it, seen your “brilliant solutions” become tech debt, etc
Operated with agency and urgency (bonus points if remotely!)
Had enough foresight to ship for today, design for 10x, and engineer for 100x in 18mo
Communicated clearly using RFCs/Docs/etc to break up + deliver large, nebulous tasks
Been oncall and know that you will be 1-2 weeks per quarter
Constructed monitoring, alerts, and dashboards to notify you before things break
Built the confidence to say no to 99% of things, and the grit to deliver the 1% that matter
Desired Qualifications/Experience
Expect to go deep in 1-2 of these to do the best work of your life
Designed and procured $1m+ hardware for datacenters
Managed and orchestrated supply chains globally
Designed rack level layouts for optimal efficiency (heat/energy/etc)
Built automated systems for inventory management up to PXE bootstrapping
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.
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.
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:
Autonomy: We have very few meetings. Just a Monday and a Friday to go over the Company Board. We think your time is sacred, whether it's at work, or outside of work.
Ownership: We're a company with a high ownership, high autonomy culture. We hope that you'll come in, help us, and over the course of many years do the best work of your life. When we bring you onboard, we expect you to change the company.
Novel problems/solutions: We're a startup that's well funded, with cool problems, which lets us implement novel solutions! We abhor “busywork” and think, whether it's community, engineering, operations, etc there's always opportunity for creative and high leverage solutions.
Growth: We want you to grow with us, but we know that talent is loaned, so when you figure out what area you want to grow in next, whether it's at Railway or outside, we'll make sure you land there.
How we hire
No tricks. No surprises. Here's the entire process:
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.
Work on a small project to discuss in the interview
Asynchronously implement the following:
Pre-interview: Design a datacenter procurement, buildout, and management process from scratch
You can, and SHOULD! ask us questions ahead of time.
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 (before your interview): Complete your solution (advised)
0-5m: introduction
5-50m: Building (or expanding) your solution
50-60m: Questions on Railway/Tech/etc
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.
Offer and Details Chat with CEO
Finally, we will go over the process, the role, and hammer out the details about your position, onboarding, and all the deets.
#Global
","descriptionPlain":"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.\n\nAt Railway, we make it simple to ship anything. A lot goes into that. This role bridges the universe of atoms, to the universe of bits.\n\nWe’ve built ground up infrastructure to deliver better-than-best-in-class experience to all of our users, by building datacenters all over the world.\n\nThey’re designed for performance of course, but also for resilience and reliability. Doesn’t matter how good your stuff is if it doesn’t stay up right?\n\n“The person who says it cannot be done, should not interrupt the person doing it”\n\n- Confucius\n\nCurious? Learn more in our blog post about this team and the great work they’re doing: So You Want to Build Your Own Data Center https://blog.railway.com/p/data-center-build-part-one\n\nWant to learn about our work culture? Here is a three-part blog series that will help you see the unique ways our team works (1 https://blog.railway.app/p/how-we-workand 2 https://blog.railway.app/p/how-we-work-volume-ii and 3 https://blog.railway.app/p/how-we-work-volume-iii).\n\n\n\n\nREQUIRED QUALIFICATIONS/EXPERIENCE\n\nExpect to need all of these, day to day, to excel at Railway\n\n 1. Built application level code (Golang, GRPC, Postgres, etc)\n\n 2. Made use of OS primitives (syscalls, cgroups, etc)\n\n 3. Delivered projects 0→N. Lead it, scaled it, seen your “brilliant solutions” become tech debt, etc\n\n 4. Operated with agency and urgency (bonus points if remotely!)\n\n 5. Had enough foresight to ship for today, design for 10x, and engineer for 100x in 18mo\n\n 6. Communicated clearly using RFCs/Docs/etc to break up + deliver large, nebulous tasks\n\n 7. Been oncall and know that you will be 1-2 weeks per quarter\n\n 8. Constructed monitoring, alerts, and dashboards to notify you before things break\n\n 9. Built the confidence to say no to 99% of things, and the grit to deliver the 1% that matter\n\n\n\nJOB DESCRIPTION\n\nAt Railway, we make it simple to ship anything. A lot goes into that. This role bridges the universe of atoms, to the universe of bits.\n\nWe’ve built ground up infrastructure to deliver better-than-best-in-class experience to all of our users, by building datacenters all over the world.\n\nThey’re designed for performance of course, but also for resilience and reliability. Doesn’t matter how good your stuff is if it doesn’t stay up right?\n\n“The person who says it cannot be done, should not interrupt the person doing it”\n\n- Confucius\n\nCurious? Learn more in our blog post about this team and the great work they’re doing: So You Want to Build Your Own Data Center https://blog.railway.com/p/data-center-build-part-one\n\nWant to learn about our work culture? Here is a three-part blog series that will help you see the unique ways our team works (1 https://blog.railway.app/p/how-we-workand 2 https://blog.railway.app/p/how-we-work-volume-ii and 3 https://blog.railway.app/p/how-we-work-volume-iii).\n\nRequired Qualifications/Experience\n\nExpect to need all of these, day to day, to excel at Railway\n\n 1. Built application level code (Golang, GRPC, Postgres, etc)\n\n 2. Made use of OS primitives (syscalls, cgroups, etc)\n\n 3. Delivered projects 0→N. Lead it, scaled it, seen your “brilliant solutions” become tech debt, etc\n\n 4. Operated with agency and urgency (bonus points if remotely!)\n\n 5. Had enough foresight to ship for today, design for 10x, and engineer for 100x in 18mo\n\n 6. Communicated clearly using RFCs/Docs/etc to break up + deliver large, nebulous tasks\n\n 7. Been oncall and know that you will be 1-2 weeks per quarter\n\n 8. Constructed monitoring, alerts, and dashboards to notify you before things break\n\n 9. Built the confidence to say no to 99% of things, and the grit to deliver the 1% that matter\n\nDesired Qualifications/Experience\n\nExpect to go deep in 1-2 of these to do the best work of your life\n\n 1. Designed and procured $1m+ hardware for datacenters\n\n 2. Managed and orchestrated supply chains globally\n\n 3. Designed rack level layouts for optimal efficiency (heat/energy/etc)\n\n 4. Built automated systems for inventory management up to PXE bootstrapping\n\nWe value and love to work with diverse persons from all backgrounds\n\nThings to know\n\nFor better or worse, we're a startup; our team dynamics are different from companies of different sizes and stages.\n\n - 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.\n\n - 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.\n\n - 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.\n\n - 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.\n\nBenefits and perks\n\nAt 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 https://railway.app/careers/full-stack.\n\nBeyond compensation, there are a few things that we believe that make working at Railway truly unique:\n\n - Autonomy: We have very few meetings. Just a Monday and a Friday to go over the Company Board. We think your time is sacred, whether it's at work, or outside of work.\n\n - Ownership: We're a company with a high ownership, high autonomy culture. We hope that you'll come in, help us, and over the course of many years do the best work of your life. When we bring you onboard, we expect you to change the company.\n\n - Novel problems/solutions: We're a startup that's well funded, with cool problems, which lets us implement novel solutions! We abhor “busywork” and think, whether it's community, engineering, operations, etc there's always opportunity for creative and high leverage solutions.\n\n - Growth: We want you to grow with us, but we know that talent is loaned, so when you figure out what area you want to grow in next, whether it's at Railway or outside, we'll make sure you land there.\n\nHow we hire\n\nNo tricks. No surprises. Here's the entire process:\n\n 1. Talk with us about the role\n \n - 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.\n\n 2. Work on a small project to discuss in the interview\n \n - Asynchronously implement the following:\n \n - Pre-interview: Design a datacenter procurement, buildout, and management process from scratch\n \n - You can, and SHOULD! ask us questions ahead of time.\n\n 3. Review your solution with the Team\n \n 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.\n \n 1. Looking for: Learn about your problem solving skills. How you break down a problem and how you present a solution.\n \n 2. Interview Structure (60 Minutes):\n \n 1. Pre-work (before your interview): Complete your solution (advised)\n \n 2. 0-5m: introduction\n \n 3. 5-50m: Building (or expanding) your solution\n \n 4. 50-60m: Questions on Railway/Tech/etc\n\n 4. Meet the Team\n \n 1. You'll meet the Team, which will be comprised of 4 people from vastly different sections of the company.\n \n 1. Looking for: How you work with the rest of the team and communicate.\n\n 5. Offer and Details Chat with CEO\n \n 1. Finally, we will go over the process, the role, and hammer out the details about your position, onboarding, and all the deets.\n\n#Global"},{"id":"5f51771e-339f-49f9-8da2-e3c7179c7bad","title":"Senior Product Engineer, Scalability","department":"Product","team":"Engineering","employmentType":"FullTime","location":"Global","secondaryLocations":[],"publishedAt":"2026-06-11T19:42:15.346+00:00","isListed":true,"isRemote":true,"workplaceType":"Remote","address":{"postalAddress":{"addressRegion":"California ","addressCountry":"USA","addressLocality":"San Francisco"}},"jobUrl":"https://jobs.ashbyhq.com/railway/5f51771e-339f-49f9-8da2-e3c7179c7bad","applyUrl":"https://jobs.ashbyhq.com/railway/5f51771e-339f-49f9-8da2-e3c7179c7bad/application","descriptionHtml":"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. Railway now powers workloads for millions of builders, and the systems underneath — usage metering, billing and payments, fraud and abuse protection, background workers, and the data pipelines that feed them all — have to scale every week.
You'll be the person who architects that stack: making it fast, correct, and trustworthy at a volume that keeps growing. If you're looking to scale the backbone of an operating system for builders, we'd love to talk with you!
Want to learn about our work culture? Here is a multi-part blog series that will help you see the unique ways our team works (Parts 1, 2, 3, and 4).
This is a backend-leaning role focused on scaling systems. Billing and fraud will be a focus, but your remit spans every high-throughput system at Railway — workers, queues, event pipelines, and the databases underneath them. You'll own your work end-to-end, including when a feature reaches the UI.
For this role, you will:
Architect and scale the pipelines that turn raw usage into accurate, real-time billing — metering, aggregation, rating, and invoicing across millions of events, from ingestion in ClickHouse to the rating engine.
Build payment flows that are correct under concurrency and partial failure: idempotent charges, retries, reconciliation, and clean handling of provider edge cases (Stripe and beyond).
Develop fraud and abuse detection — signal collection, real-time scoring, automated mitigation — that protects platform margin without getting in legitimate users' way.
Scale the systems everything else depends on: Postgres under heavy write load, Node.js services under pressure, and long-running workflows orchestrated with Temporal where exactly-once semantics and durability actually matter.
Build TypeScript + GraphQL APIs where correctness and auditability are non-negotiable.
Write Engineering Requirement Documents to take something from idea, to defined tasks, to implementation, to monitoring its success and scaling it further.
Contribute to our open-source repositories (CLI, Typescript SDK, Railpack, etc.) — Rust experience, or the desire to learn it, helps here.
Be oncall from time to time.
Some projects this team takes on:
Re-architect billing end-to-end: per-second usage metering at platform scale, idempotent payment processing that survives provider outages without double-charging, and credit, prepayment, and enterprise-invoicing models that hold up under audit.
Stand up a fraud-detection service that scores signups and deployments in real time and automatically throttles abuse (crypto mining, free-tier farming, stolen cards).
Scale our Temporal workloads to orchestrate workflows across millions of deployments.
Build internal tooling that gives teams across Railway a trustworthy, real-time view into the systems they depend on.
This is a high impact, high agency role with direct effect on company culture, trajectory, and outcome.
An ability to autonomously lead, design, and implement backend systems where correctness, consistency, and auditability are first-class requirements.
A track record of scaling systems — you've taken a pipeline, service, or database that was falling over and made it handle 10x, and you know which tools to reach for (and when polling stops being enough).
Deep expertise in Postgres and relational data modeling — you reach for the right consistency guarantees, understand the cost of getting them wrong, and know how Postgres itself behaves at scale.
Strong working knowledge of Node.js internals — the event loop, memory behavior, and what to do when a service degrades under load.
Experience managing complex asynchronous and long-running backend jobs, ideally with a workflow engine like Temporal, for things like billing runs or payment reconciliation.
Familiarity with the realities of money movement: payment providers, idempotency, retries, reconciliation, and their failure modes. Direct billing, payments, or fraud experience is a strong plus.
A security and abuse-aware mindset — you instinctively think about how a system can be gamed, and you design accordingly.
A desire to be a part of the entire project development process, from research gathering and planning, to implementation and monitoring.
Great written and verbal communication skills for expressing ideas, designs, and potential solutions in a mostly-asynchronous manner.
We value and love to work with diverse persons from all backgrounds.
For better or worse, we're a startup; our team dynamics are different from companies of different sizes and stages.
We're globally distributed—and getting more so. Stuff is always happening somewhere.
We don't expect you to be online all the time, but you'll need to be diligent about your boundaries — your end of day will overlap with someone else's start.
We're a small, high-ownership team that cares deeply about doing exceptional work. We're scaling quickly, which means we rely on leverage—systems over coordination, judgment over process. Expect ambiguity and a fast-moving environment.
You'll own real outcomes. That means making decisions, not just executing—and owning the success, or failure, that comes with them.
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 make working at Railway truly unique:
Autonomy: We have very few meetings. Just a Monday and a Friday to go over the Company Board. We think your time is sacred, whether it's at work, or outside of work.
Ownership: We're a company with a high ownership, high autonomy culture. We hope that you'll come in, help us, and over the course of many years do the best work of your life. When we bring you onboard, we expect you to change the company.
Novel problems/solutions: We're a startup that's well funded, with cool problems, which lets us implement novel solutions! We abhor \"busywork\" and think, whether it's community, engineering, operations, etc there's always opportunity for creative and high leverage solutions.
Growth: We want you to grow with us, but we know that talent is loaned, so when you figure out what area you want to grow in next, whether it's at Railway or outside, we'll make sure you land there.
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 design a system that scales. You choose the domain — pick whichever shows your thinking best:
A usage metering and billing pipeline that meters CPU/RAM for millions of workloads and bills accurately (you may depend on third parties such as Stripe), or
A stream-processing system that ingests high-cardinality observability events in real time, or
Whatever you pick, come ready to defend the architecture end-to-end. We'll dig into:
Polling vs. stream processing, and how you avoid losing data when streaming
Correctness under concurrency and partial failure: idempotency, retries, reconciliation, what happens when a step fails halfway through
How you handle cardinality, and which tools you lean on and why
The scalability of the things you depend on — what happens when Postgres becomes the bottleneck
Interview Structure to expect (60 Minutes):
Prework (submitted before your interview): Your design
0–5 minutes: Introductions
5–35 minutes: Walking through the design and how you'd extend it — new failure modes, 10x load, a fraud signal
35–50 minutes: Noodling on technology, data modeling, and how you think about scale, money-movement, and abuse
50–60 minutes: Time for you to ask your interviewers questions
You can, and SHOULD! ask us questions ahead of time. Ask away!
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.
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 — Chat with CEO
Sit down with our founder and CEO for 30 minutes. This is a 1:1, open ended conversation.
6 — Offer call
Finally, we will present the offers, hammer out the details about your position, tee up onboarding, and start our journey together.
Final Note: The interview goes both ways. Once again, please ask us things. Many things! Hard things. That's what we're here for.
","descriptionPlain":"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. Railway now powers workloads for millions of builders, and the systems underneath — usage metering, billing and payments, fraud and abuse protection, background workers, and the data pipelines that feed them all — have to scale every week.\n\nYou'll be the person who architects that stack: making it fast, correct, and trustworthy at a volume that keeps growing. If you're looking to scale the backbone of an operating system for builders, we'd love to talk with you!\n\nWant to learn about our work culture? Here is a multi-part blog series that will help you see the unique ways our team works (Parts 1 https://blog.railway.app/p/how-we-work, 2 https://blog.railway.app/p/how-we-work-volume-ii, 3 https://blog.railway.app/p/how-we-work-volume-iii, and 4 https://blog.railway.com/p/how-we-work-volume-iv).\n\n\nABOUT THE ROLE\n\nThis is a backend-leaning role focused on scaling systems. Billing and fraud will be a focus, but your remit spans every high-throughput system at Railway — workers, queues, event pipelines, and the databases underneath them. You'll own your work end-to-end, including when a feature reaches the UI.\n\nFor this role, you will:\n\n - Architect and scale the pipelines that turn raw usage into accurate, real-time billing — metering, aggregation, rating, and invoicing across millions of events, from ingestion in ClickHouse to the rating engine.\n\n - Build payment flows that are correct under concurrency and partial failure: idempotent charges, retries, reconciliation, and clean handling of provider edge cases (Stripe and beyond).\n\n - Develop fraud and abuse detection — signal collection, real-time scoring, automated mitigation — that protects platform margin without getting in legitimate users' way.\n\n - Scale the systems everything else depends on: Postgres under heavy write load, Node.js services under pressure, and long-running workflows orchestrated with Temporal where exactly-once semantics and durability actually matter.\n\n - Build TypeScript + GraphQL APIs where correctness and auditability are non-negotiable.\n\n - Write Engineering Requirement Documents to take something from idea, to defined tasks, to implementation, to monitoring its success and scaling it further.\n\n - Contribute to our open-source repositories (CLI, Typescript SDK, Railpack, etc.) — Rust experience, or the desire to learn it, helps here.\n\n - Be oncall from time to time.\n\nSome projects this team takes on:\n\n - Re-architect billing end-to-end: per-second usage metering at platform scale, idempotent payment processing that survives provider outages without double-charging, and credit, prepayment, and enterprise-invoicing models that hold up under audit.\n\n - Stand up a fraud-detection service that scores signups and deployments in real time and automatically throttles abuse (crypto mining, free-tier farming, stolen cards).\n\n - Scale our Temporal workloads to orchestrate workflows across millions of deployments.\n\n - Build internal tooling that gives teams across Railway a trustworthy, real-time view into the systems they depend on.\n\nThis is a high impact, high agency role with direct effect on company culture, trajectory, and outcome.\n\n\nABOUT YOU\n\n - An ability to autonomously lead, design, and implement backend systems where correctness, consistency, and auditability are first-class requirements.\n\n - A track record of scaling systems — you've taken a pipeline, service, or database that was falling over and made it handle 10x, and you know which tools to reach for (and when polling stops being enough).\n\n - Deep expertise in Postgres and relational data modeling — you reach for the right consistency guarantees, understand the cost of getting them wrong, and know how Postgres itself behaves at scale.\n\n - Strong working knowledge of Node.js internals — the event loop, memory behavior, and what to do when a service degrades under load.\n\n - Experience managing complex asynchronous and long-running backend jobs, ideally with a workflow engine like Temporal, for things like billing runs or payment reconciliation.\n\n - Familiarity with the realities of money movement: payment providers, idempotency, retries, reconciliation, and their failure modes. Direct billing, payments, or fraud experience is a strong plus.\n\n - A security and abuse-aware mindset — you instinctively think about how a system can be gamed, and you design accordingly.\n\n - A desire to be a part of the entire project development process, from research gathering and planning, to implementation and monitoring.\n\n - Great written and verbal communication skills for expressing ideas, designs, and potential solutions in a mostly-asynchronous manner.\n\nWe value and love to work with diverse persons from all backgrounds.\n\n\nTHINGS TO KNOW\n\nFor better or worse, we're a startup; our team dynamics are different from companies of different sizes and stages.\n\n - We're globally distributed—and getting more so. Stuff is always happening somewhere.\n\n - We don't expect you to be online all the time, but you'll need to be diligent about your boundaries — your end of day will overlap with someone else's start.\n\n - We're a small, high-ownership team that cares deeply about doing exceptional work. We're scaling quickly, which means we rely on leverage—systems over coordination, judgment over process. Expect ambiguity and a fast-moving environment.\n\n - You'll own real outcomes. That means making decisions, not just executing—and owning the success, or failure, that comes with them.\n\n\nBENEFITS AND PERKS\n\nAt 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 https://railway.com/careers.\n\nBeyond compensation, there are a few things that we believe make working at Railway truly unique:\n\n - Autonomy: We have very few meetings. Just a Monday and a Friday to go over the Company Board. We think your time is sacred, whether it's at work, or outside of work.\n\n - Ownership: We're a company with a high ownership, high autonomy culture. We hope that you'll come in, help us, and over the course of many years do the best work of your life. When we bring you onboard, we expect you to change the company.\n\n - Novel problems/solutions: We're a startup that's well funded, with cool problems, which lets us implement novel solutions! We abhor \"busywork\" and think, whether it's community, engineering, operations, etc there's always opportunity for creative and high leverage solutions.\n\n - Growth: We want you to grow with us, but we know that talent is loaned, so when you figure out what area you want to grow in next, whether it's at Railway or outside, we'll make sure you land there.\n\n\nHOW WE HIRE\n\nNo tricks. No surprises. Here's the entire process.\n\n1 — Talk with us about the role\n\nThis is completely open ended and we're just trying to see who you are, what you want to do, and where you wanna go.\n\n2 — Work on a small project to discuss in the interview\n\nAsynchronously design a system that scales. You choose the domain — pick whichever shows your thinking best:\n\n - A usage metering and billing pipeline that meters CPU/RAM for millions of workloads and bills accurately (you may depend on third parties such as Stripe), or\n\n - A stream-processing system that ingests high-cardinality observability events in real time, or\n\n - \n\nWhatever you pick, come ready to defend the architecture end-to-end. We'll dig into:\n\n - Polling vs. stream processing, and how you avoid losing data when streaming\n\n - Correctness under concurrency and partial failure: idempotency, retries, reconciliation, what happens when a step fails halfway through\n\n - How you handle cardinality, and which tools you lean on and why\n\n - The scalability of the things you depend on — what happens when Postgres becomes the bottleneck\n\n - Interview Structure to expect (60 Minutes):\n \n - Prework (submitted before your interview): Your design\n \n - 0–5 minutes: Introductions\n \n - 5–35 minutes: Walking through the design and how you'd extend it — new failure modes, 10x load, a fraud signal\n \n - 35–50 minutes: Noodling on technology, data modeling, and how you think about scale, money-movement, and abuse\n \n - 50–60 minutes: Time for you to ask your interviewers questions\n\nYou can, and SHOULD! ask us questions ahead of time. Ask away!\n\n3 — Review your solution with the Team\n\nYou'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.\n\nLooking for: Learn about your problem solving skills. How you break down a problem and how you present a solution.\n\n4 — Meet the Team\n\nYou'll meet the Team, which will be comprised of 4 people from vastly different sections of the company.\n\nLooking for: How you work with the rest of the team and communicate.\n\n5 — Chat with CEO\n\nSit down with our founder and CEO for 30 minutes. This is a 1:1, open ended conversation.\n\n6 — Offer call\n\nFinally, we will present the offers, hammer out the details about your position, tee up onboarding, and start our journey together.\n\nFinal Note: The interview goes both ways. Once again, please ask us things. Many things! Hard things. That's what we're here for."},{"id":"6ddcfe47-6cce-469b-ba6d-4f0e83440c9d","title":"Senior Full-Stack Engineer - Product","department":"Product","team":"Engineering","employmentType":"FullTime","location":"Remote (United States)","secondaryLocations":[],"publishedAt":"2024-02-07T20:30:20.299+00:00","isListed":true,"isRemote":true,"workplaceType":"Remote","address":{"postalAddress":{"addressCountry":"United States"}},"jobUrl":"https://jobs.ashbyhq.com/railway/6ddcfe47-6cce-469b-ba6d-4f0e83440c9d","applyUrl":"https://jobs.ashbyhq.com/railway/6ddcfe47-6cce-469b-ba6d-4f0e83440c9d/application","descriptionHtml":"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.
At Railway, we believe that making tooling more accessible for build and deployment is one of the greatest possible productivity unlocks of our generation. We also believe that the major roadblock between us and our goal is strong interfacing paradigms.
If you’re looking to build an operating system for builders, we’d love to talk with you!
Curious? Learn more in our blog post about this team and the great work they’re doing: Team Spotlight: Product Engineering (https://blog.railway.app/p/team-spotlight-product-engineering)
For this role, you will:
Build features end-to-end, from the UI in our dashboard to orchestrating workflows that interact with our microservices using Temporal.
Craft intuitive interfaces that allow our users to interface with powerful computing paradigms, with help from our design team.
Build TypeScript + GraphQL APIs with strong guarantees around modeling data, allowing both internal and external users to build against.
Write Engineering Requirement Documents to take something from idea, to defined tasks, to implementation, to monitoring it’s success.
Experience with, or at least the desire to learn Rust to contribute to our open-source repositories (CLI, Nixpacks, etc).
Some projects full-stack engineers have worked on in the past
Rebuild logging infrastructure to support 1B logs/day, from configuring ClickHouse to developing a brand new observability UI
Build Git for infrastructure and re-thinking how a project evolves over time
Build a tool for building user code into a deployable image using Nix packages. (github.com/railwayapp/nixpacks)
Create interfaces to visualize project infrastructure on a 2D canvas
Add support for migrating deployments with a volume from one region to another using Temporal
Create a marketplace for users to share re-usable pieces of infrastructure
This is a high impact, high agency role with direct effect on company culture, trajectory, and outcome.
An ability to autonomously lead, design, and implement great product experiences, from front to back.
A strong understanding of frontend architecture to build interactivity-rich systems for fetching, mutating, and rendering data effectively
Experience managing complex asynchronous backend jobs for something like a build/deploy pipeline.
A desire to be a part of the entire project development process. From research gathering and planning, to implementation and monitoring
Great written and verbal communication skills for expressing ideas, designs, and potential solutions in mostly-asynchronous manner
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.
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.
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:
Autonomy: We have very few meetings. Just a Monday and a Friday to go over the Company Board. We think your time is sacred, whether it's at work, or outside of work.
Ownership: We're a company with a high ownership, high autonomy culture. We hope that you'll come in, help us, and over the course of many years do the best work of your life. When we bring you onboard, we expect you to change the company.
Novel problems/solutions: We're a startup that's well funded, with cool problems, which lets us implement novel solutions! We abhor “busywork” and think, whether it's community, engineering, operations, etc there's always opportunity for creative and high leverage solutions.
Growth: We want you to grow with us, but we know that talent is loaned, so when you figure out what area you want to grow in next, whether it's at Railway or outside, we'll make sure you land there.
How we hire
No tricks. No surprises. Here's the entire process:
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.
Work on a small project to discuss in the interview
Asynchronously implement the following:
Build an application to spin up and spin down a container using our GQL API. Please deploy on Railway before the interview and we will review the code during your interview. The app needs to have a UI component and not just a backend that uses the API.
You will submit your solution before the interview, and 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.
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 a member 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 to expect when you review with the team (60 Minutes):
0-5 minutes: Introductions
5-35 minutes: Walking through the code, talking about how you’d extend it
35-50 minutes: Noodling on technology, frameworks, how you think about product
50-60 minutes: Time for you to ask your interviewers question
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.
Offer and Details Chat with CEO
Finally, we will go over the process, the role, and hammer out the details about your position, onboarding, and all the deets.
#Global
","descriptionPlain":"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.\n\nOur 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.\n\nAt Railway, we believe that making tooling more accessible for build and deployment is one of the greatest possible productivity unlocks of our generation. We also believe that the major roadblock between us and our goal is strong interfacing paradigms.\n\nIf you’re looking to build an operating system for builders, we’d love to talk with you!\n\nCurious? Learn more in our blog post about this team and the great work they’re doing: Team Spotlight: Product Engineering (https://blog.railway.app/p/team-spotlight-product-engineering)\n\n\n\n\nABOUT THE ROLE\n\nFor this role, you will:\n\n - Build features end-to-end, from the UI in our dashboard to orchestrating workflows that interact with our microservices using Temporal.\n\n - Craft intuitive interfaces that allow our users to interface with powerful computing paradigms, with help from our design team.\n\n - Build TypeScript + GraphQL APIs with strong guarantees around modeling data, allowing both internal and external users to build against.\n\n - Write Engineering Requirement Documents to take something from idea, to defined tasks, to implementation, to monitoring it’s success.\n\n - Experience with, or at least the desire to learn Rust to contribute to our open-source repositories (CLI, Nixpacks https://nixpacks.com/docs, etc).\n\nSome projects full-stack engineers have worked on in the past\n\n - Rebuild logging infrastructure https://blog.railway.app/p/launch-week-01-observability to support 1B logs/day, from configuring ClickHouse to developing a brand new observability UI\n\n - Build Git for infrastructure https://blog.railway.app/p/launch-week-01-changesets and re-thinking how a project evolves over time\n\n - Build a tool for building user code into a deployable image using Nix packages. (github.com/railwayapp/nixpacks) http://github.com/railwayapp/nixpacks\n\n - Create interfaces to visualize project infrastructure on a 2D canvas https://community.railway.app/discuss/thread/service-groups-c1faed81\n\n - Add support for migrating deployments with a volume from one region to another using Temporal\n\n - Create a marketplace https://railway.app/templates for users to share re-usable pieces of infrastructure\n\nThis is a high impact, high agency role with direct effect on company culture, trajectory, and outcome.\n\n\n\n\nABOUT YOU\n\n - An ability to autonomously lead, design, and implement great product experiences, from front to back.\n\n - A strong understanding of frontend architecture to build interactivity-rich systems for fetching, mutating, and rendering data effectively\n\n - Experience managing complex asynchronous backend jobs for something like a build/deploy pipeline.\n\n - A desire to be a part of the entire project development process. From research gathering and planning, to implementation and monitoring\n\n - Great written and verbal communication skills for expressing ideas, designs, and potential solutions in mostly-asynchronous manner\n\nWe value and love to work with diverse persons from all backgrounds\n\nThings to know\n\nFor better or worse, we're a startup; our team dynamics are different from companies of different sizes and stages.\n\n - 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.\n\n - 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.\n\n - 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.\n\n - 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.\n\nBenefits and perks\n\nAt 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 https://railway.app/careers/full-stack.\n\nBeyond compensation, there are a few things that we believe that make working at Railway truly unique:\n\n - Autonomy: We have very few meetings. Just a Monday and a Friday to go over the Company Board. We think your time is sacred, whether it's at work, or outside of work.\n\n - Ownership: We're a company with a high ownership, high autonomy culture. We hope that you'll come in, help us, and over the course of many years do the best work of your life. When we bring you onboard, we expect you to change the company.\n\n - Novel problems/solutions: We're a startup that's well funded, with cool problems, which lets us implement novel solutions! We abhor “busywork” and think, whether it's community, engineering, operations, etc there's always opportunity for creative and high leverage solutions.\n\n - Growth: We want you to grow with us, but we know that talent is loaned, so when you figure out what area you want to grow in next, whether it's at Railway or outside, we'll make sure you land there.\n\nHow we hire\n\nNo tricks. No surprises. Here's the entire process:\n\n 1. Talk with us about the role\n \n - 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.\n\n 2. Work on a small project to discuss in the interview\n \n - Asynchronously implement the following:\n \n - Build an application to spin up and spin down a container using our GQL API. Please deploy on Railway before the interview and we will review the code during your interview. The app needs to have a UI component and not just a backend that uses the API.\n \n - You will submit your solution before the interview, and 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.\n \n - You can, and SHOULD! ask us questions ahead of time.\n\n 3. Review your solution with the Team\n \n 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 a member of the team.\n \n 1. Looking for: Learn about your problem solving skills. How you break down a problem and how you present a solution.\n \n 2. Interview Structure to expect when you review with the team (60 Minutes):\n \n 3. 0-5 minutes: Introductions\n \n 4. 5-35 minutes: Walking through the code, talking about how you’d extend it\n \n 5. 35-50 minutes: Noodling on technology, frameworks, how you think about product\n \n 6. 50-60 minutes: Time for you to ask your interviewers question\n\n 4. Meet the Team\n \n 1. You'll meet the Team, which will be comprised of 4 people from vastly different sections of the company.\n \n 1. Looking for: How you work with the rest of the team and communicate.\n\n 5. Offer and Details Chat with CEO\n \n 1. Finally, we will go over the process, the role, and hammer out the details about your position, onboarding, and all the deets.\n\n#Global"},{"id":"6fb07755-acd8-4400-9de3-fa598e4eeb7d","title":"Product Designer","department":"Product","team":"Product","employmentType":"FullTime","location":"Remote (United States)","secondaryLocations":[],"publishedAt":"2025-11-03T23:54:45.950+00:00","isListed":true,"isRemote":true,"workplaceType":"Remote","address":{"postalAddress":{"addressCountry":"United States"}},"jobUrl":"https://jobs.ashbyhq.com/railway/6fb07755-acd8-4400-9de3-fa598e4eeb7d","applyUrl":"https://jobs.ashbyhq.com/railway/6fb07755-acd8-4400-9de3-fa598e4eeb7d/application","descriptionHtml":"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.
By building tooling for infrastructure automation, we seek to make people 100x more effective, and build 100x more impactful systems. Building leverage is a core part of what we do.
We’re seeking a versatile and seasoned Product Designer who strives to create great products, loves collaborating, and takes the initiative. The ideal candidate will derive satisfaction from ideating, designing, and delivering exceptional solutions to hundreds of thousands of developers. This position is tailored for a well-rounded professional who appreciates the art of creative thinking but places equal importance on witnessing their ideas come to life.
“Products are made in a factory but brands are created in the mind.” - Walter Landor
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
Play a pivotal role in Railway's developer experience, redefining the future of software infrastructure.
Collaborate closely with product, support, and engineering to scope, define, design, and ship high-quality features.
Contribute to the overall design direction of the product, leveraging your creativity and problem-solving skills to address complex design challenges and deliver elegant solutions.
Balance user needs, business goals, and technical constraints of design solutions, ensuring that Railway remains user-friendly, scalable, and reliable.
Define workflows, prototypes, and visual design of your projects.
Learn about our users, how they use our platform, understand their pain points, and propose projects to fix them.
Help us maintain and evolve our internal Design System
Work in an ambiguous environment to create levers for design excellence, using process sparingly but effectively.
Contribute to the design culture within the company.
About you
You have a strong portfolio showcasing your skills in user interface design, interaction design, and visual design. Your portfolio demonstrates your ability to solve complex design problems and showcases your attention to detail.
You care about creating good products, understand what makes a good experience, and constantly think of improvement opportunities for the products you use.
You care about business needs, implications, and the practicality of your solutions and work to deliver clear, intuitive, and appealing human interfaces.
You are a creative thinker who can push the boundaries of design while ensuring a balance between user needs, business goals, and technical constraints.
You feel comfortable designing, illustrating, iterating, and prototyping in Figma, but always look for new tools to open new possibilities (Blender, Spline, Rive, shaders, etc.).
You have experience balancing trade-offs while implementing a feature to ship it on time without compromising the long-term product vision.
You have experience effectively collaborating with cross-functional teams to deliver high-quality designs within project timelines.
You have excellent communication skills and can articulate design decisions and rationale effectively to stakeholders and team members.
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.
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.
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:
Autonomy: We have very few meetings. Just a Monday and a Friday to go over the Company Board. We think your time is sacred, whether it's at work, or outside of work.
Ownership: We're a company with a high ownership, high autonomy culture. We hope that you'll come in, help us, and over the course of many years do the best work of your life. When we bring you onboard, we expect you to change the company.
Novel problems/solutions: We're a startup that's well funded, with cool problems, which lets us implement novel solutions! We abhor “busywork” and think, whether it's community, engineering, operations, etc there's always opportunity for creative and high leverage solutions.
Growth: We want you to grow with us, but we know that talent is loaned, so when you figure out what area you want to grow in next, whether it's at Railway or outside, we'll make sure you land there.
How we hire
No tricks. No surprises. Here's the entire process.
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.
Work on a small project to discuss in the interview
Review the Railway product and identify one improvement (a redesign of an existing area or a new feature that extends functionality). Then, implement one workflow to illustrate your idea—using either Figma screens, a clickable prototype, or code.
Deliverable: One workflow in Figma screens, a Figma prototype, or an implementation in code that communicates your vision and design quality.
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.
You can, and SHOULD! ask us questions ahead of time. What our prior solution looks like, what ideas we have to improve it, etc. Ask away!
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.
Offer and Details Chat with CEO
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.
","descriptionPlain":"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.\n\nBy building tooling for infrastructure automation, we seek to make people 100x more effective, and build 100x more impactful systems. Building leverage is a core part of what we do.\n\nWe’re seeking a versatile and seasoned Product Designer who strives to create great products, loves collaborating, and takes the initiative. The ideal candidate will derive satisfaction from ideating, designing, and delivering exceptional solutions to hundreds of thousands of developers. This position is tailored for a well-rounded professional who appreciates the art of creative thinking but places equal importance on witnessing their ideas come to life.\n\n“Products are made in a factory but brands are created in the mind.” - Walter Landor\n\nWant 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 https://blog.railway.app/p/how-we-work, 2 https://blog.railway.app/p/how-we-work-volume-ii, 3 https://blog.railway.app/p/how-we-work-volume-iii, and 4 https://blog.railway.com/p/how-we-work-volume-iv)\n\nAbout the role\n\n - Play a pivotal role in Railway's developer experience, redefining the future of software infrastructure.\n\n - Collaborate closely with product, support, and engineering to scope, define, design, and ship high-quality features.\n\n - Contribute to the overall design direction of the product, leveraging your creativity and problem-solving skills to address complex design challenges and deliver elegant solutions.\n\n - Balance user needs, business goals, and technical constraints of design solutions, ensuring that Railway remains user-friendly, scalable, and reliable.\n\n - Define workflows, prototypes, and visual design of your projects.\n\n - Learn about our users, how they use our platform, understand their pain points, and propose projects to fix them.\n\n - Help us maintain and evolve our internal Design System\n\n - Work in an ambiguous environment to create levers for design excellence, using process sparingly but effectively.\n\n - Contribute to the design culture within the company.\n\nAbout you\n\n - You have a strong portfolio showcasing your skills in user interface design, interaction design, and visual design. Your portfolio demonstrates your ability to solve complex design problems and showcases your attention to detail.\n\n - You care about creating good products, understand what makes a good experience, and constantly think of improvement opportunities for the products you use.\n\n - You care about business needs, implications, and the practicality of your solutions and work to deliver clear, intuitive, and appealing human interfaces.\n\n - You are a creative thinker who can push the boundaries of design while ensuring a balance between user needs, business goals, and technical constraints.\n\n - You feel comfortable designing, illustrating, iterating, and prototyping in Figma, but always look for new tools to open new possibilities (Blender, Spline, Rive, shaders, etc.).\n\n - You have experience balancing trade-offs while implementing a feature to ship it on time without compromising the long-term product vision.\n\n - You have experience effectively collaborating with cross-functional teams to deliver high-quality designs within project timelines.\n\n - You have excellent communication skills and can articulate design decisions and rationale effectively to stakeholders and team members.\n\nWe value and love to work with diverse persons from all backgrounds\n\nThings to know\n\nFor better or worse, we're a startup; our team dynamics are different from companies of different sizes and stages.\n\n - 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.\n\n - 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.\n\n - 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.\n\n - 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.\n\nBenefits and perks\n\nAt 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 https://railway.app/careers/Product-designer.\n\nBeyond compensation, there are a few things that we believe that make working at Railway truly unique:\n\n - Autonomy: We have very few meetings. Just a Monday and a Friday to go over the Company Board. We think your time is sacred, whether it's at work, or outside of work.\n\n - Ownership: We're a company with a high ownership, high autonomy culture. We hope that you'll come in, help us, and over the course of many years do the best work of your life. When we bring you onboard, we expect you to change the company.\n\n - Novel problems/solutions: We're a startup that's well funded, with cool problems, which lets us implement novel solutions! We abhor “busywork” and think, whether it's community, engineering, operations, etc there's always opportunity for creative and high leverage solutions.\n\n - Growth: We want you to grow with us, but we know that talent is loaned, so when you figure out what area you want to grow in next, whether it's at Railway or outside, we'll make sure you land there.\n\nHow we hire\n\nNo tricks. No surprises. Here's the entire process.\n\n 1. Talk with us about the role\n \n - 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.\n\n 2. Work on a small project to discuss in the interview\n \n 1. Review the Railway product and identify one improvement (a redesign of an existing area or a new feature that extends functionality). Then, implement one workflow to illustrate your idea—using either Figma screens, a clickable prototype, or code.\n \n 2. Deliverable: One workflow in Figma screens, a Figma prototype, or an implementation in code that communicates your vision and design quality.\n \n 3. 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.\n \n 4. You can, and SHOULD! ask us questions ahead of time. What our prior solution looks like, what ideas we have to improve it, etc. Ask away!\n\n 3. Meet the Team\n \n 1. You'll meet the Team, which will be comprised of 4 people from vastly different sections of the company.\n \n 2. Looking for: How you work with the rest of the team and communicate.\n\n 4. Offer and Details Chat with CEO\n \n 1. Finally, we will go over the process, the role, and hammer out the details about your position, onboarding, and all the deets.\n\nFinal Note: The interview goes both ways. Once again, please ask us things. Many things! Hard things. That's what we're here for."},{"id":"7d42f0e8-15a5-453d-8992-9e8638846077","title":"Developer Relations","department":"Product","team":"Engineering","employmentType":"FullTime","location":"Remote (United States)","secondaryLocations":[],"publishedAt":"2024-12-02T21:09:38.607+00:00","isListed":true,"isRemote":true,"workplaceType":"Remote","address":{"postalAddress":{"addressCountry":"United States"}},"jobUrl":"https://jobs.ashbyhq.com/railway/7d42f0e8-15a5-453d-8992-9e8638846077","applyUrl":"https://jobs.ashbyhq.com/railway/7d42f0e8-15a5-453d-8992-9e8638846077/application","descriptionHtml":"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:
Implement programs to gather developer feedback and then exercise discretion on how to best communicate to those users
Build and refine product adoption loops through content, improvements to the product, and nurturing community
Assist the team on initiatives around our Open Source presence such as our CLI, Nixpacks, and Templates
Craft resources that help grow the developer ecosystem and ensure that the experience for new and existing users is as seamless as possible
About you
A strong ability to communicate clearly, whether it's via writing, video, or practical projects incorporating Railway
A enthusiast about our product, Railway uses Railway to build Railway. (Say that 5 times fast) You should be able to share insights with developers of all stripes to let them know how our product can help them
A great sense of direction and prioritization when it comes to dealing with the ambiguity of an early stage startup
Someone who is comfortable in a few different languages/stacks and can create educational content on how to deploy those projects on a public cloud (the status quo) or Railway (the thing we hope to be better than the status quo)
Able to take really technical concepts and make it as easy to understand as possible
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.
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.
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:
Autonomy: We have very few meetings. Just a Monday and a Friday to go over the Company Board. We think your time is sacred, whether it's at work, or outside of work.
Ownership: We're a company with a high ownership, high autonomy culture. We hope that you'll come in, help us, and over the course of many years do the best work of your life. When we bring you onboard, we expect you to change the company.
Novel problems/solutions: We're a startup that's well funded, with cool problems, which lets us implement novel solutions! We abhor “busywork” and think, whether it's community, engineering, operations, etc there's always opportunity for creative and high leverage solutions.
Growth: We want you to grow with us, but we know that talent is loaned, so when you figure out what area you want to grow in next, whether it's at Railway or outside, we'll make sure you land there.
How We Hire
No tricks. No surprises. Here's the entire process.
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.
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.
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
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.
Offer and Details Chat with CEO
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
","descriptionPlain":"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.\n\n\n\nAt 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.\n\nDev 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.\n\nThis 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.\n\nWant 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 https://blog.railway.app/p/how-we-work, 2 https://blog.railway.app/p/how-we-work-volume-ii, 3 https://blog.railway.app/p/how-we-work-volume-iii, and 4 https://blog.railway.com/p/how-we-work-volume-iv).\n\n\n\nAbout the role\n\nFor this role, you will:\n\n - Implement programs to gather developer feedback and then exercise discretion on how to best communicate to those users\n\n - Build and refine product adoption loops through content, improvements to the product, and nurturing community\n\n - Assist the team on initiatives around our Open Source presence such as our CLI, Nixpacks, and Templates\n\n - Craft resources that help grow the developer ecosystem and ensure that the experience for new and existing users is as seamless as possible\n\nAbout you\n\n - A strong ability to communicate clearly, whether it's via writing, video, or practical projects incorporating Railway\n\n - A enthusiast about our product, Railway uses Railway to build Railway. (Say that 5 times fast) You should be able to share insights with developers of all stripes to let them know how our product can help them\n\n - A great sense of direction and prioritization when it comes to dealing with the ambiguity of an early stage startup\n\n - Someone who is comfortable in a few different languages/stacks and can create educational content on how to deploy those projects on a public cloud (the status quo) or Railway (the thing we hope to be better than the status quo)\n\n - Able to take really technical concepts and make it as easy to understand as possible\n\nWe value and love to work with diverse persons from all backgrounds\n\n\n\nThings to Know\n\nFor better or worse, we're a startup; our team dynamics are different from companies of different sizes and stages.\n\n - 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.\n\n - 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.\n\n - 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.\n\n - 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.\n\n\n\nBenefits and Perks\n\nAt 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 https://railway.app/careers/developer-relations.\n\nBeyond compensation, there are a few things that we believe that make working at Railway truly unique:\n\n - Autonomy: We have very few meetings. Just a Monday and a Friday to go over the Company Board. We think your time is sacred, whether it's at work, or outside of work.\n\n - Ownership: We're a company with a high ownership, high autonomy culture. We hope that you'll come in, help us, and over the course of many years do the best work of your life. When we bring you onboard, we expect you to change the company.\n\n - Novel problems/solutions: We're a startup that's well funded, with cool problems, which lets us implement novel solutions! We abhor “busywork” and think, whether it's community, engineering, operations, etc there's always opportunity for creative and high leverage solutions.\n\n - Growth: We want you to grow with us, but we know that talent is loaned, so when you figure out what area you want to grow in next, whether it's at Railway or outside, we'll make sure you land there.\n\n\n\nHow We Hire\n\nNo tricks. No surprises. Here's the entire process.\n\n 1. Talk with us about the role\n \n - 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.\n\n 2. Work on a small project to discuss in the interview\n \n - Asynchronously implement the following:\n \n - Build something and deploy it on Railway using as many features as possible\n \n - 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.\n \n - You can, and SHOULD ask us questions ahead of time if you have them.\n\n 3. Review your solution with the Team\n \n - 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.\n \n - Looking for: Learn about your problem solving skills. How you break down a problem and how you present a solution.\n \n - Interview Structure (60 Minutes):\n \n - Pre-work (submitted before your interview): Build and deploy your project\n \n - 0-5 minutes: Introduction\n \n - 5-20 minutes: Walking through the project\n \n - 20-50 minutes: Walking through how you think about content, relations, intersection with other roles\n \n - 50-60 minutes: Time for you to ask your interviewers questions\n\n 4. Meet the Team\n \n - You'll meet the Team, which will be comprised of 4 people from vastly different sections of the company.\n \n - Looking for: How you work with the rest of the team and communicate.\n\n 5. Offer and Details Chat with CEO\n \n 1. Finally, we will go over the process, the role, and hammer out the details about your position, onboarding, and all the deets.\n\nFinal Note: The interview goes both ways. Once again, please ask us things. Many things! Hard things. That's what we're here for.\n\n#Global"},{"id":"b8072f95-043f-404d-a313-f0bdf8dd3c81","title":"Infrastructure Engineer","department":"Platform","team":"Platform","employmentType":"FullTime","location":"Remote (United States)","secondaryLocations":[],"publishedAt":"2024-06-03T19:11:47.266+00:00","isListed":true,"isRemote":true,"workplaceType":"Remote","address":{"postalAddress":{"addressCountry":"United States"}},"jobUrl":"https://jobs.ashbyhq.com/railway/b8072f95-043f-404d-a313-f0bdf8dd3c81","applyUrl":"https://jobs.ashbyhq.com/railway/b8072f95-043f-404d-a313-f0bdf8dd3c81/application","descriptionHtml":"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
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
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.
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.
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:
Autonomy: We have very few meetings. Just a Monday and a Friday to go over the Company Board. We think your time is sacred, whether it's at work, or outside of work.
Ownership: We're a company with a high ownership, high autonomy culture. We hope that you'll come in, help us, and over the course of many years do the best work of your life. When we bring you onboard, we expect you to change the company.
Novel problems/solutions: We're a startup that's well funded, with cool problems, which lets us implement novel solutions! We abhor “busywork” and think, whether it's community, engineering, operations, etc there's always opportunity for creative and high leverage solutions.
Growth: We want you to grow with us, but we know that talent is loaned, so when you figure out what area you want to grow in next, whether it's at Railway or outside, we'll make sure you land there.
How we hire
No tricks. No surprises. Here's the entire process:
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.
Work on a small project to discuss in the interview
Asynchronously implement the following:
Pre-interview: Architect a Container Provisioning Engine to power something like Railway
You can, and SHOULD! ask us questions ahead of time.
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):
Prework (submitted before your interview): Complete your solution
0-5m: introduction
5-50m: Building (or expanding) your solution
50-60m: Questions on Railway/Tech/etc
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.
Offer and Details Chat with CEO
Finally, we will go over the process, the role, and hammer out the details about your position, onboarding, and all the deets.
#Global
","descriptionPlain":"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.\n\nOur 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.\n\nBuilding 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!\n\n\n\n\nABOUT THE ROLE\n\nFor this role, you will:\n\n - 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\n\n - 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\n\n - 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\n\n - 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\n\n - This is a high impact, high agency role with direct effect on company culture, trajectory, and outcome\n\n - You may be oncall from time to time in this role\n\n\nABOUT YOU\n\n - A strong understanding of distributed systems. You enjoy building fault tolerant, resilient, and scalable services\n\n - 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.\n\n - The tact to implement your solution, creator monitors for it’s error boundaries, and document any requirements for when you’re not around\n\n - A great sense of direction and prioritization when it comes to dealing with the ambiguity of an early stage startup\n\n - A sense of grit to dive into a problem, implement a solution, scale that solution, and replace it when needed\n\n - A great set of communication skills for getting your point across, solution implemented, and beyond\n\nWe value and love to work with diverse persons from all backgrounds\n\nThings to know\n\nFor better or worse, we're a startup; our team dynamics are different from companies of different sizes and stages.\n\n - 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.\n\n - 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.\n\n - 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.\n\n - 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.\n\nBenefits and perks\n\nAt 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 https://railway.app/careers/full-stack.\n\nBeyond compensation, there are a few things that we believe that make working at Railway truly unique:\n\n - Autonomy: We have very few meetings. Just a Monday and a Friday to go over the Company Board. We think your time is sacred, whether it's at work, or outside of work.\n\n - Ownership: We're a company with a high ownership, high autonomy culture. We hope that you'll come in, help us, and over the course of many years do the best work of your life. When we bring you onboard, we expect you to change the company.\n\n - Novel problems/solutions: We're a startup that's well funded, with cool problems, which lets us implement novel solutions! We abhor “busywork” and think, whether it's community, engineering, operations, etc there's always opportunity for creative and high leverage solutions.\n\n - Growth: We want you to grow with us, but we know that talent is loaned, so when you figure out what area you want to grow in next, whether it's at Railway or outside, we'll make sure you land there.\n\nHow we hire\n\nNo tricks. No surprises. Here's the entire process:\n\n 1. Talk with us about the role\n \n - 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.\n\n 2. Work on a small project to discuss in the interview\n \n - Asynchronously implement the following:\n \n - Pre-interview: Architect a Container Provisioning Engine to power something like Railway\n \n - You can, and SHOULD! ask us questions ahead of time.\n\n 3. Review your solution with the Team\n \n 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.\n \n 1. Looking for: Learn about your problem solving skills. How you break down a problem and how you present a solution.\n \n 2. Interview Structure (60 Minutes):\n \n 1. Prework (submitted before your interview): Complete your solution\n \n 2. 0-5m: introduction\n \n 3. 5-50m: Building (or expanding) your solution\n \n 4. 50-60m: Questions on Railway/Tech/etc\n\n 4. Meet the Team\n \n 1. You'll meet the Team, which will be comprised of 4 people from vastly different sections of the company.\n \n 1. Looking for: How you work with the rest of the team and communicate.\n\n 5. Offer and Details Chat with CEO\n \n 1. Finally, we will go over the process, the role, and hammer out the details about your position, onboarding, and all the deets.\n\n#Global"},{"id":"d93c8794-6058-4295-83a0-092b05664f34","title":"Senior Infra Engineer: Baremetal Orchestration","department":"Platform","team":"Engineering","employmentType":"FullTime","location":"Global","secondaryLocations":[],"publishedAt":"2026-05-08T22:14:58.650+00:00","isListed":true,"isRemote":true,"workplaceType":"Remote","address":{"postalAddress":{"addressRegion":"California ","addressCountry":"USA","addressLocality":"San Francisco"}},"jobUrl":"https://jobs.ashbyhq.com/railway/d93c8794-6058-4295-83a0-092b05664f34","applyUrl":"https://jobs.ashbyhq.com/railway/d93c8794-6058-4295-83a0-092b05664f34/application","descriptionHtml":"Job description
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.
Many infrastructure platforms simply focus on how you deploy your singular application, and now how these applications function in concert. Questions like “How do you build systems for zero downtime deployment”, “How do you do service-to-service communications”, etc are usually left up to the engineers to define.
At Railway, our goal is to be an all encompassing solution to all these problems. As such, we take special care as we define our networking infrastructure.
“But the world would be a better place if more engineers, like me, hated technology. The stuff I design, if I'm successful, nobody will ever notice. Things will just work, and will be self-managing”
- Radia Perlman
About the role
For this role, you will:
Build and maintain our host provisioning stack: PXE boot, Ansible, and burn-in agents that bring new bare metal online quickly and confidently
Continue to evolve our homegrown orchestration engine to manage clusters, containers, and VMs through a single lens
Optimize the efficiency of our bin packing algorithm to maximize utilization/performance and minimize costs
Own the internal tooling that Railway engineers use to interact with our fleet every day
Build out internal observability and alerting so we catch fleet problems before customers feel them
Design and maintain the CI pipelines that ship our infrastructure code safely
Define infrastructure that can be torn down, failed over, and reconstituted from scratch using principle of immutable infrastructure using Terraform and Ansible
Build Golang/Rust GRPC services from scratch capable of supporting millions of users
Write Engineering Requirement Documents to take something from idea, to defined tasks, to implementation, to monitoring its success
The arc of this role is more internal-facing than user-facing. You're building the platform that Railway engineers run on. This is a high impact, high agency role with direct effect on company culture, trajectory, and outcome.
About you
A strong understanding of distributed systems and what it takes to operate them. You enjoy building fault tolerant, resilient, and scalable services, and you care about what happens when they break at 3am
Hands-on experience with bare metal provisioning, configuration management, and the unglamorous-but-critical work of getting hardware production-ready
Comfort building and operating internal tools. You understand that developer experience inside the company matters as much as the product outside it
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, create monitors for its 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
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.
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.
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:
Autonomy: We have very few meetings. Just a Monday and a Friday to go over the Company Board. We think your time is sacred, whether it's at work, or outside of work.
Ownership: We're a company with a high ownership, high autonomy culture. We hope that you'll come in, help us, and over the course of many years do the best work of your life. When we bring you onboard, we expect you to change the company.
Novel problems/solutions: We're a startup that's well funded, with cool problems, which lets us implement novel solutions! We abhor “busywork” and think, whether it's community, engineering, operations, etc there's always opportunity for creative and high leverage solutions.
Growth: We want you to grow with us, but we know that talent is loaned, so when you figure out what area you want to grow in next, whether it's at Railway or outside, we'll make sure you land there.
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:
Imagine a theoretical or actual system like Railway which can manage stateless and stateful compute workloads. Design the engine for managing orchestration
Interview Structure (60 Minutes):
Pre-work (before your interview): Complete your solution (advised)
0-5m: introduction
5-50m: Building (or expanding) your solution
50-60m: Questions on Railway/Tech/etc
You can, and SHOULD! ask us questions ahead of time. Ask away!
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.
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) Chat with CEO
Sit down with our founder and CEO for 30 minutes. This is a 1:1, open ended conversation.
6) Offer call
Finally, we will present the offers, hammer out the details about your position, tee up onboarding, and start our journey together.
Final Note: The interview goes both ways. Once again, please ask us things. Many things! Hard things. That's what we're here for.
","descriptionPlain":"Job description\n\nOur 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.\n\nMany infrastructure platforms simply focus on how you deploy your singular application, and now how these applications function in concert. Questions like “How do you build systems for zero downtime deployment”, “How do you do service-to-service communications”, etc are usually left up to the engineers to define.\n\nAt Railway, our goal is to be an all encompassing solution to all these problems. As such, we take special care as we define our networking infrastructure.\n\n“But the world would be a better place if more engineers, like me, hated technology. The stuff I design, if I'm successful, nobody will ever notice. Things will just work, and will be self-managing”\n\n- Radia Perlman\n\nAbout the role\n\nFor this role, you will:\n\n - Build and maintain our host provisioning stack: PXE boot, Ansible, and burn-in agents that bring new bare metal online quickly and confidently\n\n - Continue to evolve our homegrown orchestration engine to manage clusters, containers, and VMs through a single lens\n\n - Optimize the efficiency of our bin packing algorithm to maximize utilization/performance and minimize costs\n\n - Own the internal tooling that Railway engineers use to interact with our fleet every day\n\n - Build out internal observability and alerting so we catch fleet problems before customers feel them\n\n - Design and maintain the CI pipelines that ship our infrastructure code safely\n\n - Define infrastructure that can be torn down, failed over, and reconstituted from scratch using principle of immutable infrastructure using Terraform and Ansible\n\n - Build Golang/Rust GRPC services from scratch capable of supporting millions of users\n\n - Write Engineering Requirement Documents to take something from idea, to defined tasks, to implementation, to monitoring its success\n\nThe arc of this role is more internal-facing than user-facing. You're building the platform that Railway engineers run on. This is a high impact, high agency role with direct effect on company culture, trajectory, and outcome.\n\nAbout you\n\n - A strong understanding of distributed systems and what it takes to operate them. You enjoy building fault tolerant, resilient, and scalable services, and you care about what happens when they break at 3am\n\n - Hands-on experience with bare metal provisioning, configuration management, and the unglamorous-but-critical work of getting hardware production-ready\n\n - Comfort building and operating internal tools. You understand that developer experience inside the company matters as much as the product outside it\n\n - 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\n\n - The tact to implement your solution, create monitors for its error boundaries, and document any requirements for when you're not around\n\n - A great sense of direction and prioritization when it comes to dealing with the ambiguity of an early stage startup\n\n - A sense of grit to dive into a problem, implement a solution, scale that solution, and replace it when needed\n\n - A great set of communication skills for getting your point across, solution implemented, and beyond\n\nWe value and love to work with diverse persons from all backgrounds\n\nThings to know\n\nFor better or worse, we're a startup; our team dynamics are different from companies of different sizes and stages.\n\n - 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.\n\n - 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.\n\n - 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.\n\n - 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.\n\nBenefits and perks\n\nAt 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 https://railway.com/careers.\n\nBeyond compensation, there are a few things that we believe that make working at Railway truly unique:\n\n - Autonomy: We have very few meetings. Just a Monday and a Friday to go over the Company Board. We think your time is sacred, whether it's at work, or outside of work.\n\n - Ownership: We're a company with a high ownership, high autonomy culture. We hope that you'll come in, help us, and over the course of many years do the best work of your life. When we bring you onboard, we expect you to change the company.\n\n - Novel problems/solutions: We're a startup that's well funded, with cool problems, which lets us implement novel solutions! We abhor “busywork” and think, whether it's community, engineering, operations, etc there's always opportunity for creative and high leverage solutions.\n\n - Growth: We want you to grow with us, but we know that talent is loaned, so when you figure out what area you want to grow in next, whether it's at Railway or outside, we'll make sure you land there.\n\nHow we hire\n\nNo tricks. No surprises. Here's the entire process.\n\n1) Talk with us about the role\n\nThis is completely open ended and we're just trying to see who you are, what you want to do, and where you wanna go.\n\n2) Work on a small project to discuss in the interview\n\nAsynchronously implement the following:\n\n - Imagine a theoretical or actual system like Railway which can manage stateless and stateful compute workloads. Design the engine for managing orchestration\n\n - Interview Structure (60 Minutes):\n\n - Pre-work (before your interview): Complete your solution (advised)\n\n - 0-5m: introduction\n\n - 5-50m: Building (or expanding) your solution\n\n - 50-60m: Questions on Railway/Tech/etc\n\nYou can, and SHOULD! ask us questions ahead of time. Ask away!\n\n3) Review your solution with the Team\n\nYou'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.\n\nLooking for: Learn about your problem solving skills. How you break down a problem and how you present a solution.\n\n4) Meet the Team\n\nYou'll meet the Team, which will be comprised of 4 people from vastly different sections of the company.\n\nLooking for: How you work with the rest of the team and communicate.\n\n5) Chat with CEO\n\nSit down with our founder and CEO for 30 minutes. This is a 1:1, open ended conversation.\n\n6) Offer call\n\nFinally, we will present the offers, hammer out the details about your position, tee up onboarding, and start our journey together.\n\nFinal Note: The interview goes both ways. Once again, please ask us things. Many things! Hard things. That's what we're here for."}],"apiVersion":"1"}