This is an engineer's job with an audience. You'll spend your time building: reference apps, demos, integrations, and the small sharp examples that make a developer understand in thirty seconds what Exa unlocks for their agent. Then you'll show how it works, in talks, streams, workshops, repos, and wherever developers gather
You should already be building with LLMs, agents, and retrieval, and you should be able to talk to a staff engineer about where their pipeline is failing without hedging. Communication is the other key. We need someone who does both building and presenting, with good taste for production values both on stage and in videos
You'll work closely with the Head of DevRel on community and ecosystem programs, and with Technical PMM on repurposing what you build into content for SEO and AEO
This role is in-person, at either our San Francisco HQ or in New York office
WHAT YOU'LL OWN
DEMOS AND REFERENCE APPLICATIONS
Own a growing library of working code that shows Exa at its best: reference agents, integration examples, and demos built for specific developer use cases. Success is measured by usage, forks, and whether developers cite them as the reason they got started
TECHNICAL TALKS AND WORKSHOPS
Be a teacher, both in-person and on video. Represent Exa at conference talks, meetups, workshops, hackathons, and streams. Success is measured by quality of delivery and by developers who start building after seeing you
COMMUNITY PRESENCE AND SUPPORT
Be genuinely useful in public forums: answering questions, unblocking developers, participating in the communities where our users are, and being a recognizable helpful presence rather than a promotional astroturfer. Success is measured by response quality and audience trust
INTEGRATION WORK
Build and maintain integrations with the frameworks and tools developers use, in partnership with the Head of DevRel who owns the partner relationships. Success is measured by integrations that stay working as upstream changes
DEVELOPER FEEDBACK
Carry friction back to Product and Engineering with the specificity only a builder can provide: what broke, where you got stuck, and what a new developer would abandon. Success is measured by fixes shipped because you reported them well