Head of Customer Growth

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO etc). Must not include application instructions. Must not include sections with filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes "What we offer:" with bullet points: Competitive equity..., Fully remote..., 4-5 weeks..., $2,000 workspace setup..., $1,000 annual stipend..., Compensation Range: $259K. So we have compensation (Pay) and benefits (What we offer). Also schedule? Not mentioned. So we can include Pay and Benefits sections. Also maybe "About the role" (the intro paragraph). Responsibilities: "What you will be responsible for" etc. Requirements/Qualifications: "What you will need to be successful". Skills maybe part of that. We'll structure. We need to preserve all substantive info, not invent or summarize away detail. Must not omit details. Must keep all content from posting except boilerplate. Must not add new content. We need to parse the posting and extract sections. Let's extract: Intro paragraph: "RevenueCat removes the headaches of building and scaling in‑app subscriptions. Since graduating from YC’s S18 batch we’ve grown into the default monetization platform for mobile: we’re in >40% of newly shipped subscription apps, we process $12B+ in annual purchase volume, and we help everyone from a solo dev in Brazil to the OpenAI mobile team understand and grow their revenue. We’re a remote‑first crew of 150+, spread across 25+ countries, and guided by values we actually practice: Customer Obsession, Always Be Shipping, Own It, and Balance. If you want your work to touch hundreds of millions of end‑users (and help the developers behind them get paid), you’ll fit right in." Then "The role" heading: "We are looking for a Head of Customer Growth to build and lead the operating system that helps RevenueCat customers become better app businesses. This is broader than a traditional Customer Success role. It combines strategic account coverage, app-growth judgment, specialist advisory, customer education, product adoption, and scalable enablement. The goal is not to give every customer the same high-touch service. It is to identify where RevenueCat can create disproportionate value, deploy the right kind of help, and turn every successful customer intervention into knowledge that benefits the rest of the customer base. You will lead a multi-lane Customer Growth function spanning the CSM team, Growth Advisory, Growth Advocacy, and the emerging Customer Enablement function. The CSM Team Lead will own daily CSM execution. You will set the strategy, operating model, talent bar, investment plan, and measures of success for the function as a whole. For our highest-value customers, this means deep account context, growth diagnosis, stakeholder mapping, product-adoption strategy, technical-account coordination, and clear next-step ownership. For high-potential customers, it means identifying them early and providing the right help before revenue has fully materialized. For customers with specific growth bottlenecks, it means bringing in the right specialist. For the broader customer base, it means scalable education through Growth Advocates, lifecycle guidance, office hours, playbooks, templates, product nudges, and eventually dynamic next-best-action systems. Your job is to make Customer Growth one operating system rather than a collection of disconnected activities." Then "Why we are hiring for this role now": paragraph about serving various customers, need for deliberate allocation, etc. Might be part of About the role? Could be separate but we can combine into About the role. Then "What you will be responsible for": list of responsibilities bullet-like sentences. We'll need to convert to

