Build and run the content engine. We are constantly working on complex infrastructure problems and have a lot of features to launch this year, but there's no machinery yet for turning launches and engineering work into content on a reliable cadence. Today that overhead falls on engineers and founders, which means it often doesn't happen at all. You'll build the machine and own the cadence, so a regular stream of high-quality technical content ships.
Design how we launch. We're shipping several 0-to-1 products and features this year and each needs a narrative: the announcement, the docs-adjacent explainers, the demos. You'll work closely with the Product team to build up this playbook and reduce the overhead with every launch.
Turn customers into stories. We have engineering teams who cut their CI times by an order of magnitude. Find those stories, interview these teams and write compelling content that other engineers will naturally draw parallels to in their own work.
Set the bar for technical content in this category. Deep dives, benchmarks, teardowns, comparisons, the occasional argumentative essay. Things that get to the front page of Hacker News on merit.
Extend past the blog. Video, YouTube, docs, changelog, conference talks, the company account. Whatever format the story actually needs.
You're a good fit if you
Have 5+ years writing for a technical audience - developer media, technical content marketing, DevRel, or engineering-adjacent journalism.
Have published work that traveled: pieces that hit the front page of Hacker News, threads that got quoted, posts engineers send each other, or an audience you built yourself. We will ask for links to get to better know your style of writing.
Understand technical concepts deeply enough to present them credibly. You don't need to be an engineer, but you're genuinely curious about what we're building and the wider market.
Can pull a story out of engineers who don't think of themselves as storytellers. You can read a design doc or a pull request and come out with a thesis, and you ask questions to build a content piece.
Write with a point of view. We'd rather publish something arguable than something safe.
Are very online: you follow the right channels, know what's moving through Hacker News, X, and developer social chatter, and catch things early. You have instincts about what will work and what won't.
