About the roleSlash is, at its core, a technology company, and we have one of the best engineering teams in the world building infrastructure that moves over $10b a year. The problem is, almost nobody knows it yet. We're looking for a Technical Writer to change that.
You'll be the voice of Slash engineering: turning the hard, interesting things our team ships into writing that engineers actually want to read, and working closely with our engineers and founders to turn their ideas into published writing. This role blends real technical understanding with sharp writing instincts. You'll go deep on what we're building, find the stories worth telling, and ship them fast, cleanly, and with ownership.
What you'll do- Own our engineering blog end to end, from sitting with an engineer to understand what they shipped, to publishing a post that does it justice
- Turn our engineers' and founders' ideas into polished blog posts, technical deep dives, launch write-ups, and social content (LinkedIn/X), written in their voice, not a generic corporate one
- Make it effortless for our team to get their ideas out. When an engineer has something they want to write about but no time to sit down and do it, you turn it into something even better than they'd have written themselves
- Help our team post strategically across socials, amplifying the work worth highlighting rather than posting for the sake of volume
- Embed with the eng team, follow what's being built, and proactively hunt down the stories worth telling rather than waiting to be handed them
- Work directly with engineering, product, and design to make sure what we publish is technically correct and genuinely compelling
We're looking for someone who- Genuinely understands technical work, enough to write about systems, tradeoffs, and architecture without hand-waving or getting it wrong. A background in engineering, CS, or serious technical writing is a requirement
- Writes clearly and with a point of view, and can translate an engineer's rough ideas into sharp, publishable writing without losing their voice
- Knows how to write for engineers, not at them, no fluff, just clear writing that respects the reader's intelligence
- Thrives working independently in a small team that ships fast, you go find the stories rather than waiting for a content calendar
- Bonus: has written technical content that engineers actually shared, whether a blog, docs, a newsletter, or their own posts
What's in it for you- Opportunity for high growth
- High autonomy + ownership culture
- Comprehensive health + benefits plan
- Working out of our downtown San Francisco office space
- Unlimited PTO
