Head of Developer Relations

About Kenn

Kenn is a venture-backed startup building next-generation systems to power the future of agentic work. Wes McKinney, Phillip Cloud, and Marius van Niekerk founded it in 2026. Before Kenn, Wes created pandas and co-created Apache Arrow.

kenn.io · github.com/kenn-io

The role

Kenn is building a stack of local-first systems for developers who build with agents, and our open-source tools are part of it. AgentsView shows what coding agents did and what they cost. roborev reviews every commit in the background. kata tracks agent plans and progress. msgvault turns email and chat into a searchable archive that agents can use. AgentsView has more than 6,000 stars on GitHub, and msgvault and roborev each have more than 1,500.

We are hiring an experienced builder to own content and community growth for Kenn's developer tools. Most of this job is making content: blog posts, videos, and talks on how to use our tools and what you can build with them. You will also run the community around the tools, get people contributing, and make sure the team hears from the people who use them.

You will be the first person in this role. By the end of your first year, far more developers should use our tools than do today.

What you will do

The tools keep changing and the community keeps growing, so this work does not finish. Here is the kind of thing you will do week to week.

Teach people to use our tools

• Record a walkthrough of AgentsView that breaks down a week of Claude Code and Codex sessions: what the agents did and what they cost.
• Write a tutorial that adds roborev to a real project and shows what it catches in agent-written code.
• Make a short video for each release that shows what changed, with an agent driving the demo.
• Show how the tools work together, such as kata tracking an agent's plan while roborev reviews the commits it produces.
• Build a talk on how our team works with agents every day, and give it at developer and AI conferences.

Shape how we present Kenn

• Work with the team on how we present our products and how our open-source projects fit into them.
• Build slide decks and presentations for Wes McKinney, the CEO, and others on the team to give at conferences.
• Rewrite a project's README and docs so a new user has it running in minutes.

Run the community

• Run our Discord, and turn a question asked three times into a doc page or a video.
• Watch issues and pull requests across our repositories, so each one gets an answer.
• Find people building interesting things with our tools and show off their work.
• Bring what users keep asking for back to the team.

Bring in contributors

• Mark good first issues and keep the contributing guides current.
• Help new contributors land their first pull request, and keep the regulars coming back.

What you will build

In your first year, you will build the body of work that brings developers to our tools:

• An active YouTube channel.
• A blog that publishes regularly.
• Conference talks that you give.

Agents can do much of the production. An agent can script a demo and drive the product through it, so you can make many videos in far less time than recording each one by hand. You decide what is worth making, and every video has to be worth watching. We do not publish AI slop.

Who we are looking for

• Open-source experience. You have contributed to or maintained open-source projects. Someone who has never worked on an open-source project is unlikely to fit this role.
• Builds with agents. You have built something real with agents, and you can show us.
• Public speaker. You have given conference talks and have a lot of public speaking experience.
• Makes content. You write posts and make videos that teach developers something. Ideally you already have an audience, through a blog, a Substack, or YouTube or TikTok videos.
• Senior. You can start this function from nothing, from the publishing schedule to the community.

Nice to have: experience building triage tools for open-source projects. We care more about what you have built than where you studied or how many years you have worked.

Why join

Developers are changing how they build software around coding agents. At Kenn, your job is to show them what works, using tools our team builds with every day, so your demos and talks show real work on real projects.

You will work with the people behind pandas, Apache Arrow, and Ibis, and build the talks they give at conferences as well as your own. You will set how Kenn works with its open-source community from the start, and the team will hear from developers through you.