New job at Railway!

I started working at Railway!

Well, since April 20th, technically. I’ve just been too busy having fun to write about it.

Why I Joined Railway

If you’ve even briefly talked with me about software, you’ll know I’ve been a Railway fan for years. Beyond just loving the product, a huge part of why I took the role is how Railway thinks about support. Railway treats support as a core signal for product work.

“Support can’t be a bolt-on or an afterthought. Good support is necessary for good product because they’re the same thing.”

• myself, rambling about this to you in the past

Railway is one of the few places I’ve seen actually own this ethos.

I get to talk directly to users, spot recurring friction, and help turn those patterns into product improvements. To me, support is the product’s exception handling: every thread is signal about where the product could be clearer, smoother, or more resilient.

Railway has written about this exact philosophy too: Support Engineering Is Engineering.

What I’ve Been Working On

I’m on week 8 of my onboarding and have been having a blast. The team has been incredibly kind and generous with their time, and I feel privileged to have the opportunity to build alongside everyone.

So far, the majority of my work has been on improving our workflows around abuse detection, mitigation, and resolution. I won’t get into the specifics, but it has been a fantastic opportunity to learn and grow as an engineer in the context of devtooling, security, and automation.

I’ve also been working on docs and QA for our sandboxes primitive, which has been a ton of fun.

What’s Next

More building! I’ll share more about what I’m building as time goes on.