Should you work at ComfyUI?
Yes, if you want San Francisco, published pay and blunt feedback. ComfyUI publishes pay on 15 of its 17 roles at a $200K median, raised a $30M Series A, states specific scale numbers and named users, and makes many hires the first in their function with real input into the roadmap. It screens hard: all 17 roles are in person in San Francisco with relocation expected, the company describes itself as intense and demanding, blunt feedback is a stated norm and a screening criterion, and we hold no verified employee reviews.
Read from 17 live roles, 17 full job descriptions and 1 funding round. No employee reviews, no ratings.
Good fit if
- Many roles are the first hire in their function, so the scope is defining a function rather than joining one.
- Postings describe end-to-end ownership of a domain rather than a narrow slice.
- The company is funded and states specific scale numbers and named users.
- Compensation bands are published for most roles.
Think twice if
- Roles are in-person in San Francisco; relocation is expected rather than optional for several.
- The company describes itself as intense and demanding, with long hours implied.
- Candidates who want defined process or regular managerial direction are explicitly screened out.
- You will often be building process from a blank page rather than inheriting one, which suits some people and not others.
We can't tell you
- What managers are actually like day to day
- Attrition, tenure or promotion rates
- Whether the pace is sustainable
- Equity terms — no posting states them
What it pays
Median posted midpoint $200K, ranging $140K–$350K. Based on the 15 of 17 roles that publish pay.
15 of 17 roles post a range
Highest bands
Show the other 9 ranges
How to read this
2 of 17 roles post nothing. The bands here describe only the roles that publish one, which is rarely a random sample of the whole board.
Equity is mentioned, never sized. Postings that offer equity do not state amount, strike or vesting — ask early.
Ranges are pre-negotiation. A published band is what the company advertises, not what it settles at.
Where you'd sit
Of 17 roles that specify a setup.
Who they're hiring
17 live roles across 5 teams.
What the job descriptions ask of you
A reading of how 17 postings are worded — not a score, and not comparable between companies.
Pace Fast
Postings consistently describe fast shipping and shortening release cycles.
“We're moving from a release cycle measured in weeks to one measured in days.”
Autonomy Self-directed
Working without a playbook or close direction is a stated requirement across functions.
“You operate without a playbook. This function doesn't exist here yet. You're defining it.”
Structure Ambiguous
Processes, playbooks, and tooling are described as absent or still being written.
“The enterprise playbook at Comfy is still being written." / "So far we've run finance out of spreadsheets, outsourced bookkeeping, and founder intuition.”
Ownership End-to-end
Roles are framed as owning outcomes end to end, including the unglamorous parts.
“Low ego, high ownership." / "you'll own everything with a dollar sign attached to it”
Collaboration Cross-functional
Most roles are described as working directly across functions and with founders.
“You'll work directly with founders, product, and engineering" / "most of this happens directly in Slack and standup, founders included”
The upside
Stated by ComfyUI in its own postings.
Many roles are the first hire in their function, so the scope is defining a function rather than joining one.
“You'll be finance hire #1 at Comfy." / "As our first Developer Relations hire, you'll own how developers discover, learn, and succeed”
Postings describe end-to-end ownership of a domain rather than a narrow slice.
“Own the warehouse end-to-end. Design dimensional models, establish dbt conventions, and build datasets”
The company is funded and states specific scale numbers and named users.
“We recently raised $30M at a $500M valuation" and "4 million users, 60,000+ community-built nodes, and 150,000+ daily downloads”
Compensation bands are published for most roles.
“Compensation: $180,000-$220,000 + Equity + Benefits" / "$250K – $350K OTE (base plus variable), with meaningful equity”
Non-product roles are told they will have real input into the roadmap.
“Represent customer needs in product roadmap discussions. You'll have real influence over what we build”
Engineering roles state existing tooling as a baseline, not the work itself.
“We already run CI, Kubernetes, and ArgoCD today. That's the floor, not the job.”
The trade-offs
Also from the postings — not complaints from employees.
Roles are in-person in San Francisco; relocation is expected rather than optional for several.
“San Francisco, in-office." / "Are SF-based or willing to relocate to join our in-person rhythm near Alamo Square.”
The company describes itself as intense and demanding, with long hours implied.
“We're a small, intense team in San Francisco... We work hard and demand a lot of each other”
Candidates who want defined process or regular managerial direction are explicitly screened out.
“You want a manager checking in regularly. We trust people to own their work and figure things out.”
You will often be building process from a blank page rather than inheriting one, which suits some people and not others.
“You won't inherit a team, a model, or a playbook — you'll build them.”
Direct and blunt feedback is stated as a norm and a screening criterion.
“You bristle at direct feedback. Our cycle is fast and our notes are direct.”
Decisions are expected on incomplete information.
“You prefer waiting until you have all the information before acting. We move fast on incomplete data.”
Employee sentiment
No data yetWe hold no verified employee reviews for this company. Sentiment appears here only when it comes from verified employees — never from product or customer ratings, which measure something else.