Summary of the Founding Developer Relations job at Weave

Weave (YC W25) is building the definitive platform for understanding and improving how engineering teams work. We believe the way engineering output is measured today is fundamentally broken and that modern AI can give teams a far more accurate and actionable view of productivity, impact and collaboration.

Trusted by 200+ customers such as Robinhood, Rho, PostHog and Browserbase, we've delivered consistent double-digit month-over-month revenue growth since May and are looking to accelerate our growth.

As Weave's Founding Developer Advocate, you'll be Weave's voice with the engineers who actually use it. Part engineer, part writer, part community builder. You'll own the open-source Weave Router, the content and demos that teach engineers how to measure AI-era engineering, and the community of developers who make Weave the default in their orgs.

We've raised a $13.5 million Series A and are backed by Standard Capital, YCombinator, Moonfire and Burst Capital.

This is a rare opportunity to join at the ground floor and shape how millions of engineers and leaders understand engineering work.

What We're Building

Weave is rethinking engineering output from first principles.

We use AI to:

• Understand how engineers actually work (not just what they ship)

• Surface meaningful insights about productivity, quality, collaboration and impact

• Help teams improve outcomes without vanity metrics or surveillance

Our goal is not to optimize for "more output," but for better engineering.

The Team You'll Work With

You'll work directly with:

• Andrew (CTO) – previously a founding engineer at Causal, MIT alum. Andrew has been in your shoes and is deeply committed to providing the mentorship, ownership and growth he had as an early engineer.

• Adam (CEO) – leads sales and customer discovery. Adam is a former sales executive at multiple high-growth startups and deeply embedded with customers and scaled multiple sales teams from $0-30M in ARR.

This is a small, intense, highly collaborative team. You will have real ownership from day one.

The Role

This isn't a traditional developer relations role. The closest thing we can describe it as is a mashup of software engineer, technical writer, video producer, and open-source maintainer.

You own the conversation with the engineers: the tech leads, staff engineers and engineering managers who install Weave and decide whether Weave is a tool they trust or a dashboard their boss bought. Engineers everywhere are asking the same question: "am I actually better with AI, and how would I know?" The person who answers it credibly, with working code and real data, in public, will earn the trust of every engineer we want as a customer. We want that person to be you.

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.

Qualifications

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

• Prior developer advocate, DevRel or developer education role at a developer tools, AI/ML or infrastructure company

• You've maintained an open-source project, or been a core contributor to one that other people depend on

• You've shipped something on top of LLM APIs, MCP servers or agent frameworks that real people used

• You've produced demo videos, livestreams or a YouTube channel that grew on the strength of the work

• Our tech stack is React + TypeScript on the frontend, Go on the backend, and Python for ML. The Weave Router is written in Go. Experience with any of those is a bonus.

• Experience at an early-stage startup (Seed to Series B), even if it wasn't a DevRel role

Why Join

• Competitive pay + early equity

• Health/vision/dental insurance covered

• Free lunch/dinners/snacks

• Yearly team offsite with regular team events

• Yearly $500 learning/development stipend

• Get to work in SF with one of the fastest moving teams (99%+ percentile code output)

About the Interview

1. 15-minute intro call

2. 30-minute interview with our CEO, Adam

3. 45-minute technical interview with our CTO, Andrew

4. Give us a talk: a 15-minute technical talk or live demo, delivered as you would at a meetup

5. 3-5 day paid work trial