This is a role guide, not an installed employee. It explains what the role owns and how Tycoon runs it. Nothing is hired or activated until you choose it.
What your AI DevRel does
Workflows on autopilot
Release-day content pack
When engineering ships a new feature, produces the docs page, three language samples, a changelog entry, a tweet, and a 90-second Loom walkthrough — all within the day of release.
Issue triage loop
Scans GitHub issues every two hours. Applies labels, asks for missing repro info, answers common questions, escalates real bugs to engineering with a clean repro.
Docs health review
Weekly crawl of the docs site looking for broken links, stale examples, code that no longer runs, and missing sections. Fixes the top 10.
Community sentiment digest
Every Friday summarizes the week in Discord, GitHub, and Twitter — top frustrations, top wins, most-asked questions. Sends to CEO and product leads.
Sample app gallery
Maintains a library of minimal but real sample apps that prove integrations work end-to-end. New sample per release.
Monthly office hours
Hosts a public community call, takes questions, summarizes themes into a blog post, and files the real feedback as product tickets.
Without vs With a AI DevRel
- Docs rot because every engineer assumes someone else is updating them
- A developer opens a GitHub issue and waits four days for a response
- Release day is an engineering commit and no external comms
- You have no idea what developers are saying about you this week
- A human DevRel hire runs $180K+ plus travel plus tools
- DevRel owns docs health and they stay current release by release
- Triage happens within the hour, with a real answer or a real escalation
- Release day ships a content pack — docs, samples, changelog, video
- A Friday digest summarizes sentiment and top friction
- The AI DevRel covers 80% of the work for a fraction of the cost
A day in the life of your AI DevRel
08:00Scans overnight GitHub issues. Closes 4 duplicates with links, asks for repro on 2, escalates 1 real bug to engineering.10:30Drafts the Python SDK quickstart for the new webhooks feature shipping Thursday. Runs the code against staging to confirm it works end-to-end.13:00Posts a 3-tweet thread explaining the webhook design with a link to the new docs. Uses the developer's voice, not marketing language.15:00Answers 8 Discord questions. Two become new docs FAQ entries before the next developer asks.17:30Pushes the weekly sentiment digest: 4 recurring frustrations, 2 delight moments, 1 competitive displacement win.19:00Logs the day: 12 issues handled, 1 SDK sample shipped, docs site green.