Creator Community Manager

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Passionfroot" (company description) then "About The Role". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. We need to include sections only when posting has real, specific content. We have content: About Passionfroot (company overview) maybe not a required heading but could be "About the company"? Not listed. The allowed headings list includes "About the role". We could put company description under maybe a heading like "About the company"? Not in list; but we could just put it as a

without heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use

for section headings (e.g. those). Likely we should stick to those headings when appropriate. We have "About The Role" heading in source; we can map to

About the role

. Then we have responsibilities list (What You’ll Do) -> could be Responsibilities section. Requirements/Qualifications: we have "What We’re Looking For" (requirements) and "Nice to Have" (nice-to-have). Could combine as Requirements? Might split: Requirements (must have) and Nice to Have (optional). Benefits: we have "What we offer" includes Competitive Compensation, Health Benefits, Fun team off-sites, Tools & Workspace. Also mention "Competitive Compensation – A salary commensurate with experience." That's vague; we should not create Pay section if only says commensurate with experience (no specific). Benefits: we have health benefits, off-sites, tools. So we can create Benefits section with those. Pay: we should not create because only says commensurate with experience (no specific). Schedule: not mentioned. So we omit Pay and Schedule. We need to remove boilerplate: EEO, equal opportunity, etc. Also remove navigation, cookie, legal, duplicated lines, application instructions. The posting includes "Passionfroot is an equal opportunity employer..." that's boilerplate; remove. We need to preserve all substantive information. So include company description paragraph(s). Then About the role heading, then responsibilities list (maybe as

• ). Then Requirements heading with must-have items as list. Then Nice to Have heading maybe as a subsection? Could be under Requirements? But we can have separate heading "Nice to Have" though not in list; but we could treat as part of Requirements? The instruction says use those headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings but suggests using those. Nice to Have could be under Requirements as a sublist? Might be okay to have a separate heading but not in list; risk. Safer to incorporate nice-to-have into Requirements section as a separate list labeled "Nice to Have" but still under Requirements heading? Could do

  Requirements

  then

  Must have:

  ... then

  Nice to have:

  ... That's acceptable. Skills: we could list skills from requirements: experience in community management, etc. Could create Skills section but we already have Requirements covering similar. Might be redundant. Better to follow instruction: prefer few substantive sections over many thin ones. So we can have About the role, Responsibilities, Requirements, Benefits. That's four sections. Now extract content. Company description: "About Passionfroot Creator-led growth is one of the fastest-growing channels in B2B - we're building the infrastructure behind it. Passionfroot is the leading platform where modern companies scale creator-led growth, and where top creators manage and monetize brand partnerships. Our customers are some of the most ambitious, fastest-moving companies in the world - Replit, Figma, Framer, LumaAI, Gamma, Airtable - companies that set the standard for what modern growth looks like. We help them run high-impact creator programs across LinkedIn, YouTube, newsletters, and more. We're growing 13x in revenue year over year, profitable, and just closed our Series A round! We are backed by leading investors including Insight Partners, Creandum, Supernode and founders and operators from Cursor, Anthropic, n8n and more. We're expanding fast across New York, Europe, and Brazil - and we're just getting started." We'll put that as

  ...

  . About the role: heading

  About the role

  then paragraph: "We’re looking for a Creator Community Manager to build, grow, and elevate the creator community around our platform. This person will own both the creator community and the creator experience, helping creators feel supported, engaged, and successful at every stage of their journey with us. You will serve as the voice of creators internally and the face of our platform externally, shaping programs, feedback loops, education, and engagement strategies that strengthen creator trust and loyalty. This is a cross-functional role that sits at the intersection of community, product, operations, support, and growth." Then Responsibilities: heading

  Responsibilities

  then list from "What You’ll Do". Items: - Own the overall creator community strategy, including engagement, retention, advocacy, and creator satisfaction - Build strong relationships with creators and develop a deep understanding of their needs, motivations, and pain points - Design and run community programs such as creator onboarding, education, events, ambassador programs, and feedback forums - Improve the end-to-end creator experience across the platform, identifying opportunities to reduce friction and increase value - Gather and synthesize creator feedback, then partner with Product, Support, and Operations to prioritize and address key issues - Create resources, communications, and playbooks that help creators succeed on the platform - Monitor community health and creator sentiment, using data and qualitative insights to guide decisions - Develop scalable systems for creator communication, recognition, and support - Partner with Marketing and Growth to spotlight creator success stories and strengthen community-driven growth - Act as the internal advocate for creators, ensuring their perspective informs platform improvements and business decisions Make each
  • . Requirements: heading

    Requirements

    . Then we need to list must-have items from "What We’re Looking For". Items: - Experience in community management, creator partnerships, customer success, or a similar relationship-driven role - Strong understanding of what makes creator communities thrive, including engagement, trust, belonging, and recognition - Ability to balance high-touch relationship building with scalable program design - Excellent written and verbal communication skills - Experience working cross-functionally with Product, Marketing, Support, and Operations - Strong organizational skills and comfort managing multiple initiatives at once - Analytical mindset, with the ability to use both data and creator feedback to drive improvements - Empathy for creators and a genuine passion for helping them succeed Then Nice to Have: we can add a

    Nice to have:

    ... items: - Experience working at a creator economy, marketplace, media, or community-driven company - Familiarity with community platforms, creator tools, and engagement workflows - Experience launching community programs from the ground up - Background in creator support, audience development, or digital content ecosystems We'll include that under Requirements heading as separate list. Benefits: heading

    Benefits

    then list: - Competitive Compensation – A salary commensurate with experience. (But we said not to create Pay section if vague; but we can include as benefit? It's compensation info. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state Competitive Compensation – A salary commensurate with experience. That's a statement about compensation, albeit vague. It's still stating compensation. Should we include? The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. It does state compensation, albeit vague. So we can include a Benefits section and include that line. However they also said "Prefer a few substantive sections over many thin ones." Including compensation line is okay. - Health Benefits – We cover 100% of employee health insurance. - Fun team off-sites – We’ve been to Barcelona, Mallorca, South of France, Berlin. - Tools & Workspace – Latest Apple hardware. We should not include EEO line. Now ensure no duplicated lines. Also remove any mention of "Passionfroot is an equal opportunity employer..." etc. Now produce HTML fragment. Check for any leftover boilerplate: "Why This Role Matters" section: we have that paragraph after "What We’re Looking For". Should we include? It's substantive: "Why This Role Matters Creators are at the center of our platform. In this role, you’ll help shape how they experience our product, how they connect with our brand, and how they grow with us over time. Your work will directly influence creator satisfaction, retention, and the long-term strength of our ecosystem." That's substantive; we could include as a separate section maybe "Impact" but not in allowed headings. Could incorporate into About the role or Responsibilities? Might be better to add a short paragraph after About the role before Responsibilities. It's not a heading but we can include as

    . That's fine. Also there is "What we offer" we turned into Benefits. Now ensure we didn't miss any substantive info: The company description includes growth stats, investors, expansion. All included. Now produce final HTML. We'll wrap sections in appropriate tags. Let's craft:

    About Passionfroot ...

    About the role

    We’re looking for a Creator Community Manager ...

    Why This Role Matters Creators are at the center of our platform. In this role, you’ll help shape how they experience our product, how they connect with our brand, and how they grow with us over time. Your work will directly influence creator satisfaction, retention, and the long-term strength of our ecosystem.

    Responsibilities

    • Own the overall creator community strategy, including engagement, retention, advocacy, and creator satisfaction
    • Build strong relationships with creators and develop a deep understanding of their needs, motivations, and pain points
    • Design and run community programs such as creator onboarding, education, events, ambassador programs, and feedback forums
    • Improve the end-to-end creator experience across the platform, identifying opportunities to reduce friction and increase value
    • Gather and synthesize creator feedback, then partner with Product, Support, and Operations to prioritize and address key issues
    • Create resources, communications, and playbooks that help creators succeed on the platform
    • Monitor community health and creator sentiment, using data and qualitative insights to guide decisions
    • Develop scalable systems for creator communication, recognition, and support
    • Partner with Marketing and Growth to spotlight creator success stories and strengthen community-driven growth
    • Act as the internal advocate for creators, ensuring their perspective informs platform improvements and business decisions

    Requirements

    Must have:

    • Experience in community management, creator partnerships, customer success, or a similar relationship-driven role
    • Strong understanding of what makes creator communities thrive, including engagement, trust, belonging, and recognition
    • Ability to balance high-touch relationship building with scalable program design
    • Excellent written and verbal communication skills
    • Experience working cross-functionally with Product, Marketing, Support, and Operations
    • Strong organizational skills and comfort managing multiple initiatives at once
    • Analytical mindset, with the ability to use both data and creator feedback to drive improvements
    • Empathy for creators and a genuine passion for helping them succeed

    Nice to have: