Customer Success Manager, Energy Analytics (US) | REQ 0043

We need to output HTML fragment with sections: About Us, Position Overview, Ideal Profile, What You'll Be Doing (maybe break into subsections?), Essential (What You'll Bring), Desirable, Why Join Zema Global? Possibly also Benefits? Not present. Pay/Schedule not present. So we include sections where content exists. We must use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title as heading. No Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO etc. The posting includes "Application Information" and "Equality, Diversity & Inclusion" which are boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove "Application Information" and "Equality, Diversity & Inclusion" sections. Also remove "Visa Sponsorship: Not available" maybe minor metadata; we can fold into a short

  or drop it. Probably drop. We need to preserve all substantive information. So we keep About Us, Position Overview, Ideal Profile, What You'll Be Doing (with subheadings? The subheadings are bolded: Customer Success Strategy, Strategic Customer Partnership, Onboarding and Enablement, Customer Success and Service Oversight, Internal Collaboration). Those are sub-sections within What You'll Be Doing. Should we treat them as headings? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid using

  for subheadings inside a section? Probably we can still use

  for each major section; subheadings could be

  but not allowed? Only

  specified for section headings. Could use

  for each major section and within that use

  or

  . For subheadings we could use or just keep as part of paragraph. Simpler: treat "What You'll Be Doing" as a section with

  and then list the duties as

  • . The subheadings inside can be part of each
  • text. Similarly "Essential What You'll Bring" and "Desirable" could be sections: Requirements/Qualifications? We'll use

    for Requirements (Essential) and

    for Desirable (maybe Skills). But we need to avoid thin sections. We'll combine Essential and Desirable into one "Requirements" section with two lists: Required and Preferred. However instruction: Prefer a few substantive sections over many thin ones. So we could have sections: About Us, Position Overview, Responsibilities (What You'll Be Doing), Requirements (Essential & Desirable), Benefits (Why Join Zema Global?). That seems good. We must not invent sections like Benefits unless posting actually states them. "Why Join Zema Global?" is basically benefits/culture. So we can make a section "Benefits" with that content. Now we need to extract content. About Us: paragraphs from "Founded in 1995..." to "...Think Big, Make It Happen, and Win as One." We'll keep that. Position Overview: paragraph starting "As a Customer Success Manager, you will act as a strategic partner..." until "...and Customer Success colleagues across Zema Global." Responsibilities (What You'll Be Doing): list of duties under headings. We'll create a

    with each duty as
    • . Need to capture all bullet points. Let's extract duties: Customer Success Strategy: - Collaborate with customers to establish strategic success roadmaps for cQuant adoption, including 3-month, 6-month, and 1-year plans. - Identify upsell, expansion, and cross-sell opportunities, partnering with the appropriate commercial teams and ensuring new products or services are successfully integrated into the customer relationship post-contract. - Monitor and promote best practices for using cQuant products and services to increase adoption and customer value. - Support retention and annual renewal activities in partnership with the Relationship Manager, proactively identifying risks and implementing strategies to prevent dissatisfaction or contract termination. - Establish a regular cadence of customer success, adoption, and value-review meetings to assess progress against customer objectives and identify opportunities to increase value from cQuant. Strategic Customer Partnership: - Serve as a primary point of contact and trusted advisor for assigned customers, supporting both strategic conversations and escalated customer issues. - Build strong relationships with customer stakeholders to understand their business objectives, energy-market use cases, and evolving needs, and align cQuant capabilities accordingly. Onboarding and Enablement: - Partner with the Customer Delivery team throughout onboarding, from implementation through live operation and continued expansion, maintaining regular engagement to support overall account success. - Provide occasional cQuant training and enablement to strengthen user understanding and product adoption. - Document customer use cases, success roadmaps, stakeholder maps, and other key account information to support effective customer management and continuity. Customer Success and Service Oversight: - Coordinate and communicate critical updates on platform functionality that may impact customer workflows. - Use Salesforce/Service Cloud, internal usage dashboards, CSM playbooks, and other customer-success tools to assess engagement and usage trends, monitor customer health, identify potential risks, and uncover opportunities for greater adoption or expansion. - Coordinate and monitor escalated customer concerns with the appropriate internal teams, ensuring issues are progressed effectively and resolutions align with customer expectations, without owning routine support-ticket resolution. Internal Collaboration: - Act as the voice of the customer within Zema Global, collaborating across Analytics, Product, Sales, Support, and other teams to address customer needs, share insights, improve the customer experience, and contribute to continuous improvement of products and services. - Maintain accurate and up-to-date customer records, interactions, use cases, and relevant account information in Salesforce CRM and other customer-success tools. Now Essential (What You'll Bring): List: - Bachelor’s or master’s degree in economics, mathematics, statistics, engineering, physics, finance, business, technology, or a related discipline, or equivalent relevant professional experience. - 2-5 years of experience in a customer-facing role within the energy sector, such as customer success, consulting, analytics, commercial support, account management, or technical support. - Working knowledge of wholesale energy markets and relevant customer use cases. Experience may include power markets, renewable or thermal generation, battery storage, energy finance, risk management, portfolio analysis, or deal structuring. - Ability to understand analytical or technical concepts and translate them into clear business value for customers. - Evidence of building trusted customer relationships and conducting strategic conversations about customer objectives, adoption, or business outcomes. - Commercial awareness and confidence discussing retention, renewal, expansion, cross-sell, or upsell opportunities. - Ability to collaborate across Analytics, Product, Sales, and other internal teams to resolve complex customer needs and represent the voice of the customer. Desirable: - Experience with an energy analytics, modelling, forecasting, risk, or portfolio-management platform. - Previous experience in energy-market consulting, customer success, analytics, or a customer-facing analyst role. - Experience using CRM or customer success platforms; Salesforce experience is beneficial but not required. - Experience using customer engagement or product-usage data to assess customer health, adoption, or expansion opportunities. - Familiarity with quantitative modelling, dashboards, business intelligence, or Python. - Experience working in a growing, changing, or cross-functional technology organisation. Why Join Zema Global? (Benefits): List bullet points: - Global Impact. Shape the future of energy, commodities, and financial markets through innovative technology. - Innovation at Scale. Work with cutting-edge software, advanced analytics, and complex data that solve real-world challenges. - Career Growth. Join a fast-growing global organization where your ideas, development, and career progression are valued. - Exceptional People. Collaborate with talented colleagues and industry experts across North America, Europe, and Asia. - Meaningful Ownership. Take ownership of your work, influence strategic initiatives, and make a measurable impact on our customers and business. - One Global Team. Be part of a collaborative culture built on trust, respect, and our values: Think Big. Make It Happen. Win as One. Now we need to output HTML fragment only, no /. Use

      for each section heading. Use

      • for lists. Use

        for prose paragraphs. We need to decide which content is prose vs list. About Us: multiple sentences; we can put in

        . Position Overview: one paragraph;

        . Responsibilities: we will make

        . Requirements: we can split into Required and Preferred maybe as two
        with headings? Could use

        but not allowed. Could just make one

        with all items, but we need to differentiate essential vs desirable. Could make two
        preceded by

        indicating Required and Preferred. That's fine. Benefits:

        . Now we need to ensure we don't include boilerplate like "Application Information" etc. Also drop location metadata? The location info is in the job requisition lines: "Job Req ID: REQ 0043 Location: Preference is given to candidates who can work in Denver, Colorado, Texas. However, we are also open to candidates based in Illinois, Arizona, Florida, Michigan, New Hampshire, Oklahoma, Tennessee, Utah, Wyoming, Massachusetts. (Please note that we are currently prioritising candidates based in the listed locations. If you are based elsewhere but feel your experience strongly aligns with the role, we still welcome your application) Department: Business Operations Work Model: Remote Position Type: Full-time, Permanent Employment Level: Mid-level individual contributor role Industry: Energy Data, Commodities & Financial Technology (FinTech) Reports To: Director of Operations, Analytics Visa Sponsorship: Not available". This is metadata; we should fold minor metadata into a short

        or drop it. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

        or drop it." So we could include a short paragraph at top summarizing location, work model, etc. But we might drop it as not substantive? It's location and work model; could be considered substantive. However the instruction says prefer few substantive sections; we could include a

        with location and work model details. Let's include a short paragraph after the heading? But we cannot add a heading for it; just a

        . We'll place it at the beginning. We need to preserve all substantive information; location and work model are substantive. So include a

        with that info. Let's craft: "Preference is given to candidates based in Denver, Colorado, or Texas, with openness to candidates in Illinois, Arizona, Florida, Michigan, New Hampshire, Oklahoma, Tennessee, Utah, Wyoming, Massachusetts. The role is remote, full‑time, permanent, mid‑level individual contributor within Business Operations, reporting to the Director of Operations, Analytics. Visa sponsorship is not available." Now we need to ensure we don't repeat job title as heading. No heading for job title. Now produce HTML. Structure:

        Preference is given to candidates based in Denver, Colorado, or Texas, with openness to candidates in Illinois, Arizona, Florida, Michigan, New Hampshire, Oklahoma, Tennessee, Utah, Wyoming, Massachusetts. The role is remote, full‑time, permanent, mid‑level individual contributor within Business Operations, reporting to the Director of Operations, Analytics. Visa sponsorship is not available.

        About Us

        Founded in 1995, Zema Global Data Corporation empowers organizations to simplify complexity, reduce risk, and make faster, more confident decisions that drive measurable results. Over the past two years, Zema Global has accelerated its growth through strategic investment and acquisition to strengthen our global leadership. Together we’re helping our customers gain a Decisioning Advantage - one bold idea at a time. With a presence across global energy, commodity, and financial markets, Zema Global empowers customers to simplify complexity, reduce risk, and make faster, more confident decisions that drive measurable results. At Zema Global, we Think Big, Make It Happen, and Win