Developer Advocate, Content & Community
About yeet
yeet is built by a tight-knit group of systems, observability, and kernel nerds who refuse to accept “mystery outages” as normal. We’re a small, high-impact team with domain expertise in Linux, eBPF, performance instrumentation, and developer tooling.
We move fast, ship often, and take deep ownership. If you enjoy operating close to the metal, building tools that real engineers lean on during 3 AM incident sprints, and solving hard problems with minimal overhead, you’ll feel right at home here.
About the role
We’re looking for a Developer Advocate to help build the bridge between yeet and the engineers who need it most. This role is all about showing, not telling: you’ll write technical content, build sample apps, record demos, and engage with developers where they already are from GitHub and Discord to X, Reddit, YouTube, TikTok, and industry conferences.
Your job is to make sure engineers don’t just hear about yeet, they see it in action and immediately understand how it helps them debug faster, find bottlenecks, and keep systems reliable without the overhead of traditional observability.
About you
You love teaching through code: Whether it’s a blog post, a TikTok, or a demo repo, you know how to make complex topics click.
You’re equally comfortable spinning up a sample app, writing about Linux internals, or jumping into a Discord thread to help a developer troubleshoot.
You understand that developers hate fluff; you know how to communicate with clarity, authenticity, and technical credibility.
You’ve got a knack for building community, whether that’s running a GitHub project, moderating a Discord, or sparking conversations on Reddit.
You thrive on experimenting with new formats and channels to meet developers where they are.
Nice To Haves
Contributions to open source projects or running your own dev tools.
Prior experience speaking at conferences, meetups, or livestreams.
A following on Twitter / X, TikTok, YouTube, or LinkedIn where you share technical content.
Familiarity with observability, infrastructure, or dev tools: You’ve lived the pain of debugging at 3 a.m.
Experience experimenting with growth channels for developer products (memes, tutorials, challenges, etc.).
Comfort working closely with product / engineering to feed insights from the community back into the roadmap.