Sr. Growth Engineer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes many details: role description, responsibilities, what you'll do, you might be a good fit (requirements/qualifications/skills), about Comfy (company description), compensation range (Pay). No explicit Benefits, Schedule. So we should include sections: About the role (maybe a brief description?), Responsibilities (What You'll Do), Requirements/Qualifications/Skills (maybe combine?), Pay (Compensation Range). Also maybe "About Comfy" could be under About the role? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections to include based on content. We have content for: - About the role: could be the introductory paragraph describing the role (The Role Comfy has millions...). That's about the role. - Responsibilities: "What You’ll Do" bullet list. - Requirements/Qualifications/Skills: "You Might Be a Good Fit If You Have ..." plus maybe "Bonus Points". Could split into Requirements (must-have) and Skills (nice-to-have) or Qualifications. We'll include Requirements (must-have) and Skills (bonus). Or combine into one section "Requirements". But we can have multiple sections if content exists. - Pay: Compensation Range. - Benefits: none specific, so omit. - Schedule: none specific, omit. We must not repeat job title as heading. No Job ID etc. We must preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO etc. There's none. We need to output only HTML fragment, no /, no markdown fences. We'll produce something like:

About the role

... (the introductory paragraph)

Responsibilities

• Own experiments end to end: identify an opportunity, form a hypothesis, define the primary metric and guardrails, build the experience, instrument it, launch it, analyze the result, and make the ship-or-kill decision.
• Improve the full Comfy Cloud journey, including account creation, first workflow, first successful output, templates, local-to-cloud adoption, credits, upgrade flows, billing, collaboration, sharing, and retention.
• Build across the stack—from polished frontend experiences to backend services, APIs, data models, experiment assignment, billing logic, and lifecycle integrations.
• Own measurable product outcomes such as activation, time to first value, free-to-paid conversion, retained usage, expansion, and revenue, while protecting reliability, user trust, and compute economics.
• Query product data yourself and investigate user behavior without waiting for an analyst to translate it for you.
• Talk with users and learn from Comfy’s community when quantitative data does not explain what is happening.
• Build the minimum experimentation infrastructure needed to move quickly with trustworthy results: feature flags, exposure logging, event instrumentation, experiment health checks, and reusable patterns.
• Turn successful experiments into durable, production-quality product experiences.
• Raise the growth-engineering bar by documenting what the team learns and helping other engineers run better experiments.

Requirements

• 6+ years of software engineering experience and are strong across both frontend and backend development.
• Have personally owned an activation, conversion, retention, or revenue metric—and can explain how your work moved it.
• Have run real product experiments from hypothesis through analysis, including experiments that failed or produced ambiguous results.
• Can work without a detailed specification.
• Know how to combine data, user insight, product judgment, and technical constraints into a sensible next bet.
• Are comfortable building user-facing experiences in TypeScript and a modern frontend framework, as well as backend services and APIs.
• Experience with Vue is useful, but strong fundamentals matter more than an exact stack match.
• Can use SQL and product analytics tools to explore funnels, cohorts, experiment results, and unexpected behavior.
• Understand experiment fundamentals: assignment, exposure, primary metrics, guardrails, sample-size tradeoffs, novelty effects, and segmentation.
• Have excellent product judgment and care about UX quality—not just whether the code works.
• Move quickly while knowing when an experiment can be lightweight and when billing, identity, privacy, or core product architecture demands more rigor.
• Thrive in a small, intense team with high ownership, low ego, and a fast clock.

Skills

• Built growth systems for a PLG, developer-tool, creator-tool, or usage-based SaaS product.
• Worked on onboarding, templates, collaboration loops, referrals, pricing and packaging, subscriptions, credits, usage metering, or Stripe integrations.
• Built or introduced experimentation infrastructure rather than only consuming an established platform.
• Understand the unusual dynamics of growing an open-source product alongside a commercial cloud offering.
• Use ComfyUI or other professional creative-AI tools and have opinions about making their power more approachable without flattening it.
• Use AI development tools as a normal part of how you explore and ship.

Pay

Compensation Range: $160K - $220K