• . Then "What success looks like": timeline sections (first month, three months, six months, twelve months). Could be part of Responsibilities or separate? Might be considered expectations. Could be a section like "Success metrics" but not in allowed headings. We have only allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could map "What you will be responsible for" to Responsibilities. "What you will need to be successful" to Requirements/Qualifications/Skills. "What we offer" to Benefits and Pay. "Compensation Range: $259K" to Pay. We need to avoid creating sections with filler. So we will include:

  About the role

  containing intro + The role + Why we are hiring for this role now (maybe combine). Must preserve all substantive info.

  Responsibilities

  containing the bullet list from "What you will be responsible for" (including sub-bullets? It's paragraphs with semicolons). We'll need to break into list items.

  Requirements

  maybe containing "What you will need to be successful" (the paragraph about experience). Could also split into Requirements and Qualifications but we can just use Requirements. We could also have

  Skills

  for specific skills list (like commercial judgment, credibility with mobile apps, product and technical fluency, etc). But we need to avoid thin sections. Might combine into Requirements. But the instruction: Prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements, Benefits, Pay. That's five sections. We must not include Schedule (no info). Benefits: we have "What we offer:" bullet list (excluding compensation range? Actually compensation range is separate but could be part of Benefits? But we have Pay separate). We'll put Benefits: Competitive equity..., Fully remote..., 4-5 weeks..., $2,000 workspace..., $1,000 stipend. Pay: Compensation Range: $259K. We must not include any boilerplate like "Curious about the interview process? Discover more in our blog post..." That's application instructions? It's about interview process, maybe considered boilerplate? It's not EEO but it's about interview process. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The line about interview process is application instructions, so we should remove it. Also remove "Compensation Range: $259K" is pay, keep. Now we need to ensure we preserve all substantive info. Let's extract the responsibilities paragraph in detail. Responsibilities paragraph (starting after "What you will be responsible for"): "Own Customer Growth strategy across the full customer base. Define how RevenueCat helps customers grow after they begin using the product, including named accounts, high-potential customers, specialist-assisted customers, scaled customers, and the long tail. Build segmentation and coverage. Use current value, future potential, adoption, intent, growth moments, risk, and strategic importance to decide who receives named CSM coverage, time-bound help, specialist advisory, scaled education, product-led guidance, or monitoring. Lead through the CSM Team Lead. Set the bar for customer context, account strategy, stakeholder management, growth diagnosis, adoption planning, commercial awareness, and follow-through. Develop the Team Lead and create a strong leadership bench rather than becoming the permanent CSM manager. Identify high-potential customers early. Work with Data, Product, Sales, Marketing, and Support to find customers with meaningful future potential before revenue alone makes them obvious. Govern Growth Advisory. Define intake, qualification, expected impact, output quality, follow-through, and reuse. Specialists should be deployed against specific high-value problems rather than become general-purpose consulting capacity. Make Growth Advocacy a customer-education channel. Ensure Growth Advocates turn real customer learning into authoritative one-to-many education for existing customers and the broader app ecosystem. Build Customer Enablement and Scaled Growth. Create the roadmap for lifecycle programs, templates, office hours, documentation, automation, product nudges, and next-best-action guidance. Drive meaningful product adoption. Partner with Product and Product Marketing so customers adopt RevenueCat capabilities in ways that help them win, rather than merely increasing feature activity. Create clear cross-functional decision rights. Define how Customer Growth works with Sales, TAM, Support, Product, Marketing, and Data without turning CSMs into AEs, TAMs into a catch-all, or collaboration into meeting theater. Build the customer-insight loop. Repeated customer questions should become product improvements, enablement, playbooks, benchmarks, documentation, lifecycle programs, and market education. Own the function. Set metrics, operating cadences, headcount plans, budget, organization design, executive communication, and the talent bar across Customer Growth." We need to turn each sentence into a
• . Could also keep as paragraphs but instruction: Use
  • for any list of duties/requirements/benefits. So we should make a list. Similarly for Requirements: "What you will need to be successful" paragraph: "Approximately 10 or more years in Customer Success, Customer Growth, strategic accounts, Growth Advisory, product growth, lifecycle, monetization, or an adjacent customer-facing function. Five or more years leading customer-facing teams, including managers, senior team leads, or specialist groups. Evidence of owning an entire function or multi-lane operating model, not only managing an individual CSM team. Experience building or materially rebuilding segmentation, coverage, strategic-account, adoption, health, advisory, or scaled-customer systems. Strong commercial judgment around NDR, renewal risk, expansion influence, customer value, and executive alignment. Credibility with mobile apps, app monetization, in-app purchases, paywalls, checkout, pricing and offers, lifecycle, retention, experimentation, analytics, or a closely adjacent domain. Enough product and technical fluency to lead around a developer-facing platform while preserving clear ownership for TAM, Support, and Engineering. Experience managing both generalists and specialists. Evidence of turning repeated one-to-one work into scalable systems. Strong written communication, directness, and remote-first operating habits. Evidence of hiring, coaching, performance management, and raising the leadership and talent bar." Then "Ideally, you" bullet list: "Ideally, you Have led CSMs and advisory, education, lifecycle, or enablement teams together. Have scaled a customer-facing function through a major company-growth stage. Have worked in a hybrid self-serve, product-led, and enterprise business. Have firsthand experience as an app operator, growth leader, founder, or consultant. Have built product-led or tech-touch Customer Success programs. Have helped productize or commercialize an advisory or professional-services capability." We should include those as list items as well. Now Benefits: "What we offer:" list: "Competitive equity in a fast-growing, Series C startup backed by top-tier investors, including Y Combinator" "10-year window to exercise vested equity options" "Fully remote and flexible work environment" "4-5 weeks of suggested time off annually for mental, physical, and emotional recharge" "$2,000 USD for workspace setup and $1,000 USD annual stipend for continuous learning" We need to keep each as
  • . Pay: "Compensation Range: $259K". Could be a

    or

    • . Since it's a single item, we can use

      . Now About the role: combine intro paragraph, The role paragraph, Why we are hiring for this role now paragraph. Let's extract "Why we are hiring for this role now" paragraph: "Why we are hiring for this role now RevenueCat serves tiny indie apps, fast-growing startups, games, media companies, health and fitness apps, AI products, marketplaces, and some of the most sophisticated consumer app businesses in the world. The app market is top-heavy, so the human touch must be allocated deliberately. At the same time, a customer that is small today may become strategically important very quickly. Contract status and current revenue are necessary signals, but they are not sufficient. We already have many of the ingredients: CSMs,