Account Manager

We need to produce semantic HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading (none given). Must not include Job ID etc. Must preserve all substantive info, remove boilerplate like EEO, legal, application instructions, etc. Also remove "a Note On How To Reach Us" etc. Also remove "Foundant is an equal opportunity employer..." etc. Also remove "If you have accessibility requirements..." etc. Also remove "We're truly grateful..." etc. Also remove "To apply for open positions, please visit our careers page..." etc. Also remove "Foundant is an equal opportunity employer..." etc. We need to extract sections: - About Foundant (company description) maybe "About the role"? Actually "About Foundant" is about company. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to those headings. The posting includes: About Foundant (company description) – could be "About the role"? Actually "About the role" is about the job, not company. But we have no explicit "About the role". We have "Where You’ll Work", "What You’ll Do", "What You’ll Need", "What You’ll Bring To Our Team Dynamics", "Why You’ll Love Working At Foundant". We need to decide which headings to use. We have responsibilities: "What You’ll Do" list. We have requirements/qualifications: "What You’ll Need" (required) and "Preferred Experience" etc. Also "What You’ll Bring To Our Team Dynamics" (skills/attributes). Could map to Requirements, Qualifications, Skills. We have benefits: "Why You’ll Love Working At Foundant" includes competitive salary and benefits, tuition, lifestyle reimbursements, bespoke mindfulness and fitness initiatives, Flexible PTO, professional development, internal mobility, autonomy, recognition. Also mention competitive salary but not specific numbers. Since we cannot create Pay section unless posting actually states them. It says "competitive salary and benefits" but no specific numbers. The rule: 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. Does "competitive salary and benefits" count as stating them? It's vague but it's stating that there is competitive salary and benefits. Might be acceptable to include Benefits section with those details. Pay section would need actual salary numbers or range; not present, so omit Pay. Schedule: remote-first workplace, flexibility, office locations. That is schedule info. The posting says "As a remote-first workplace, we believe in offering flexibility and the freedom to work where it suits you best". That's schedule/flexibility. So we can include Schedule section with that content. We must not include boilerplate like EEO etc. We need to output only HTML fragment, using

for each section heading,

