SlipstreamJobs tracks this role from the company's public career site. Apply directly on the employer's site.
Exa is building a search engine for the AI era, having raised $250M Series C at a $2.2B valuation. The company powers AI agents, Fortune 500s, and AI labs with its Search API, disrupting an industry unchanged since the 1990s. The team of ~100 is based primarily in San Francisco and includes talent from Harvard, MIT, Meta, Google Research, and Y Combinator.
You will own the organic discovery engine for Exa's developer audience, driving weekly technical content that engineers respect and share. Your core responsibilities span six interconnected areas:
**Weekly Technical Content Engine**: Ship a steady cadence of high-quality technical content including tutorials, benchmarks, architecture deep dives, comparisons, and release commentary. Success is measured by consistent weekly publication, survival on Hacker News, and organic traffic/signups sourced from the content.
**Answer Engine Optimization**: Own how Exa appears in AI-generated answers from Claude, ChatGPT, and other models. This includes entity coverage, structured content, citation-worthy material, and measurement of citation share across major AI assistants.
**Search Visibility & Topic Architecture**: Define the organic topic map—which questions and keywords Exa should win—and design the content architecture, internal linking, and page strategy to support them. You partner with Digital Marketing on site mechanics.
**Technical Narrative**: Establish and own the substantive point of view on retrieval quality measurement and why agents need different search types. Success is measured by developers and sellers citing your work.
**Measurement & Reporting**: Connect content to pipeline through organic sessions, signups, AI citation tracking, and deal influence. Leadership should trust these numbers.
**AI-First Production Pipeline**: Design workflows that move ideas from concept to published, technically accurate pieces quickly. Automate any step that runs manually more than twice.
You will read code, call APIs, run evaluations, and publish work with your name on it. This is an AI-first role at an AI-first company—your research, drafting, and measurement loops should leverage AI, with clear judgment about what requires human touch.
You do NOT own paid channels, website infrastructure, sales enablement, core positioning, developer documentation, case studies, or email marketing—those belong to other teams.
Success looks like: weekly technical content that engineers share organically; growing YouTube and X followings; Exa cited by major AI assistants when developers ask about search for agents; winning organic questions that matter to your ICP with measurable signups; sales and DevRel leveraging your content; benchmarks that hold up under reproduction; content decisions driven by conversion data.
