Developer Relations Engineer

About Kilo: We're building the fastest-evolving open-source AI coding agent to make programming accessible to billions. In just a few months: #1 AI coding tool on OpenRouter, over 250K downloads, countless 5-star reviews, multiple Hacker News front page articles. But we're just getting started.

Kilo Code is more than just another coding tool. We're creating a superset of the best features from existing AI coding agents, combined with our own innovations, all built with community feedback at the core.

The situation: We’re an open source AI coding tool taking on Cursor, Windsurf, and the rest. We just launched Teams. We have a brand new but fast growing community, and more content ideas than we could make in 100 lifetimes. We are still figuring out how to talk to the majority of developers who may be hesitant to try AI. This is not a bug, it’s your opportunity.

You are:

• Someone who's shipped code that real developers actually use

• Allergic to corporate DevRel theater but obsessed with helping developers win

• As comfortable live-coding to 1000 people as debugging with one person at 2am in Discord

• Fast bias for action. Like, ship-a-tutorial-while-the-feature-is-still-in-PR fast

• Chronically online and interested in the AI devtooling space

Week 1 you will:

• Ship your first Kilo tutorial/demo that gets 100+ reactions

• Answer 50 Discord questions and turn 5 into docs

• Find the three biggest pain points in our onboarding and fix one

Month 1 you will:

• Told us what the "5-minute to wow" onboarding experience needs to look like

• Ship 10 pieces of content, kill 7, double down on 3

• Host your first Kilo community event (virtual or IRL)

• Have strong opinions on why developers bounce, backed by data

Month 3 you will:

• Ship videos that make developers stop scrolling - demos, walkthroughs, “oh wow" moments. Iterate based on what gets watched vs. what gets skipped

• Be the bridge between community chaos and product roadmap - every Discord rant, GitHub issue, and DM gets packaged into actionable insights for engineering

• Track everything that matters - views, discussions, time-to-first-PR, rage-quits. Spot patterns before they're trends, kill what's not working, scale what is

The work setup:

• Remote, but we ship together in Amsterdam every 2-3 months (think: hackathon energy, not conference rooms). We have an office in SF as well.

• Create content that doesn't suck: Colab repos, YouTube demos, blog posts that developers actually read. If it takes more than 5 minutes to get value, you've failed.

• The product changes weekly, so you will ship technical experiments: Build integrations, starter templates, and "what if we..." prototypes. Some will be terrible. Ship them anyway, learn fast.

• We thank people publicly, give feedback directly, and own our mistakes

• Your dopamine needs to come from making things happen, not from having a playbook

What you’ll bring:

• Technical depth: You can debug why someone's LLM context is exploding, explain our architecture, and build a demo app in the same day

• Community instincts: You know when a meme is about to hit, why that one feature request has 500 upvotes, and which influencer just discovered AI coding

• Content velocity: You ship daily. A thread here, a demo there, a workshop on Friday. Quality through quantity, then iterate.

• Developer empathy: You remember what it's like to not understand something. You've been the confused person in documentation hell.

Anti-requirements:

• Years of "Developer Relations" at Oracle/Microsoft/[BigCo]

• Needing a content calendar approved by 5 people

• "I don't code anymore, I'm strategic now"

• PowerPoint as a primary output

• Comfort with slow

Apply with:

• Links to code you've written that developers use

• Your most viral technical content (thread, video, blog, whatever)

• The worst documentation you've ever had to use and what you would've done differently

• Optional: Roast our current docs/onboarding in 280 characters