Developer Relations

Inception creates the world’s fastest, most efficient AI models. Our Mercury model is the world’s fastest reasoning LLM and first commercially available diffusion LLM, delivering 5x greater speed and efficiency than today’s LLMs, with best-in-class quality. We are the AI researchers and engineers behind such breakthrough AI technologies as diffusion models, flash attention, and DPO. The Opportunity Diffusion for language is a new paradigm, and we're the team with the researchers who pioneered it. The developer conversation around this technology is only just beginning and we're looking for the person who will lead it. This role is the public technical voice for the Mercury family of models. You'll ship runnable code, publish honest benchmarks, build integrations developers actually reach for, and set the standard for how the world understands diffusion LLMs. You'll own our developer-facing presence end-to-end from the technical blog to X to Discord. And you'll do it in partnership with the researchers who invented the underlying technology, with direct access to founders. This is a broad role for someone who wants breadth. You'll write, ship, engage, benchmark, and represent Mercury across every surface where technical decisions get made. You'll partner with the Head of Marketing on technical content strategy, Sales on customer-facing technical initiatives, and Product and [... source excerpt omitted ...] tegrations that make Mercury the model developers reach for first. If you want to define how a new category is understood and build a community around it, this is the seat. What You'll Own Technical content and demos Ship a runnable technical artifact every ~2 days: a demo, a benchmark, a tutorial, an integration, or a technical blog post Author the technical blog cadence, a minimum of 2-3 quality technical posts per month, ideally more Build public demos that show Mercury's speed and capability on realistic developer workloads (voice, agents, search/RAG, coding) Publish honest benchmarks with reproducible methodology alongside our Eval team; own the response when public [... source excerpt omitted ...] M technical work Partner with Marketing for technical portions of compete pages: architecture arguments, benchmarks, reproducible comparisons Produce technical sales enablement: customer-facing benchmark deep-dives, POC support materials, technical case studies with paying customers Partner with sales on customer conversations where a technical voice materially moves the deal Partner with marketing on distribution, campaign integration, brand/enterprise-facing content, and cross-audience amplification (Head of Marketing owns marketing OKRs; DevRel contributes to them through the work above) Partner with product/eng on developer feedback, docs improvements, and API/product ro