• for lists,

  for prose. We need to preserve all substantive information. Let's extract. Sections: - About the role? Could use "About Foundant" as "About the role"? Might be better to use "About the role" heading and put company description there? But the instruction says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those exact headings where appropriate. So we should map content to those headings. Thus we need sections: - About the role: maybe a brief description of the role? We have "What You’ll Do" (responsibilities) and "Where You’ll Work". There's no explicit role summary besides those. Could combine "About the role" with a short paragraph summarizing the role: building relationships, managing renewals, etc. But we must not invent or summarize away detail. We can use the existing prose that describes the role: maybe the first paragraph under "What You’ll Do"? Actually "What You’ll Do" starts with "You'll build and maintain strong, trusted relationships..." That's responsibilities. There's no separate role summary. Could we put "About the role" heading and then put the first sentence of "What You’ll Do"? That would be duplicating content. Better to not create About the role if we don't have distinct content. The rule: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. If we don't have a distinct "About the role" summary, we could omit that section. However we need to preserve all substantive information; we can put the role description under Responsibilities or similar. The instruction says we can prefer a few substantive sections over many thin ones. So we could omit About the role and just have Responsibilities, Requirements, Qualifications, Skills, Benefits, Schedule. But we need to map content to allowed headings. Let's see what we have: - Responsibilities: "What You’ll Do" list (bullet points). Good. - Requirements: "What You’ll Need" (required). Also "Must be legally eligible to work in Canada or the United States". That's a requirement. - Qualifications: maybe "Preferred Experience in the nonprofit, philanthropic, or government sectors" and "Understanding of SaaS metrics and client health scoring". Could be qualifications. - Skills: "What You’ll Bring To Our Team Dynamics" includes Adaptive Achievement, Productive Collaboration, Service Orientation, Business Insight. Those are skills/attributes. - Benefits: "Why You’ll Love Working At Foundant" includes competitive salary and benefits, tuition, lifestyle reimbursements, bespoke mindfulness and fitness initiatives, Flexible PTO, professional development, internal mobility, autonomy, recognition. - Schedule: remote-first workplace, flexibility, office locations (Bozeman, MT; Toronto, Canada; Dublin, Ireland). Also mention working remotely or from office. - Pay: not specific, omit. Thus we will output sections: Responsibilities, Requirements, Qualifications, Skills, Benefits, Schedule. We need to use

  for each heading. Inside each, we need to preserve all substantive info. Let's extract exact text. Responsibilities (What You’ll Do): - You'll build and maintain strong, trusted relationships with clients across our portfolio, serving as a strategic advisor and advocate — because renewals are built on relationships, not just contracts - You'll own the renewal process end to end and proactively identify upsell and cross-sell opportunities aligned with client goals and product capabilities - You'll track and assess client engagement, satisfaction, and usage metrics to ensure high retention and get ahead of churn risk - You'll partner closely with Customer Success to align on client needs, share feedback, and coordinate efforts that drive client success — because we do more good when we work together - You'll develop account plans for key clients, outlining growth strategies, risk mitigation, and engagement tactics - You'll maintain a deep understanding of Foundant, GivingData, and SmartSimple offerings so you can guide clients toward the solutions and outcomes that matter most to their mission - Other duties as assigned We need to keep "Other duties as assigned". It's substantive. Requirements (What You’ll Need): - 3+ years of experience in account management, customer success, or a related role in SaaS or technology environments - A proven track record of managing renewals and driving upsell/cross-sell outcomes - Experience working cross-functionally in a fast-paced, client-centric environment - Familiarity with CRM tools (e.g., Salesforce) and customer success platforms - Must be legally eligible to work in Canada or the United States Qualifications (Preferred): - Preferred Experience in the nonprofit, philanthropic, or government sectors - Understanding of SaaS metrics and client health scoring Skills (What You’ll Bring To Our Team Dynamics): - Adaptive Achievement: Owns a full renewal pipeline independently — juggling multiple accounts and deadlines, and adapting account plans as client needs and priorities shift - Productive Collaboration: Builds trusted, cross-functional relationships with Customer Success and other internal teams to keep client outcomes aligned, because we do more good together - Service Orientation: Anticipates client needs before renewal conversations happen, understanding that a client's success is what makes the relationship — and the business — sustainable - Business Insight: Understands how Foundant, GivingData, and SmartSimple solutions drive measurable outcomes for organizations in the philanthropic and social good sector, and uses that knowledge to identify genuine upsell and cross-sell opportunities Benefits (Why You’ll Love Working At Foundant): We need to extract the benefits paragraph: "At the heart of everything we do is a commitment to innovation and making a positive impact. Whether you’re working on projects that empower not-for-profits, community foundations, or corporations, your contributions will help drive real-world change. We offer competitive salary and benefits, including tuition, and lifestyle reimbursements, and bespoke mindfulness and fitness initiatives. With our Flexible PTO policy, you’ll have the freedom to manage your time in a way that supports your personal well-being and professional success. We’re committed to your professional and personal development. With our merger, you'll have the chance to collaborate across teams, giving you exposure to diverse ideas, expertise, and projects that span multiple industries. As part of a larger organization, you’ll have even more opportunities to grow your career. Whether it’s exploring new roles, leadership opportunities, or shifting to a different department, we support internal mobility to help you achieve your career goals You’ll enjoy autonomy and responsibility, empowering you to approach your work creatively and independently, fostering innovation and independent thought. Employee recognition is a core part of our culture. When you do a great job, we make sure everyone knows about it!" Note there is a typo: "including tuition, and lifestyle reimbursements, and bespoke mindfulness and fitness initiatives." We'll keep as is. We should also note that the sentence "We offer competitive salary and benefits, including tuition, and lifestyle reimbursements, and bespoke mindfulness and fitness initiatives." includes "competitive salary and benefits". Since we are not making a Pay section, we can include that in Benefits. Schedule: - As a remote-first workplace, we believe in offering flexibility and the freedom to work where it suits you best, while staying connected through technology. - Our global network of talent is supported by physical office hubs and virtual collaboration, fostering a dynamic environment where innovation and growth thrive. - With office locations in Bozeman, MT, Toronto, Canada, and Dublin, Ireland, you'll be part of a globally connected team. - Whether you're working remotely or from one of our office locations, you'll be contributing to a vibrant, collaborative culture focused on driving meaningful impact across the world. We need to ensure we don't include boilerplate like "Foundant is an equal opportunity employer..." etc. Remove that. Also remove "a Note On How To Reach Us" etc. Now produce HTML. We'll wrap each section in

  Heading

  then content. For lists, use
  • items. For prose, use

    . We need to decide which content is list vs prose. Responsibilities: list of duties ->

    • each bullet. Requirements: list ->
      • . Qualifications: list ->
        • . Skills: list ->
          • (each bullet includes a bold label? We can keep as is. Benefits: prose ->

            (maybe multiple paragraphs). Could split into multiple

            for readability but not required. We'll keep as one

            containing the benefits text. Schedule: could be

            or

            . It's descriptive; we can use

            with multiple sentences. Could also use

            but not required. We'll