We also might include About Comfy as part of About the role? The instruction says About the role heading for section headings. The introductory paragraph includes description of Comfy and role. Could also add a separate About Comfy section but not in list. Probably better to include About the role containing both role description and company overview. We'll put the first paragraph(s) into About the role. We need to preserve all substantive information: we must include the description of Comfy Cloud, mission, etc. The "About Comfy" paragraph includes details about Comfy, its users, open-source ecosystem, funding, team, etc. That is substantive and should be included. Where to put? Could be part of About the role or a separate section "About Comfy". Since only prescribed headings list includes About the role, we can put company info there. Thus About the role paragraph will include: "The Role Comfy has millions of users and one of the largest open-source ecosystems in generative AI. Comfy Cloud gives that community a zero-setup way to create with ComfyUI, but we are still early in building the product-led growth engine around it. We’re looking for a senior full-stack engineer to own that engine...." plus later "About Comfy Comfy (https://www.comfy.org) is the AI creation engine..." etc. We'll combine. We must not repeat job title as heading. No job title appears. We must not include navigation/legal/EEO etc. None. We must not include placeholders like "commensurate with experience". Not present. We must not invent or summarize away detail. We'll keep details. Now produce final HTML. Check for any duplicated lines: The posting includes "What Success Looks Like" etc. That's also substantive; should we include? It's under "What Success Looks Like". Could be part of Responsibilities or a separate section? Not in prescribed headings but we could include as part of Responsibilities? However the instruction says prefer a few substantive sections over many thin ones. We could incorporate success expectations into Responsibilities or maybe a separate section "Expectations". But not in list. Safer to incorporate into Responsibilities as additional bullet points. We have "What Success Looks Like In your first three months..." etc. That's substantive; we should include. Could add as bullet under Responsibilities or a separate section "Expectations". Since not in prescribed headings, maybe we add as bullet under Responsibilities. Similarly "What This Role Is Not" etc. Could be omitted? It's substantive but maybe not needed. However instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should include that too. Could be a section "What This Role Is Not". Not in prescribed headings but we could add as a section anyway? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive list? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. But also says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can create other headings if needed, but they gave examples. Safer to stick to those headings and fit content into them. Thus we need to fit "What Success Looks Like" and "What This Role Is Not" into existing sections. Could put success expectations under Responsibilities (makes sense). "What This Role Is Not" could be under About the role or maybe under Responsibilities as clarifications. We'll add bullet points under Responsibilities for success expectations and maybe a note about what it's not. We must not lose any substantive info. Let's capture all bullet points from the posting: - "Own experiments end to end: identify an opportunity, form a hypothesis, define the primary metric and guardrails, build the experience, instrument it, launch it, analyze the result, and make the ship-or-kill decision." - "Improve the full Comfy Cloud journey, including account creation, first workflow, first successful output, templates, local-to-cloud adoption, credits, upgrade flows, billing, collaboration, sharing, and retention." - "Build across the stack—from polished frontend experiences to backend services, APIs, data models, experiment assignment, billing logic, and lifecycle integrations." - "Own measurable product outcomes such as activation, time to first value, free-to-paid conversion, retained usage, expansion, and revenue, while protecting reliability, user trust, and compute economics." - "Query product data yourself and investigate user behavior without waiting for an analyst to translate it for you." - "Talk with users and learn from Comfy’s community when quantitative data does not explain what is happening." - "Build the minimum experimentation infrastructure needed to move quickly with trustworthy results: feature flags, exposure logging, event instrumentation, experiment health checks, and reusable patterns." - "Turn successful experiments into durable, production-quality product experiences." - "Raise the growth-engineering bar by documenting what the team learns and helping other engineers run better experiments." Success expectations: - "In your first three months, you will understand the Comfy Cloud funnel, establish trustworthy baselines, identify the largest points of friction, and ship your first experiments." - "Within six months, you will own a repeatable experiment cadence, have produced measurable improvements to at least one company-level growth metric, and have made it substantially easier for the team to launch and evaluate new growth ideas." - "Within twelve months, Comfy will have a stronger self-serve growth engine—and a body of accumulated knowledge about what helps creators discover value, convert, and stay—because of the systems and experiments you built." What This Role Is Not: - "A marketing-engineering role limited to landing pages and SEO." - "An analytics-engineering role focused primarily on pipelines and dashboards." - "A feature factory where Product decides what to build and Data decides whether it worked." - "A research role that produces experiment ideas for other engineers to implement." We can include these as bullet points under Responsibilities or maybe a separate section "What This Role Is Not". Since not in prescribed headings, maybe we add as bullet under Responsibilities with a note. We'll include them as bullet points under Responsibilities. Now Requirements: we have the "You Might Be a Good Fit If You Have ..." list. We'll capture each bullet. List: -