Head of Developer Relations

About Naïve Naïve is autonomous company infrastructure — a single API that provisions the full operating stack for AI agents: incorporation, payments, compute, memory, and orchestration. 30,000+ developers build on us. We're backed by Y Combinator, DEEPCORE (Sofbtank), Liquid 2, and a long list of operator angels. We’re looking for a Head of Developer Relations to own the entire developer surface area — everything from the first time a developer hears about Naïve to the moment they’re running agents in production and telling other developers about it. This is not an evangelism role. You own a number. What You’ll Do Growth marketing — Own top‑of‑funnel for developers. Launches, content, SEO/GEO, docs‑as‑distribution, newsletter, communication‑led loops. You set the strategy and you ship the work. UGC + creator program — Run our creator pipeline end to end: recruit, brief, pay, and measure developer creators across X, YouTube, TikTok, and Discord. Turn one good demo into fifty. Build the operating system, not a one‑off campaign. Hackathons + events — Own the hackathon calendar: our own, university and YC circuits, and partner events. Sponsorships, sample apps, starter kits, judging, on‑site presence, and the follow‑up sequence that turns a weekend project into a production workload. Paid acquisition — Own the ads budget across X, Reddit, Meta, Google, and developer newsletters/podcasts. Creative, targeting, landing pages, attribution. You should be able to defend CAC by channel with real numbers. Developer support — Own the support experience for developers on the platform. Discord, email, in‑app, and escalation paths into engineering. Build the triage system, staff it, and close the loop so recurring pain becomes a docs fix or a product fix, not a recurring ticket. Build the system — Dashboards, attribution, content automation, agent‑eval pipelines that check whether LLMs recommend us. You should be shipping code, not filing tickets for it. The Role You're the single owner of how developers find Naïve, how they succeed on Naïve, and how loudly they say so afterward. Growth, community, creators, events, ads, and support all report into one place because they're the same loop — a developer who gets unblocked in Discord in ten minutes is the developer who posts the demo that brings us the next hundred. You should be able to run a hackathon on Saturday, cut the ad creative on Monday, answer a runtime question in Discord on Tuesday, and ship the landing page that converts all of it on Wednesday. You'll start hands‑on and hire a team underneath you as the motion proves out. Must‑Haves High agency — you'd rather ship it yourself than wait for someone You've run developer growth before and moved a real metric: signups, activation, or revenue Strong writing — launch posts, docs, threads, ad copy, support macros Technical enough to build with our API and debug a developer's stack trace (TypeScript, Python, Next.js) Comfortable with LLMs as tooling — content generation, agent evals, support triage, scraping pipelines Taste — visual, written, brand. You know what a developer will screenshot and what they'll scroll past Comfortable owning a P&L line and defending spend Nice‑to‑Haves Built and run a creator/UGC program at a developer company Ran a Discord or OSS community through a hypergrowth phase Hackathon operating experience — sponsorships, judging, university and YC circuits Paid acquisition experience selling to developers (a genuinely hard channel — say so if you've made it work) Familiarity with how agents discover and rank tools: MCP registries, agent search, LLM recommendation systems Prior 0→1 at an early‑stage startup #J-18808-Ljbffr Naïve