Director of Customer Success

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. Must not repeat job title as heading. Must not include Job ID etc. Must remove boilerplate like EEO, application instructions. Must preserve all substantive info. We need to parse the posting. Let's extract sections: - About your role: description of role (Director of Customer Growth & Success). This is prose. - Your team: description of team and what they'll get to do (list of responsibilities). Could be responsibilities. - To be successful in this role, you’ll also: list of items. - Your experience: list of must-haves (MBA, etc.) and other qualifications. - Your superpowers: list of skills/attributes. - Our culture: description of culture (maybe benefits? but not explicit pay/benefits). There's mention of competitive pay, full benefits, amazing perks (flexible PTO). So we have Benefits and Pay info. - About Givelify: company description (maybe not needed as section? Could be About the company but not required headings list; we can include as About the role? Actually About the role is separate. Could include a section About the company but not in allowed headings list. The allowed headings are limited to those; we should not add others. So we can incorporate company description into maybe About the role or maybe omit? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples; we can use those headings. Probably we should stick to those. We can include About the role (role description). Responsibilities (list of duties). Requirements (must-haves). Qualifications (maybe other qualifications). Skills (superpowers). Benefits (benefits mentioned). Pay (competitive pay). Schedule (maybe not mentioned; no schedule info, so omit). We must not create sections with placeholder text. Thus we need to extract content for each. Let's gather: About the role: The paragraph starting "About your role:As Director of Customer Growth & Success, you’ll lead the team..." etc. Also includes "Your team:" maybe part of responsibilities. But we can put About the role as the initial description: "As Director of Customer Growth & Success, you’ll lead the team that helps churches and nonprofits grow their giving through Givelify. You’ll drive outcomes like higher customer adoption rates, strong CSAT scores, and increased donor engagement. You’ll oversee strategy and execution for high-touch engagement, ensuring Customer Success Managers (meet targets such as Executive Business Review completion, no-show reduction, and number of customer touches. You’ll track key KPIs—product adoption, retention, and CSAT—and champion customer advocacy by surfacing insights, elevating the voice of the customer, and building strong, trust-based relationships with customers." We need to preserve all substantive info; we can keep that. Responsibilities: list from "Your team:In this position, you’ll get to:" bullet list. Also "To be successful in this role, you’ll also:" list. Also maybe from "Your team:" includes items like "Drive strategy and execution for high-touch customer engagement across the customer success team", etc. Also "Champion and scale customer success enablement programs", etc. Also "Analyze and act on customer health insights", etc. Also "Operationalize the voice of the customer", etc. Also "Collaborate with Product, Revenue Ops, Marketing, and Support", etc. Also "Pilot and evolve strategic programs on the Customer Success raodmap", etc. Also "Represent Customer Success in executive forums, planning cycles, and strategic initiatives". Also from "To be successful in this role, you’ll also:" items: "Use data and customer insights to guide strategy and course-correct quickly", "Coach and support CSMs with clear performance expectations and growth paths", "Maintain strong executive relationships with key customers", "Serve as a strategic thought partner on retention, growth, and product feedback", "Contribute to company-wide planning with customer-centric insights and success metrics". We'll combine these into a responsibilities list. Requirements: Must-haves: "MBA, or Master’s Degree", "5+ years of experience in Account Management, Customer Success and Growth at a company with a usage-based pricing revenue model", "2+ years leading customer-facing teams with measurable performance metrics". Also maybe "Strong background in high-touch customer engagement and success planning", "Proven track record managing KPIs tied to retention, engagement, CSAT, and program adoption", "Exceptional communication, coaching, and strategic thinking skills", "Experience working cross-functionally with Product, Ops, and Marketing teams", "Familiarity with tools like Salesforce, Gong, and customer health scoring frameworks", "Passion for helping mission-based organizations grow their impact", "Background in faith-based, nonprofit, or values-aligned organizations is a plus". These could be qualifications or requirements. We'll separate: Requirements = the must-haves (MBA, years experience, leading teams). Qualifications = other qualifications (strong background, proven track record, etc.). Skills = superpowers list. Benefits: "competitive pay with excellent benefits", "full benefits to help care for you today and in the future, amazing perks (including flexible PTO)". Also maybe "We take great pride in providing competitive pay, full benefits...". So we can list: competitive pay, full benefits, amazing perks (flexible PTO). Also maybe "We are a virtual team..." but that's culture. Pay: "competitive pay". Could be separate section. Schedule: none. We must not create sections with placeholder text. So we will include About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Omit Schedule. Now produce HTML: use

for each heading, then content:

for prose,

