AI Content Engineer

Responsibilities

• Own content at Soda, end to end.
• The Role The website. Technical blogs, webinars, and product videos. Your own content and following.
• You're expected to get it out of heads and onto the internet, at a volume that is only possible with a machine behind it.
• You need to be able to write and you need to be able to build.

Requirements

• 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.