Developer Relations
US$150,000 – US$200,000 / yr base salary
Posted 31 Jul 2026
BranchFactor Summary
The original posting with the fluff stripped out
- Management level
- Individual contributor
- Employment
- On-Site
- Contract
- Full-time
| Base salary | US$150,000 – US$200,000 / yr |
|---|
About the Role
As our first Developer Relations hire, you'll own how developers discover, learn, and succeed with Comfy programmatically — and you'll be the person inside the building who represents them.
Outbound, you write the guides and build the sample apps developers start from, run the office hours and hackathons where they get unstuck, and act as our public technical voice. Inbound, you're the first person to build against every API surface we ship, and you turn what you learn from developers into work that gets prioritized.
You'll serve two audiences: developers calling ComfyUI from their own applications and pipelines, and the authors behind our 60,000+ community-built custom nodes. The first is the larger share of year one. We already have a Head of Community who owns the artist community, Discord, and events — this role is for the developers writing code.
The content and advocacy experience you bring doesn't have to come from a DevRel title. The ability to actually build what you're writing about does.
Example Projects Include…
-
Owning the path to first success: the trip from "I have a workflow" to "my application is calling it in production" should take minutes. You own that path and every piece of content along it.
-
Learning from developers already building on Comfy: teams run ComfyUI programmatically in production today. Meet them, understand their pipelines and what they need next, and bring back both public content and concrete product input.
-
Shipping sample apps and starter templates: reference implementations developers clone and adapt. Production-shaped, not demo-shaped — real secret handling, real error handling, real retries and backoff.
-
Turning developer friction into fixes: you're the first person to build against every API surface we ship, and the one who files it when something is awkward. You'll sit in engineering planning, though at our size most of this happens directly in Slack and standup, founders included.
-
Owning developer docs: you write the tutorials and guides end to end, and you're the editorial owner of the API reference engineering produces — the person who reads it the way a developer would and sends it back when it doesn't hold up.
-
Supporting custom node authors: documenting extension points, writing migration guides when breaking changes land, and acting as the channel between prolific node authors and the core team.