Responsibilities

• Ship the marketing site, landing pages, and campaign surfaces as code. You build them and rebuild them when the data says to.
• Instrument every public surface from first touch through signup and into activation. Expect to rebuild some of this in your first month.
• Own answer engine discoverability. Developers ask Claude and ChatGPT before they ask Google, and their coding agents increasingly ask on their behalf. Structured data, llms.txt, docs architecture, and the measurement that tells us whether any of it works.
• Run demand generation, from paid acquisition and lifecycle through the pipeline that turns a first visit into a sales conversation. You decide where budget goes and you own the number.
• Run social in the places engineers actually are, using agents to move fast and your own taste to decide what ships.
• Build internal agents that remove manual work from campaign operations, content production, competitive monitoring, and reporting. You own them after they ship, including when a third-party API breaks at 2am.
• Choose the stack, consolidate what overlaps, and keep the cost of your own automation in view.

Requirements

• You have shipped web applications end to end: with users, deployed, instrumented, and maintained. Show us.
• You build with coding agents as a matter of routine. Claude Code, Cursor, or equivalent, as part of how you work rather than something you have tried.
• You think about conversion, activation, and developer trust without being asked to. The marketing half of this role is judgment about metrics rather than campaign credentials.
• You have opinions about how developers evaluate infrastructure, formed by building for them or by being the developer being marketed to.
• You want to run a function alone, and you treat a team of one as an advantage.

Preferred

• Useful, not required: prior work on marketing sites, docs sites, or product-led growth surfaces at a dev tools, infrastructure, or AI company. SEO and AEO experience grounded in tests rather than theory. Familiarity with graph databases, retrieval, or agent frameworks. Technical content that engineers read to the end.