Member of Technical Staff, Quality Systems
Quick Summary
The Role ComfyUI has 4 million users, 60,000+ community-built nodes, and a canvas where every workflow is different. Nobody can write enough tests to cover that by hand.
ComfyUI has 4 million users, 60,000+ community-built nodes, and a canvas where every workflow is different. Nobody can write enough tests to cover that by hand. We want someone to build the systems that do it instead.
This is not a testing role in the traditional sense. You won't run standups, manage a manual test team, or own a defect queue. You'll build the infrastructure that decides whether a release is safe to ship - and make that decision fast enough that we can ship every day.
We're moving from a release cycle measured in weeks to one measured in days. That only works if quality is proven by machines, not negotiated in meetings. That's your mandate.
Responsibilities
~2 min read- →
Own what "correct" means for ComfyUI, and build the systems that prove it. Release gates, coverage of real user journeys, and the automation that makes shipping daily safe rather than scary.
- →
Solve the combinatorial problem. Users combine 60,000+ community nodes freely. Design property-based and generative testing that finds breakage in workflows nobody has written yet.
- →
Solve the visual correctness problem. Canvas rendering, node layout, and link routing break in ways pixel diffs can't catch without drowning you in false positives. Build perceptual comparison that engineers actually trust.
- →
Solve the non-determinism problem. Model output shifts with seeds, hardware, and drivers. Build the evaluation harness that separates a real regression from acceptable variance.
- →
Build custom node CI. Our ecosystem is our moat and our largest untested surface. Make third-party node compatibility something we verify continuously, not discover from bug reports.
- →
Use AI agents aggressively, and verify their output. Agent-driven exploratory testing, generated test cases, self-repairing suites - all of it, gated behind checks that reject the majority of what the agents produce.
- →
Make quality legible. Publish the metrics that tell us whether we're getting better, and own them in front of the team.
You'll also help us answer a harder question: as more of our code gets written with AI assistance, how do we know it's actually good? Building evaluation for our own engineering loop is part of this role, once product quality is on solid ground.
Have built testing or verification infrastructure that other engineers depended on. You write production code - this is an engineering role, not a process role.
Have worked on a system where scripted test coverage was impossible, and did something smarter about it: property-based testing, fuzzing, simulation, generative testing, or evaluation harnesses.
Have shipped something that gates releases, and can tell us what happened the first time it blocked a launch.
Are strong in TypeScript or Python, and comfortable in CI systems and build graphs.
Have opinions about flakiness. You treat a flaky test as a defect with a root cause, not weather.
Have a startup mindset: you thrive in fast-moving environments, take ownership, and love solving problems at scale.
Nice to Have
~1 min readTested graphics, canvas, or rendering surfaces - WebGL, shaders, or visual diffing at scale.
Built evaluation systems for non-deterministic output: golden datasets, judge calibration, scored regression tracking.
Maintained an open-source project, especially one where you had to keep a plugin or extension ecosystem working across versions.
Used ComfyUI, or contributed to it.
Managing a manual QA team.
Owning a Jira defect workflow.
Writing Playwright scripts to someone else's specification.
We have Playwright, Vitest, Storybook, and Codecov in CI today. That's the floor, not the job.
What We Offer
~1 min readComfy (https://www.comfy.org) is the AI creation engine for visual professionals who demand control over every model, every parameter, and every output. The most powerful workflow engine for visual AI.
Unlike tools that hide everything behind a prompt box, Comfy lets you connect models, processing steps, and outputs on a canvas where every decision is visible and every step is inspectable. It gives you the building blocks to create workflows nobody's imagined yet, and share them with everyone.
What started as an open-source project in 2023 now has 4 million users, 60,000+ community-built nodes, and 150,000+ daily downloads. It's used by artists, filmmakers, game studios, designers, researchers, and VFX houses, including teams at OpenAI, Netflix, Amazon Studios, Ubisoft, EA, and Tencent.
We're a small, intense team in San Francisco. Our team comes from Stability AI and Google, and many contributed to the ComfyUI ecosystem long before working here. Low ego, high ownership. We work hard and demand a lot of each other, but we have fun. Everyone here is building something meaningful that will end up being our life's work.
If this mission excites you and you view yourself as top-tier talent, your future latent self is waiting for you at Comfy.
Check out our Github and blog. We recently raised $30M at a $500M valuation. The round was led by Craft, with participation from Pace Capital, Chemistry, TruArrow, and others.
Location & Eligibility
Listing Details
- Posted
- August 5, 2026
- First seen
- August 6, 2026
- Last seen
- August 6, 2026
Posting Health
- Days active
- 0
- Repost count
- 0
- Trust Level
- 63%
- Scored at
- August 6, 2026
Signal breakdown
Please let comfy-org know you found this job on Jobera.
3 other jobs at comfy-org
View all →Explore open roles at comfy-org.
Similar Member Of Technical Staff jobs
View all →Browse Similar Jobs
Stay ahead of the market
Get the latest job openings, salary trends, and hiring insights delivered to your inbox every week.
No spam. Unsubscribe at any time.