Responsibilities

• The Role The website. Technical blogs, webinars, and product videos. Your own content and following.
• One person cannot hand-make all of that. So you'll build the system that can. That isn't a stretch goal or a second phase - we don't think the job exists without it.
• You'll join the Growth team reporting to a co-founder.
• What you might call yourself. Content engineer, technical content marketer, growth engineer, marketing engineer, GTM engineer, developer advocate, technical writer who got bored, or nothing in particular. We've seen this job posted under every one of those. We don't care what's on your CV. You need to be able to write and you need to be able to build, and almost nobody can do both.
• Your job is to get it out of their heads and onto the internet, at a volume that is only possible with a machine behind it.
• The engine has to write in distinct voices: a founder sounds nothing like a customer engineer, and the output should sound like them, not like a model. Your own profile and following is part of how we'll know it works. If it can't make you sound good, it won't make anyone else sound good either.
• What this is not. You'll write code every day, but this is not a software engineering job. We're not hiring you to build product, and if you're a backend, data, or platform engineer looking for your next engineering role, this isn't it. It's also not a traditional marketing or DevRel role: no agency to brief and no conference circuit.

Requirements

• You can write, and you can tell good writing from bad: send us something you wrote that a technical audience actually read. The most important line in this ad.
• Serious prompt engineering: multi-step LLM pipelines with structured outputs and evals, not chatting with a model. You know why the naive version produces slop.
• 3+ years building things that go to market: technical content, growth engineering, marketing engineering, GTM engineering, DevRel, marketing ops, RevOps, or a founder background. Nobody agrees what to call this job yet. Titles vary; portfolios don't.
• Enough code to be autonomous: Python or TypeScript, APIs, webhooks, a database. Nothing should be blocked waiting for an engineer. We build agentically here - Claude Code, MCP servers, and agent skills are the daily workflow.
• Enough data fluency to be credible: you're writing for Staff Data Engineers and CDOs. You can hold your own on pipelines, data quality, and warehouses.
• Generalist instinct: you find the constraint and fix it, and you'd rather build the workflow than do the task fifteen more times.
• Independence: you don't need hand-holding in a distributed, async team across 12+ countries.
• Fluent English.

Preferred

• You've grown a technical audience of your own: newsletter, blog, LinkedIn, open source, YouTube.
• Content, growth, or DevRel in data, developer tools, or infrastructure.
• Agentic workflows shipped to real users: MCP servers, Claude skills, tool-using agents.
• You can shoot and cut video yourself.
• Data quality, data management, or data observability industry experience.

Benefits

• Fully remote (US or EU-based), with offices in Brooklyn if you want one.
• All the tokens you need, across all frontier models.
• Real ownership, real impact, no micromanagement.
• Colleagues in 12+ countries.