How Railway Interviews in 2026: Process, Sample Questions & What They Score

Railway describes this stage on its job pages as "completely open ended and we're just trying to see who you are, what you want to do, and where you wanna go." (exact wording, from the full-stack posting). No duration is published. The same stage name and position (stage 1 of 6) appears on product, infrastructure (all three variants), DevRel and growth postings.

Railway asks candidates to do the work on their own time before the call, so the effort varies by role and by how far you take the build. Product/full-stack: "Build an application to spin up and spin down a container using our GQL API", with a UI and not just a backend calling the API, deployed on Railway before the interview. Infra platform: "Architect a Container Provisioning Engine to power something like Railway". Bare-metal orchestration: design an orchestration engine for a system managing stateless and stateful compute workloads. Observability: design an observability engine for a compute-workload system. Scalability: pick one of a usage metering and billing pipeline for millions of workloads, or a stream-processing system for high-cardinality observability events. DevRel: build and deploy a project on Railway using several of its features. Growth: "Build, and present, a campaign to move Railway's top-of-funnel forward." Several postings (scalability, growth-marketer, orchestration-baremetal, platform-engineer-instrumentation) explicitly say candidates may or should ask clarifying questions before starting, in the words "You can, and SHOULD! ask us questions ahead of time. Ask away!" on scalability and growth-marketer.

Railway publishes the agenda under the same heading as the work sample ("Work on a small project to discuss in the interview"). Product/full-stack version: 0-5 minutes introductions, 5-35 minutes walking through the code and how you would extend it, 35-50 minutes "Noodling on technology, frameworks, how you think about product", 50-60 minutes for your questions. Infrastructure and observability version: 0-5m introduction, 5-50m "Building (or expanding) your solution" (orchestration-baremetal specifies this as a 45-minute block), 50-60m questions on Railway and tech. DevRel version: 0-5m introduction, 5-20m project walkthrough, 20-50m content strategy and cross-functional collaboration, 50-60m your questions. Stated aim: "Learn about your problem solving skills. How you break down a problem and how you present a solution."

Published wording (exact, from the full-stack posting): "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." So one reviewer plus two additional team members. No duration is published, and the postings do not say whether this is one session or several.

Published wording (exactly as it appears in the full-stack posting): "You'll meet the Team, which will be comprised of 4 people from vastly different sections of the company." Stated criterion is "How you work with the rest of the team and communicate", not further technical depth. Non-engineers are in the room.

Published wording (exactly as it appears in the full-stack posting): "Sit down with our founder and CEO for 30 minutes. This is a 1:1, open ended conversation." Same stage on every posting cited, engineering and non-engineering.

Published wording (exactly as it appears in the full-stack posting): "Finally, we will present the offers, hammer out the details about your position, tee up onboarding, and start our journey together." Railway's own writing describes onboarding as a customised 6 to 8 week plan in three two-week phases (Tasks, then Problems, then Opportunities), with the goal that "Nail onboarding and we trust you to tackle new problems within 4 weeks."