Jobs · OTHR

Customer Success Manager

Amplify · United States · 1 mo ago
RemoteRemoteOTHRFull-time
We need to output HTML fragment with sections for headings where content exists. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. Must not include boilerplate like EEO, legal, application instructions. Must preserve substantive info. We need to parse the posting. Content: - About Amplify (company description) maybe not needed as heading? Could be part of About the role? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should include sections only if posting has real specific content. We have: About the role: The job description includes "Amplify is seeking a Customer Success Manager (CSM) to serve as the primary point of contact for our customers in the Strategic Region. In this role, you will own the customer experience from launch through ongoing partnership, ensuring a high-quality, outcomes-driven journey. You will manage account relationships, lead onboarding and implementation efforts, and provide ongoing support to help customers achieve their student achievement goals. The CSM acts as a trusted advisor, strategic thought partner, and coach, partnering cross-functionally to manage and grow a portfolio of accounts. You will drive retention, identify expansion opportunities, and ensure customers realize the full value of Amplify’s products. Whether supporting high-needs accounts or complex, multi-year implementations, you will mitigate risk and deliver measurable impact." That's substantive. So we can have

About the role

with

containing that paragraph(s). Could split into multiple paragraphs but okay. Responsibilities: The "Essential Responsibilities" section includes many bullet-like statements. We need to turn into

  • . The content includes subheadings like Account Ownership & Retention, etc. We could treat each bullet as list item. The subheadings themselves could be part of list items? Probably we can list each responsibility as a list item, preserving the text. We'll need to extract each responsibility line. Let's extract from the posting: Essential Responsibilities Account Ownership & Retention Own the Customer Journey: Own the entire customer journey for a defined book of business from launch through post-sale, acting as the accountable party for account success, retention, and renewal. Strategic Planning: Develop and execute advanced success plans aligned with customer goals to facilitate account expansion and retention. Cultivate robust partnerships with account leaders (instructional and technical) to develop long-term student achievement strategies and set multi-year goals. Trusted Advisor: Act as a consultant and coach to district leaders, defining and measuring the realization of curriculum objectives. Build trusting relationships with instructional and district leaders by applying knowledge of Amplify products, instructional best practices, and professional learning to the customer’s context. Serve as the primary point of contact, collaborating closely with internal teams to deliver a superior experience. Strategic Thought Partner: Serve as a strategic thought partner to district and school leaders, connecting Amplify’s products, professional learning, and implementation supports to local instructional priorities and student achievement goals. Deploy an understanding of education, teaching, and district implementation to help customers interpret evidence, identify opportunities, and make informed decisions. Implementation, Onboarding & Operations Project Management: Execute project plans for implementations (ranging from standard back-to-school launches to complex, multi-stream district deployments). Onboarding: Work with district/school personnel to define project priorities, ensuring launch readiness and success. Risk Management: Proactively identify risks and launch blockers; alert stakeholders and implement solutions or workarounds to keep projects on track. Operational Excellence: Leverage project tracking tools for consistency; maintain knowledge of project status to communicate effectively with internal and external partners. Build capacity of key stakeholders through regular cadence calls and by making connections to relevant product resources and professional development opportunities. Resource Coordination: Coordinate the development of Professional Learning plans and involve product specialists as needed to meet customer requirements. Business Value & Data Analysis Data-Driven Insights: Analyze usage and student performance data, and lead conversations with school and district leaders to set yearly implementation goals and align on progress toward them. Connect findings with instruction and student outcomes, and recommend targeted supports and action steps. Contract & Revenue Management: Develop a deep understanding of customer contracts to ensure compliance and proactively make recommendations. Capitalize on upsell opportunities, support renewal efforts, and identify additional upselling opportunities to contribute to overall business growth. Health Monitoring: Accurately report and monitor the health of customer engagements and drive corrective action plans where needed. Cross-Functional Collaboration, Product Expertise & Continuous Improvement Internal Partnership: Partner with internal teams to resolve customer issues, align on initiatives, and help inform the approach to customer lifecycle processes. Product Mastery: Maintain expertise across Amplify’s suite of products (focusing on Literacy and/or STEM) to advise accounts across all curriculum needs and support regional training efforts. Problem Solving: Determine the order and priority of account issues, coordinating with internal teams to remove barriers, advance implementation goals, and provide timely updates on resolution. We can treat each line after a heading as a list item. Could also keep the heading as part of list item text. Simpler: create a
      and each responsibility as
    • containing the sentence(s). We'll include all. Next: Personal Attributes section: "Personal Attributes Inspirational leader: Empowers team members and fosters a culture of collaboration.Resilient: Thrives in high-pressure environments, maintaining focus and composure under stress.Growth Mindset: Open-minded, receptive to feedback, and committed to continuous self-development.Professional: Displays humility, professionalism, and confidence in interactions with team members and key stakeholders.Continuous Improvement: Actively seeks opportunities to improve their own practice and advance customer outcomes, using feedback, evidence, and lessons learned to strengthen account and implementation support rather than maintaining the status quo." These could go under Requirements? Or Qualifications? The posting has Minimum Qualifications and Preferred Qualifications sections. Personal Attributes could be part of Requirements or Qualifications. Since we have sections for Requirements and Qualifications, we need to decide where to place personal attributes. Probably under Requirements (or Qualifications). The Minimum Qualifications includes Education, Experience, Strategic Partnership, Data Analysis & Communication, Skills, Project Management, Escalation Management, Communication (duplicate?), Strategic Skills, Independence, Schedule Flexibility. Preferred Qualifications includes Industry Knowledge, Subject Matter, Technical Proficiency, Experience, Professional Learning & Coaching, Strategic District Partnership. We need to map content accordingly. We must not repeat headings with filler. So we need to include sections only if there is real content. We have content for: - About the role (yes) - Responsibilities (yes) - Requirements (maybe Minimum Qualifications) - Qualifications (maybe Preferred Qualifications) - Skills (maybe part of Minimum Qualifications includes Skills, but we could also have a Skills section separate if there is distinct skill list. The Minimum Qualifications includes a "Skills:" line: "Excellent verbal, written, and presentation skills; ability to create district reports and meeting minutes." Also later "Communication: Exceptional communication and presentation skills, with the ability to engage and influence stakeholders at all executive levels." That's duplicated. We could combine into Skills section. But we already have a Skills heading possible. However we also have many skill-like items in Minimum Qualifications (Project Management, Escalation Management, etc.). Might be better to put those under Requirements or Qualifications. The instruction says use headings like Skills, Benefits, Pay, Schedule. We should only create those if posting actually states them. The posting does mention Skills explicitly (under Minimum Qualifications). So we can create a Skills section with that content. But we also have many other qualifications like Education, Experience, etc. Those could go under Requirements or Qualifications. Since we have both Requirements and Qualifications headings available, we can split: Requirements = Minimum Qualifications (education, experience, etc.) and Qualifications = Preferred Qualifications. But we also have Personal Attributes; could be part of Requirements or Qualifications. Might fit under Requirements as "Personal Attributes". But we don't have a heading for Personal Attributes; we could include them under Requirements as part of list. We need to avoid filler like "commensurate with experience". Not present. We need to remove boilerplate: EEO, legal, accommodation, background check, vaccination, E-Verify. Remove those. Also remove "About Amplify" company description? It's not a heading but could be considered part of About the role? The instruction says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should not include a heading "About Amplify". The company description could be omitted or placed under About the role? The About the role section is about the role, not company. But we could include a brief intro about company as part of About the role? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the company description somewhere. It is substantive. Where to put? Could be a preceding paragraph before About the role heading, as a

      . That's allowed: we can have a

      with company description before the headings. The instruction says use

      for section headings; doesn't forbid other

      outside sections. So we can output a

      with the Amplify overview, then

      About the role

      etc. Similarly, we need to not include "Job Description" heading. Thus final HTML: start with a

      containing the Amplify overview (the first paragraph about Amplify). Then

      About the role

      with

      containing the role description paragraph(s). Then

      Responsibilities

      with
      • ... each responsibility. Then

        Requirements

        with
        • for Minimum Qualifications items (Education, Experience, Strategic Partnership, Data Analysis & Communication, Skills, Project Management, Escalation Management, Communication, Strategic Skills, Independence, Schedule Flexibility). Also Personal Attributes could be added as list items under Requirements. Then

          Qualifications

          with
          • for Preferred Qualifications items. Then

            Skills

            maybe we already included Skills under Requirements; but we could still have a separate Skills section if we want to highlight skills. However we must not create a Skills section unless posting actually states them. The posting does state "Skills:" under Minimum Qualifications. So we could have a Skills section with that specific line(s). But we already used Skills inside Requirements; duplication may be okay but we risk repeating content. Better to follow instruction: we can have a Skills section with the skill details, and not duplicate them elsewhere. Then Requirements would exclude the Skills line. Let's parse Minimum Qualifications lines: Minimum Qualifications Education: Bachelor’s Degree or related work experience. Experience: 4+ years working in K–12 education with an understanding of teaching and learning, curriculum implementation, and the roles and priorities of district and school leaders. Strategic Partnership: Ability to serve as a credible strategic thought partner to educators and district leaders, translating complex implementation or achievement information into practical decisions and actions. Data Analysis & Communication: Ability to interpret customer data, identify meaningful patterns, and communicate concise, evidence-based recommendations to varied audiences. Skills: Excellent verbal, written, and presentation skills; ability to create district reports and meeting minutes. Project Management: Strong organizational skills with the ability to manage multiple projects in a fast-paced environment. Escalation Management: Proven track record in handling customer escalations and fostering positive resolutions. Communication: Exceptional communication and presentation skills, with the ability to engage and influence stakeholders at all executive levels. Strategic Skills: Strong strategic thinking, project management skills, and the ability to drive results independently. Independence: Resourcefulness, independent problem-solving ability, and comfort operating under ambiguity. Schedule Flexibility: Willingness to work a flexible schedule to support international accounts, as needed, including participating in calls or meetings during non-standard business hours. Note there is both Skills and Communication separate. Could combine but we can keep as separate list items. Thus Requirements section will contain all those except maybe we treat

Similar jobs