• for lists. We must not repeat job title as heading. So headings are as above. We must not include Job ID etc. We must not include boilerplate like EEO, legal, etc. Already removed. Now craft. About the role: combine paragraphs. Let's write:

  About the role

  As Director of Customer Growth & Success, you’ll lead the team that helps churches and nonprofits grow their giving through Givelify. You’ll drive outcomes like higher customer adoption rates, strong CSAT scores, and increased donor engagement. You’ll oversee strategy and execution for high-touch engagement, ensuring Customer Success Managers meet targets such as Executive Business Review completion, no-show reduction, and number of customer touches. You’ll track key KPIs—product adoption, retention, and CSAT—and champion customer advocacy by surfacing insights, elevating the voice of the customer, and building strong, trust‑based relationships with customers.

  Responsibilities: list items. We'll create
  with each responsibility. List items: - Drive strategy and execution for high-touch customer engagement across the customer success team - Own and improve key KPIs: Product Adoption Rate, Customer Retention Rate, # Of Donors using the product, CSAT (Customer Satisfaction Score), Customer Engagement Rate, EBR Scheduling and Completion Rate and No-Show Reduction, Number of High-Quality Customer Touches - Champion and scale customer success enablement programs (e.g., EBR playbooks, objection handling, success frameworks) - Analyze and act on customer health insights to retain, grow, and segment accounts - Operationalize the voice of the customer—turning feedback into product, process, and messaging improvements - Collaborate with Product, Revenue Ops, Marketing, and Support to deliver a connected customer experience - Pilot and evolve strategic programs on the Customer Success roadmap - Represent Customer Success in executive forums, planning cycles, and strategic initiatives - Use data and customer insights to guide strategy and course‑correct quickly - Coach and support CSMs with clear performance expectations and growth paths - Maintain strong executive relationships with key customers - Serve as a strategic thought partner on retention, growth, and product feedback - Contribute to company‑wide planning with customer‑centric insights and success metrics That seems comprehensive. Requirements: list must-haves. - MBA, or Master’s Degree - 5+ years of experience in Account Management, Customer Success and Growth at a company with a usage‑based pricing revenue model - 2+ years leading customer‑facing teams with measurable performance metrics Qualifications: list other qualifications. - Strong background in high‑touch customer engagement and success planning - Proven track record managing KPIs tied to retention, engagement, CSAT, and program adoption - Exceptional communication, coaching, and strategic thinking skills - Experience working cross‑functionally with Product, Ops, and Marketing teams - Familiarity with tools like Salesforce, Gong, and customer health scoring frameworks - Passion for helping mission‑based organizations grow their impact - Background in faith‑based, nonprofit, or values‑aligned organizations is a plus Skills: superpowers list. - Strategic thinker with a bias toward action and measurable outcomes - Empathetic leader who can coach, inspire, and hold a team accountable - Exceptional communicator and trusted customer advisor - Operationally savvy with an eye for improving systems and processes - Passionate about helping people do more good in the world Benefits: list. - Competitive pay - Full benefits (health, dental, vision, etc.) to help care for you today and in the future - Amazing perks, including flexible PTO Pay: maybe just a sentence: "Competitive pay." Could be a

  . We should not duplicate benefits and pay; but we have both sections. Benefits includes competitive pay; Pay section could just reiterate competitive pay. Might be redundant but okay. Could combine but instruction: prefer few substantive sections over many thin ones. Having both Benefits and Pay may be thin. Perhaps we can combine into Benefits section only, and omit Pay. Since Pay is mentioned as part of benefits, we can include Pay within Benefits. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state competitive pay and benefits. So we could have a Benefits section that includes both pay and perks. Then we don't need a separate Pay section. That reduces thin sections. Thus we will have About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. No Pay, no Schedule. Now Benefits content: combine. - Competitive pay - Full benefits to help care for you today and in the future - Amazing perks, including flexible PTO We could also mention "We take great pride in providing competitive pay, full benefits..." but that's fine. Now produce HTML. Check for any leftover boilerplate: we removed "Inc. 5000, the Stevies® Awards, Gartner, Forbes, and many more have recognized our story..." that's about company; we didn't include a section for that. Could we include as About the role? Not appropriate. Could we include as a separate section like "About Givelify"? Not in allowed headings; but we could incorporate into Benefits? No. The instruction says we should not invent sections; we can omit that info if not fitting headings. However we must preserve ALL substantive information. The company description is substantive. But we have no heading for it; we could incorporate into About the role? Not really. Could we add a section "About the company"? Not in allowed headings list but the instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not an exhaustive list; we could add other headings if needed. However they said "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections; but we could also use other headings if needed? The instruction: