Founding Developer Relations

Responsibilities

• Build in public. Ship demos, integrations, plugins and sample projects on top of Weave and the Weave Router. Real code engineers can clone, not slideware.
• Own the Weave Router community. Issues, PRs, releases, docs, contributors. Make the router the default way teams route prompts across Claude Code, Codex, Cursor and whatever ships next.
• Write the technical content. Deep dives, tutorials, benchmarks and integration guides that engineers cite. "We analyzed 2M PRs and here's what AI actually changed" is your kind of headline.
• Own developer experience. Every integration should take minutes. You'll find the rough edges in our docs, SDKs and installers before customers do and fix them, in the docs or in the code.
• Show up where engineers are. Meetups, hackathons, livestreams, podcasts, X, Hacker News. The Field CTO owns the keynote stage; you own the hallway track, the demo booth and the comments section.
• Feed the community back into product. You'll hear what hundreds of engineers actually struggle with. Bring it home and sharpen our roadmap with it.
• Partner with marketing and sales. Technical firepower for launches alongside our Founding Marketer. Technical credibility in deals alongside our Forward Deployed Engineers.
• Be flexible: some days you're shipping a plugin, others you're recording a demo video, triaging router issues, or debugging a customer's MCP config live on a call.

Must-Have

• You're an engineer first. You've shipped production code and you still write it every week. You can build the demo, not just present it.
• You write exceptionally well. Your posts, docs or READMEs have an audience because engineers found them useful, not because the SEO is good.
• You've built an audience or a community. On X, YouTube, a newsletter, a Discord, or an open-source project people depend on. Not "a post did well once." You can show us the receipts.
• You live the AI coding shift. You use Claude Code, Cursor, Codex or similar daily. Your opinions about models, tokens and agents come from your own terminal, not from a thread you read.
• You care about how engineering is measured. You have real opinions on DORA, SPACE and DevEx, and on what changes when half the code is written by agents.
• This role is 5 days in office in SF, with regular travel to meetups, hackathons and conferences

Nice-to-Have

Why Join

About the Interview