Head of Developer Relations

## The role

This is our first community and developer relations hire. LightSprint sits at an unusual intersection: our most enthusiastic users are non-technical builders shipping to production for the first time, and the people they work with are engineers who need to trust what agents produce. You’ll be the voice between us and both audiences, building the community where they learn from each other, and making sure what we hear from them shapes what we build.

Everything you make (demos, docs, talks, threads) comes from actually using the product, every day, in an AI-cloud-agent workflow.

## What you’ll do

* **Build the community from zero.** Own our Discord/Slack, spin up rituals that make people want to show up (demo days, build-in-public showcases, office hours) and turn early users into evangelists.
* **Ship content that teaches, not markets.** Demo videos, tutorials, templates, and technical deep-dives that show what spec-driven delivery looks like in practice, for PMs and engineers alike.
* **Be the feedback loop.** Synthesize what the community is saying into sharp product input for the founders. You’ll know before anyone else where the product delights and where it confuses.
* **Represent LightSprint in public.** Talks, podcasts, meetups, launch posts, and the ongoing conversation about how AI changes how teams ship software.
* **Own launches.** Coordinate Product Hunt, Hacker News, X, and community channels so every release lands with momentum.

## Requirements

* You’ve done DevRel, community, or developer education at a developer tool or technical product, ideally early-stage, where you built the motion rather than inherited it. 3+ years of relevant experience.
* You can use the product for real. You don’t need to be a professional engineer, but you can ship something with AI coding tools, read a PR, and explain a preview environment without notes.
* Exceptional written and spoken communication. You make complex, technical things feel simple and exciting, to a PM and to a staff engineer, in the same piece.
* You’re a builder of audiences. You have evidence: a community you grew, a following, a channel, a newsletter, something that shows people choose to listen to you.

## Nice-to-have

* An existing audience or credibility in the AI coding / agent tooling space.
* Experience creating video content (demos, tutorials, short-form) end to end.
* Prior experience as an engineer, PM, or founder.
* Experience with community platforms and tooling (Discord, Circle, Luma, Common Room or similar).