Growth Content Engineer

This is a remote position available anywhere in the world! Linkedin makes us show a country, but we hire the best people wherever they are. 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 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). 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.

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

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

• 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!

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

• You can, and SHOULD ask us questions ahead of time if you have them. 3. Review your solution with the Team - You'll sit down with someone on the team and go over the above. We'll poke into your solution, as well as get you acquainted with two more members of the team.
• Looking for: Learn about your problem solving skills.

• Interview Structure (60 Minutes): - Pre-work (submitted before your interview): Build and deploy your project - 0-5 minutes: Introduction - 5-20 minutes: Walking through the project - 20-50 minutes: Walking through how you think about content, relations, intersection with other roles - 50-60 minutes: Time for you to ask your interviewers questions 4.

• Looking for: How you work with the rest of the team and communicate. 5. Offer and Details Chat with CEO 1. Finally, we will go over the process, the role, and hammer out the details about your position, onboarding, and all the deets.

- Highlight Your Communication Skills: Showcase your ability to communicate complex technical ideas in a simple, clear manner.

• Demonstrate Your Passion for Developer Tools: Share your vision for the future of DevTools and how you think Railway's product fits into that landscape.
• Prepare Examples of Your Work: Come ready to discuss specific projects or content you've created that demonstrate your technical and communication skills.
• Research Railway's Culture: Understand the company's values and work culture to show your enthusiasm and fit.
• Be Ready to Discuss Ambiguity and Prioritization: Share how you handle ambiguous situations and prioritize tasks in a fast-paced, distributed work environment.
• Ask About Growth Opportunities: Inquire about how the company supports professional growth and development in the role.
• Discuss Your Experience with Remote Work: If applicable, share your experience working in distributed teams and how you manage your time and boundaries effectively.