zlacker

>>whoish+(OP)
Railway | engineering, design | Remote | https://railway.app/careers

Tired of trying to beat kube into shape? Does writing YAML to ship code fill you with utter dread? Dream of a future where deploying software is simple, and you don't need an army of infrastructure engineers to build that perfect janky bash script™ to make life easy?

We're Railway, and we think infrastructure can be better. So far we've built out a platform loved by hundreds of thousands of users who simply tell us "Give me Postgres", "Deploy this repo", and we make it happen

Fair warning! The problems are complex: home-rolled hypervisors, cut-above container orchestration, over/under/whateverlay networks, virtio device drivers, edge proxies, IAM that doesn't suck, kitchen sinks - we need to build it and we're looking for likeminded individuals who think this stuff is fun.

If that sounds like you, please apply at railway.app/careers. We have a number of roles, but are prioritizing the following four roles:

+Platform Engineer - General

+Platform Engineer - Orchestration

+Support Engineer/Technical Writer

+Brand Designer

See you soon, and happy shipping.

>>kollma+P9
I don't see pay range(s) listed for the open roles. Not sure how many employees you have, but at least in California, if you have 15 or more, you have to disclose a pay range in the job listing. Colorado has a similar laws. New York's takes effect in September 2023 (and applies to 4 or more employees).

>>tedyou+Dk
Great point, this is also true about other states now. I've noticed generally only large multinationals are listing salary ranges online, smaller companies aren't doing that and they resist when you ask. In Colorado and Washington State you are also required supposed to do this now too.