Developer Relations

Developer Relations

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.

• Running office hours, workshops, and hackathons : recurring live contact with the developers building on us. You pitch and own these; Community helps you run them.

• Being our public technical voice : written guides, video walkthroughs, livestreams, and an active presence wherever AI developers actually are.

You May Be a Fit If

• You can build a real application against an API without hand-holding, and you've shipped something that had to survive production — not just a demo.

• You've integrated a third-party API or a self-hosted service into a real product, and you still remember exactly what was painful about it.

• You've produced technical content developers actually used: tutorials, sample repos, videos, docs. We care about the work itself, not the job title that was attached to it.

• You've worked on an API, SDK, or developer platform product and have opinions about what makes one pleasant or miserable to integrate against.

• You know enough about generative AI to talk to our users credibly — checkpoints, LoRAs, samplers — and you want to go deeper. You aren't expected to know exactly how diffusion models work under the hood — just how our users may want to interact with them.

• You give direct, specific product feedback, and you keep giving it when the answer is "not this quarter."

• You operate without a playbook. This function doesn't exist here yet. You're defining it.

• No specific language requirement. Python and TypeScript are simply the first SDKs we're shipping. If you're strongest in Go, Rust, or C++ and can flex, that's fine.

Nice to Have

• Experience with media, VFX, game, or other creative production pipelines. A meaningful share of our developers are building inside them, and understanding how those pipelines really work is hard to fake.

• You can flex into shipping platform code when it helps — SDK work, auth flows, API surface. Not the core of the job, but a real multiplier.

• Opinions about documentation tooling, and how developer docs should be built and kept accurate over time.

• You've used ComfyUI, or written a custom node for it. Rare, and a strong signal.

• Experience with an open-source product that has a large, opinionated community. Ours has 4 million users and they tell us exactly what they think.

• Experience serving self-serve developers and large-company integration teams at the same time. Both show up here.

Not a Fit If

• You come from marketing and can't actually build the thing you're demoing. This audience notices immediately.

• You've published a lot of content but can't name a single product change that happened because of your feedback.

• Your background is pure consumer apps rather than APIs, SDKs, or developer platforms.

• You need an established team, a defined playbook, and a content calendar handed to you.

• Your best work is impressive demos and hackathon projects, and you've never had to make something hold up in production. If your sample code puts the API key in a constant, this isn't the role.

• A large, blunt, opinionated open-source community sounds exhausting rather than energizing.

Applying

If there's a fit, you'll do a recruiter screen, a technical conversation, a behavioral conversation, and an onsite. The onsite includes a review of work you've already published and a short exercise where you build something against our API and present it back — including a specific critique of what you found awkward in the API and the docs. We pull as much signal forward as we can, so the onsite is short and high signal.

• Location : San Francisco preferred

• Compensation : $150,000-$200,000