Enterprise Customer Success Manager

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes Position Summary (which could be About the role). Responsibilities section present. Requirements? There's a "You Must Have" list which are requirements. Also "About Us" maybe not needed. There's "What We Offer" which includes benefits, pay, etc. There's mention of "Market competitive pay leveraging Carta data" but no specific numbers. That's vague; we should not create Pay section unless posting actually states them. It says "Market competitive pay leveraging Carta data" - that's not specific numbers, but it's still a statement about pay. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Market competitive pay leveraging Carta data" which is a statement about pay, albeit vague. Should we include Pay section? It says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state something about pay, so we could include a Pay section with that statement. However also "What We Offer" includes many benefits: Employee recognition through Bonusly, 401(k) with match, Unlimited PTO, supportive time off, employer-contributed healthcare benefits, parental leave, community events. Those are benefits. So we can include Benefits section with those details. Schedule? Not mentioned. So we omit Schedule. We also need About the role: could be Position Summary plus maybe About Us? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content. We have Position Summary: "We are looking for an Enterprise Customer Success Manager..." That's about the role. We'll put that under

About the role

as

. Responsibilities: we have a big list. We'll put under

Responsibilities

with

• each item. Requirements: The "You Must Have" list. Those are requirements. We'll put under

  Requirements

  with
  • . Qualifications? Not separate; maybe we could treat "You Must Have" as qualifications. But we already used Requirements. Could also have Qualifications but we don't have separate content. We'll omit Qualifications. Skills: Could be derived from requirements but we might not need separate Skills section if not distinct. The instruction: prefer a few substantive sections over many thin ones. So we could combine Requirements and Skills? But we have explicit list of skills like Technical Proficiency, Sales Acumen, Project Management, Proficiency in working with CRMs, etc. Those could be Skills. However we already have Requirements list includes those. To avoid duplication, we could keep Requirements as the list and not add Skills. Or we could split: Requirements (nonprofit tech experience, customer-centric focus, relationship building, proactive problem-solving, collaborative mindset) and Skills (technical proficiency, sales acumen, project management, proficiency with CRMs, email marketing). But the instruction says only include section when posting has real specific content. It does have those specifics. So we could make two sections: Requirements and Skills. However we need to avoid thin sections. But each would have multiple items. That's okay. Let's parse the "You Must Have" list: - Customer-Centric Focus: Deep understanding of customer needs and a passion for ensuring their success with Virtuous products. - Nonprofit Tech Experience: Direct experience working with nonprofit customers in a B2B SaaS environment, with a real understanding of how nonprofits operate and fundraise. - Relationship Building: Strong propensity for relationship building, enjoying forming and maintaining meaningful customer relationships. - Proactive Problem-Solving: Proven ability to identify and address customer issues before they escalate, demonstrating a proactive and solution-oriented approach. - Collaborative Mindset: Ability to collaborate effectively with cross-functional teams, ensuring seamless communication and a unified customer-centric approach. - Technical Proficiency: Strong technical acumen to provide product support and guidance. - Sales Acumen: Ability to identify upsell and cross-sell opportunities based on a deep understanding of the client’s use-case and needs. - Project Management: Organizational skills, with the ability to prioritize effectively along with critical thinking abilities to balance customer needs with Virtuous' objectives. - Proficiency in working with CRMs, email marketing, and other technology. We could split: Requirements: first five (customer-centric, nonprofit tech, relationship building, proactive problem-solving, collaborative mindset). Skills: technical proficiency, sales acumen, project management, proficiency with CRMs/email marketing. But the instruction says prefer a few substantive sections over many thin ones. Having two sections each with ~4-5 items is fine. Now Benefits: from "What We Offer". We'll list each benefit as
  • . Pay: we have "Market competitive pay leveraging Carta data". That's a statement. We'll put under

    Pay

    with

    Market competitive pay leveraging Carta data.

    Schedule: none, omit. Now we need to remove boilerplate: navigation, legal, EEO, scam warning etc. The posting includes a scam warning paragraph at the end. We must remove that. Also remove "About Us" maybe? It's not a required heading but could be considered part of About the role? The instruction says do not repeat job title as heading. About Us is not required; we could omit it because it's not under the specified headings. However it contains substantive info about company mission and values. Could we include it under About the role? Possibly we could extend About the role paragraph to include that? But the instruction says use headings for those specific categories; we can also include extra paragraphs not under headings? The instruction: Output ONLY the HTML fragment. It didn't forbid extra paragraphs outside headings, but we should follow the structure: use headings for sections. It didn't say we cannot have other paragraphs. However to be safe, we could include About Us as part of About the role section (maybe as a second paragraph). But the About the role heading is for role description; About Us is company description. Might be okay to include as a separate

    About the company

    but that's not in the allowed list. The allowed list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not add other headings. So we should incorporate About Us content into About the role paragraph or maybe omit it. The instruction: "Prefer a few substantive sections over many thin ones." Including About Us as a separate paragraph under About the role could be okay. Let's add a second

    under About the role containing the About Us content (mission, values). That keeps it within the allowed heading. Now we need to ensure we don't include any boilerplate like "We’ve recently noticed an increase in recruitment scams..." Remove that. Now produce HTML:

    About the role

    Position Summary ...

    About Us ...

    Then

    Responsibilities

    with
    items. Then

    Requirements

    with
    items (first five). Then

    Skills

    with
    items (technical proficiency, sales acumen, project management, proficiency with CRMs, email marketing, other technology). Then

    Benefits

    with
    items. Then

    Pay

    with

    Market competitive pay leveraging Carta data.

    No Schedule. Now we need to extract the exact text for each item, preserving all substantive information, not inventing or summarizing away detail. Let's copy the Position Summary text exactly: "Position Summary We are looking for an Enterprise Customer Success Manager to join our growing Customer Success Team. As an Enterprise Customer Success Manager, you will report to the Manager of Enterprise Customer Success and will be focused on our largest and most strategic customers' product adoption, utilization, and overall satisfaction. We're looking for people who bring both nonprofit expertise and SaaS experience to the table, ideally in nonprofit technology. Whether you've spent years serving the sector from inside a tech company or you're a nonprofit leader who's fallen in love with software, your blended background is exactly what makes this role exciting. In this role, you will work closely with teams across the company including Marketing, Sales, and Revenue Enablement to help maximize our growth. Your responsibilities will include supporting strategic enterprise-level customers in strengthening their donor relationships, selling upgrades and add-ons to our current customers, and working on renewals of annual contracts. You will serve as the primary point of contact for our nonprofit customers, collaborating closely with them to understand their unique needs, goals, and challenges. By leveraging your expertise in both our platform and the nonprofit industry, you will drive adoption, retention, and expansion initiatives, ultimately contributing to the long-term success and growth of our customers." We need to ensure we keep that as a paragraph. Might need to add a space after "Position Summary". We'll just output the sentences. Now About Us text: "Virtuous software is powering the world’s leading nonprofits and inspiring a new generation of generosity. At Virtuous, we believe generosity has the power to transform the world - and so we are on a mission to create $10B in net new generosity by helping nonprofits better connect with and inspire their donors. Our talented team is hungry, humble, and committed to delivering best-in-class software solutions, customer success interactions, and sales experiences to the nonprofit community. Our Values Are More Than Just a Poster On The Wall. Instead, Our Mission And Values Are Precisely Why Candidates Choose Virtuous. Our Core Values Are Build Better: We build audacious ideas to accelerate philanthropy and dismantle the status quo.Display Radical Generosity: We are generous with our time & talent as we serve our team and the nonprofit community.Stay Humble & Enjoy the Journey: We take our work seriously, but we don't take ourselves too seriously. Virtuous should act as a career accelerator for everyone on our team. Team members should look back at their time at Virtuous as one of the most productive and stretching seasons in their professional lives. This means that working at Virtuous isn't for everybody. It is for the select few who are ready to do hard things and build something truly great. If this sounds like you, we’d love for you to apply!" We need to keep that as a paragraph. Note there are some missing spaces after colons (e.g., "status quo.Display"). We'll keep as is. Now Responsibilities list: we need to extract each bullet from the responsibilities section. The responsibilities section includes headings like "Customer Relationship Management:", "Proactive Issue Resolution:", etc. Each has a sentence. We'll turn each into
    • . Let's copy them exactly: - Customer Relationship Management: Serve as a dedicated point of contact, accompanying customers on their journey from sales closure through the entire lifecycle. Cultivate deep, meaningful multi-threaded relationships, ensuring customer loyalty and trust with all key stakeholders for optimized product adoption. - Proactive Issue Resolution: Anticipate customer issues and proactively address them before they escalate. Your proactive approach distinguishes you from traditional customer service, turning potential problems into opportunities for customers and Virtuous alike. - Strategic Account Expansion: Understand each customer’s unique needs, allowing you to suggest innovative solutions that enhance their success with our products. Identify organic upsell opportunities by comprehensively understanding their use-case, ultimately driving business growth. - Advocacy and Collaboration: Advocate for Virtuous by generating excitement about upcoming product launches and updates. Collaborate with internal teams including customer success, sales, support, and product, voicing customer concerns and needs and ensuring a customer-first approach company-wide. - Product Expert: Provide strategic product support and comprehensive guidance on best practices. Your expertise ensures customers seamlessly adopt our products, enhancing their overall experience and deepening customer trust. - Issue Identification and Resolution: Handle complex customer issues with efficiency and professionalism. Offer tailored product and service solutions to address customer pain