Head of Customer Success
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content: description includes responsibilities, requirements, benefits. No explicit Pay or Schedule details (only remote work arrangement, with working hours aligned to U.S. East Coast – that's schedule info). So we can include Schedule section with that detail. Benefits section present. No explicit Pay (compensation to be determined) – we should NOT create Pay section because it's not specific; it's "Compensation and additional benefits to be determined according to the engagement terms." That's vague, not specific; we should not create Pay section. Also no Qualifications separate from Requirements? Could combine but we have Requirements section. Skills maybe part of Requirements; but we could still include Skills if we have explicit skills list. The posting includes "Strong proficiency with HubSpot, Salesforce, or similar CRM platforms." etc. Could put under Skills. But we need to avoid thin sections. Might combine Requirements and Skills into one Requirements section. However instructions: Use headings for those categories if we have content. We have content for About the role (intro paragraph). Responsibilities (list of accountabilities). Requirements (list). Benefits (list). Schedule (remote work arrangement). We'll not include Qualifications or Skills separately unless we have distinct content. We could put skills under Requirements. Let's parse. About the role: first paragraph(s) describing role. Responsibilities: list of accountabilities (starting with "Accountabilities" then bullet points). We'll convert each line after "Accountabilities" into
under Schedule heading. We must remove boilerplate: "This position is listed on behalf of a partner company..." etc. Also remove "How Jobgether Works", "Why Apply Through Jobgether?", data privacy notice, etc. Also remove "Opportunity to build and lead..." etc? That's benefits; keep. We need to preserve all substantive information. So keep the description about role, responsibilities, requirements, benefits, schedule. Let's extract. Original text: "This position is listed on behalf of a partner company, who manages all applications and next steps. Our partner is looking for a Head of Customer Success based in United States. This is a senior, hands-on leadership role responsible for shaping the entire post-sale customer experience within a fast-growing B2B SaaS environment. You will own retention, expansion, and adoption outcomes while developing the strategies and systems that support sustainable customer growth. Working closely with senior leadership, you will combine strategic direction with direct involvement in key customer relationships. You will lead and develop an expanding Customer Success team while establishing scalable playbooks across onboarding, adoption, renewal, and expansion. The role offers significant autonomy and the opportunity to build the Customer Success function during an important stage of company growth. Success will be measured through meaningful business outcomes, customer value, and recurring revenue rather than activity alone." That's About the role. Then "Accountabilities" list: - Own overall Customer Success strategy and execution, with direct accountability for retention, expansion, Net Revenue Retention (NRR), and churn outcomes. - Drive customer adoption by increasing both the breadth and depth of product usage across the customer base. - Coach, enable, and actively support the Customer Success team, stepping directly into strategic accounts when intervention or additional leadership is required. - Lead, develop, and scale the Customer Success organization as the business grows, including hiring and onboarding future team members. - Build and continuously refine a scalable Customer Success playbook covering onboarding, adoption, success planning, renewal, and expansion. - Establish customer success plans, health-scoring frameworks, account-management standards, and repeatable processes tied to measurable retention and expansion outcomes. - Partner closely with Sales, Product, and Engineering to communicate customer needs, surface opportunities, and represent the voice of the customer. - Maintain accurate visibility into customer health, risks, opportunities, and performance through HubSpot or comparable CRM systems. - Proactively identify accounts at risk as well as expansion opportunities, developing practical and actionable recommendations for leadership. - Build a culture of ownership and customer value, ensuring processes and team activity remain closely connected to business outcomes. - Use customer insights and performance data to continuously improve the Customer Success operating model. Then "Requirements" list: - Proven leadership experience in B2B SaaS Customer Success, including direct people-management responsibility. - Demonstrated experience owning retention and expansion metrics and coaching teams toward measurable commercial outcomes. - Hands-on leadership approach, with the ability to personally engage with strategic accounts while developing the team to operate effectively at scale. - Experience building, improving, or scaling Customer Success processes within an early-stage or high-growth company. - Strong understanding of the complete customer lifecycle, including onboarding, adoption, renewal, expansion, and account management. - Consultative and customer-focused mindset, with the ability to ask thoughtful questions, identify improvement opportunities, and recommend practical solutions. - Highly autonomous and proactive, able to identify priorities independently and take ownership without requiring extensive direction. - Strong proficiency with HubSpot, Salesforce, or similar CRM platforms. - Excellent analytical, organizational, communication, and stakeholder-management skills. - Exceptional written and spoken English. - Experience with customer health-scoring or Customer Success platforms such as Gainsight, Vitally, or similar tools is an advantage. - Familiarity with partner-led or channel-influenced Customer Success models is a plus. Then "Benefits" list: - Opportunity to build and lead a Customer Success organization within a rapidly growing SaaS environment. - Direct collaboration with founders and senior leadership on customer strategy and organizational development. - Significant ownership and autonomy in shaping Customer Success processes, playbooks, and team structures. - Exposure to strategic customer relationships and the opportunity to influence retention and expansion outcomes directly. - Entrepreneurial, low-ego working environment focused on ownership, execution, and measurable customer value. - Opportunity to work within an AI-native technology environment focused on modernizing partnership operations. - Remote work arrangement, with working hours aligned to the U.S. East Coast. - Opportunity for professional growth and leadership development as the organization scales. - Exposure to a broad range of B2B SaaS customer challenges and partner-focused business models. - Compensation and additional benefits to be determined according to the engagement terms. Note: The last bullet about compensation is vague; we might still include it as part of Benefits? It's still a benefit but vague. The instruction: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The compensation bullet says "Compensation and additional benefits to be determined according to the engagement terms." That's vague but still a statement; it's not a placeholder like TBD? It's basically saying to be determined. Might be considered filler. Safer to exclude that bullet from Benefits because it's not specific. However the instruction says never create Benefits section unless posting actually states them. It does state benefits (list). The compensation bullet is part of benefits but vague. We could keep it but risk being considered filler. I'd keep the other benefits and maybe drop that bullet. Schedule: remote work arrangement, with working hours aligned to the U.S. East Coast. That's specific enough for Schedule. Now produce HTML:
About the role
... (the paragraph(s) about role).
Responsibilities
- ... ...
Requirements
- ... ...
Benefits
- ... ...
Schedule
Remote work arrangement, with working hours aligned to the U.S. East Coast.
We must not include any extra text. Ensure we removed boilerplate like "This position is listed on behalf of a partner company..." etc. That's part of About the role? Actually first sentence is about partner company managing applications; that's meta about posting, not substantive role. Should we remove? It's not about the role; it's about the posting. Likely we should remove that line as it's not substantive about the role. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The first sentence is about the partner managing applications; it's not about the role but could be considered application instruction? It's about who manages applications. Might be considered boilerplate. Safer to remove it. Start from "Our partner is looking for a Head of Customer Success based in United States." That's substantive. Thus About the role paragraph: "Our partner is looking for a Head of Customer Success based in United States. This is a senior, hands-on leadership role responsible for shaping the entire post-sale customer experience within a fast-growing B2B SaaS environment. You will own retention, expansion, and adoption outcomes while developing the strategies and systems that support sustainable customer growth. Working closely with senior leadership, you will combine strategic direction with direct involvement in key customer relationships. You will lead and develop an expanding Customer Success team while establishing scalable playbooks across onboarding, adoption, renewal, and expansion. The role offers significant autonomy and the opportunity to build the Customer Success function during an important stage of company growth. Success will be measured through meaningful business outcomes, customer value, and recurring revenue rather than activity alone." Now Responsibilities list as above. Requirements list as above. Benefits list: we need to include all except the compensation bullet. Let's list: - Opportunity to build and lead a Customer Success organization within a rapidly growing SaaS environment. - Direct collaboration with founders and senior leadership on customer strategy and organizational development. - Significant ownership and autonomy in shaping Customer Success processes, playbooks, and team structures. - Exposure to strategic customer relationships and the opportunity to influence retention and expansion outcomes directly. - Entrepreneurial, low-ego working environment focused on ownership, execution, and measurable customer value. - Opportunity to work within an AI-native technology environment focused on modernizing partnership operations. - Remote work arrangement, with working hours aligned to the U.S. East Coast. (But we moved this to Schedule; maybe we should not duplicate. Since we have Schedule section, we could omit this from Benefits to avoid duplication. However the benefit list includes remote work arrangement; we could keep it in Benefits and not have separate Schedule. But we decided to have Schedule section. To avoid duplication, we could keep remote work in Benefits and not have Schedule. But the instruction: create Schedule section only if posting actually states them. It does state remote work arrangement with hours aligned to US East Coast. That's schedule info. So we could have Schedule section with that sentence, and we could still keep other benefits. It's okay to have remote work mentioned also in Benefits? Might be duplication but not prohibited. However we should avoid duplicated lines. The instruction: Remove duplicated lines. So we should not repeat the same sentence in two places. So we should either put remote work in Benefits or Schedule, not both. Since we have a Schedule section, we put it there and remove from Benefits. Thus Benefits list excludes that bullet. Now Benefits list (9 items? Let's count): 1 Opportunity to build and lead a Customer Success organization within a rapidly growing SaaS environment. 2 Direct collaboration with founders and senior leadership on customer strategy and organizational development. 3 Significant ownership and autonomy in shaping Customer Success processes, playbooks, and team structures. 4 Exposure to strategic customer relationships and the opportunity to influence retention and expansion outcomes directly. 5 Entrepreneurial, low-ego working environment focused on ownership, execution, and measurable customer value. 6 Opportunity to work within an AI-native technology environment focused on modernizing partnership operations. 7 Opportunity for professional growth and leadership development as the organization scales. 8 Exposure to a broad range of B2B SaaS customer challenges and partner-focused business models. (We omitted compensation bullet.) Now Schedule section