Technical Storyteller

Blacksmith•New York, NY

8d•$150,000 - $180,000

About The Position

Blacksmith is a rapidly growing company that started by building infrastructure to run CI workloads very fast. Their first product helps companies run GitHub Actions faster and cheaper by operating their own global fleet of bare-metal machines. They currently orchestrate tens of millions of Firecracker VMs weekly, running CI for over 5,000 companies and achieving approximately $50 million in ARR within 2.5 years. The company operates thousands of bare-metal machines across multiple regions, schedules over 100,000 vCPUs concurrently, and manages a petabyte-scale Ceph cluster. Blacksmith has raised $58.5 million from Seed to Series B, with funding led by Google Ventures (GV) and Peak XV Partners. The founding team has extensive experience in systems and scaling, including work at Faire and Cockroach Labs. The Go-To-Market strategy is led by Jon Boyer, formerly Head of Sales at Zapier. The company is now expanding its CI infrastructure into a broader platform, focusing on running agent sandboxes at scale and developing its own background coding agent.

Requirements

5+ years of experience writing for a technical audience (developer media, technical content marketing, DevRel, or engineering-adjacent journalism).
A portfolio of published work that has gained traction (e.g., front page of Hacker News, widely quoted threads, posts shared among engineers, or a self-built audience).
Sufficient understanding of technical concepts to present them credibly; genuine curiosity about the company's technology and market.
Ability to extract stories from engineers who may not consider themselves storytellers, by reading design documents, pull requests, and asking insightful questions.
A distinct point of view in writing, preferring arguable content over safe content.
Deep familiarity with online developer communities, including Hacker News, X (formerly Twitter), and general developer social chatter, with an instinct for what resonates.
Ability to work autonomously, deciding what content is worth creating without a manager or predefined brief.

Responsibilities

Build and run the content engine, establishing a reliable cadence for content creation around product launches and engineering work.
Design the launch strategy for new products and features, creating narratives, announcement materials, explainers, and demos.
Identify and interview customers to gather stories about significant engineering achievements (e.g., order-of-magnitude CI time reductions) and write compelling content.
Set the standard for technical content in the company's category through deep dives, benchmarks, teardowns, comparisons, and opinionated essays.
Extend content beyond the blog to include video, YouTube, documentation, changelogs, conference talks, and social media.