SlipstreamJobs tracks this role from the company's public career site. Apply directly on the employer's site.
Blacksmith is a high-growth infrastructure company that has built a platform to run CI workloads at scale using a global fleet of bare-metal machines. The company orchestrates tens of millions of Firecracker VMs weekly for 5,000+ customers, has achieved ~$50M ARR in 2.5 years, and recently raised $58.5M from Google Ventures and Peak XV Partners.
As Technical Storyteller, you will own the content engine and narrative strategy for the company. Your responsibilities include:
- Building and executing a reliable cadence for shipping high-quality technical content tied to product launches and engineering milestones, reducing the overhead that currently falls on engineers and founders.
- Designing launch narratives for 0-to-1 products and features, including announcements, technical explainers, and demos, working closely with the Product team to build repeatable playbooks.
- Identifying and developing customer success stories—interviewing engineering teams who have achieved dramatic improvements (e.g., order-of-magnitude CI time reductions) and translating those into compelling narratives that resonate with other engineers.
- Setting the bar for technical content in the infrastructure/CI category through deep dives, benchmarks, teardowns, comparisons, and thought-leadership essays designed to earn organic reach on platforms like Hacker News.
- Extending content across multiple formats: blog, video, YouTube, documentation, changelogs, conference talks, and company social accounts.
You bring 5+ years of experience writing for technical audiences—whether through developer media, technical content marketing, DevRel, or engineering-adjacent journalism. You have a portfolio of published work that has traveled: pieces that hit Hacker News front page, threads that got quoted, or an audience you built yourself. You understand technical concepts deeply enough to present them credibly (you don't need to be an engineer, but you're genuinely curious about infrastructure, CI, and the broader market). You can extract compelling stories from engineers who don't naturally think of themselves as storytellers, reading design docs and pull requests to identify theses and asking the right questions to build content. You write with a point of view—you'd rather publish something arguable than something safe. You're very online, following Hacker News, X, and developer communities, with instincts about what will resonate. You work with autonomy; there's no manager, brief, or pre-set calendar—you decide what's worth writing.
