Senior CRM Manager

We need to output HTML fragment with sections for headings present in posting: About the role? Actually posting includes "About Bask & Lather Co.", "The Opportunity", "What You Will Own", "What Success Looks Like", "What You Bring", "Who You Are". Also maybe "Responsibilities" etc but not present. We need to use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). However we should only include sections when posting has real specific content. The headings we have: About Bask & Lather Co. (but that's about company, not role). The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should map content to those standard headings if appropriate. But we can also use other headings? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings when applicable. However we have sections like "About Bask & Lather Co." maybe we could treat as "About the role"? Not exactly. Could we omit that? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." It doesn't forbid other headings. It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those headings for sections we have. We need to map content: - About Bask & Lather Co. -> could be "About the role"? Not exactly. Maybe we can treat as "About the role" describing the role? But it's about company. Could we omit? The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we need to include sections that have content. We have content about company, opportunity, responsibilities (What You Will Own), success metrics (What Success Looks Like), qualifications (What You Bring), personal attributes (Who You Are). So we can map: - About the role: maybe combine "About Bask & Lather Co." and "The Opportunity". But better to have separate sections: "About the role" could be the opportunity description. However we have "About Bask & Lather Co." which is about company; maybe we can put that under a generic "About the company" but not in list. Since not in allowed list, maybe we should not create a heading for it; we could just put that content in a

without heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests we should use those. Safer to stick to those headings and map content accordingly. Thus we can have sections: - About the role: include "The Opportunity" description (the role overview). Could also include brief about company? Might be okay. - Responsibilities: "What You Will Own" (detailed responsibilities). - Requirements: "What You Bring" (qualifications). - Skills: maybe not separate; could be part of Requirements. - Qualifications: maybe same as Requirements. But we need to avoid duplicate thin sections. Better to have: About the role, Responsibilities, Requirements. Possibly also "Qualifications" if distinct. But we have "What Success Looks Like" which is performance expectations; could be under "Responsibilities" or separate "Performance Expectations". Not in list. Could we create a custom heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot use other headings, but it's implied we should use those. However "What Success Looks Like" is not in list; we could treat as part of Responsibilities or maybe as "Qualifications"? Not ideal. Maybe we can create sections: About the role, Responsibilities, Requirements, and then include "What Success Looks Like" as a

under Responsibilities? Or as a separate section with heading "Performance Expectations" but that's not in the list; risk of being considered filler? The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid custom headings, just says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). I think we can still use other headings as long as they are

. But to be safe, we can map to the given headings. Thus: - About the role: combine "About Bask & Lather Co." and "The Opportunity". Provide description. - Responsibilities: "What You Will Own". - Requirements: "What You Bring". - Qualifications: maybe not needed; we could omit. - Skills: maybe not needed. - Benefits, Pay, Schedule: not present, so omit. We also have "Who You Are" which is personal attributes; could be part of Requirements or maybe a separate "Qualifications"? Could treat as "Qualifications". But we already have Requirements for experience/skills; Who You Are is about traits. Could be part of Requirements as well. We could create a section "Qualifications" for Who You Are. But we need to avoid thin sections. It's substantive. Thus we could have: - About the role - Responsibilities - Requirements - Qualifications Each with appropriate content. Let's extract content. About Bask & Lather Co.: "Bask & Lather Co. is a fast-growing, family-founded textured haircare brand built on a scalp-first philosophy, authentic results, and a deeply engaged community. We serve customers across our website, app, TikTok Shop, Amazon, Walmart, and emerging channels. Our mission is to help customers grow it and keep it too." The Opportunity: "We are seeking a hands-on Senior CRM Manager to own the execution and performance of our customer relationship marketing program. You will lead email and SMS campaigns, build and improve automated journeys, and turn customer insight into stronger repeat purchase, subscription retention, and long-term value. Q4 execution is an immediate priority, alongside building a durable lifecycle program. This is a working manager role. You will set priorities, work directly in Klaviyo, review every major send for accuracy, analyze performance, and coach our CRM Coordinator. You will partner with the future Director of Retention & Customer Lifecycle, who will own the broader retention strategy, budget, and department roadmap." Combine. Responsibilities (What You Will Own): List bullet points: - Campaign Strategy and Q4 Execution - Own the email and SMS calendar for launches, education, promotions, replenishment, and engagement. - Translate business priorities into briefs, audience plans, creative requirements, send schedules, and measurable goals. - Lead Black Friday/Cyber Monday and holiday CRM planning, including offers, segmentation, contact frequency, contingency plans, and recaps. - Partner with Brand, Creative, E-Commerce, Growth, Product, and CX to deliver timely, accurate messages. - Establish pre-send QA for audience, consent, suppression, offer, inventory, links, rendering, timing, and tracking. - Lifecycle and Retention - Audit, build, and optimize welcome, browse and cart abandonment, post-purchase, education, replenishment, cross-sell, winback, and subscription journeys. - Segment first-time, repeat, high-value, lapsed, and subscription customers using purchase behavior, product interest, and engagement. - Improve second purchase, frequency, subscription save and renewal, and customer lifetime value. - Collaborate with Subscription, CX, and E-Commerce on friction that requires changes beyond messaging. - Coordinate email, SMS, and relevant app messaging so the customer experience remains coherent. - Klaviyo, Data, and Operations - Serve as a hands-on Klaviyo owner for campaigns, flows, segments, templates, testing, and reporting. - Help complete and stabilize the email and SMS migration to Klaviyo. - Validate customer data, consent and suppressions, event tracking, flows, integrations, and deliverability before and after cutover. - Partner with E-Commerce and technical resources on Shopify, subscription, and other customer events. - Create documentation, naming conventions, approval workflows, and repeatable QA checklists. - Protect list health, deliverability, and customer preferences while operating an ambitious calendar. - Measurement and Leadership - Own weekly CRM reporting across campaign and flow results, customer cohorts, repeat purchase, subscription behavior, list health, and testing insights. - Build a prioritized test plan for audiences, content, timing, offers, and journeys. Use baselines and holdouts where feasible to assess incremental impact. - Manage, coach, and set priorities for the CRM Coordinator. Review work and build technical and analytical skills. - Manage agency or freelance support when needed and flag capacity, data, creative, or launch risks early. We need to turn each bullet into

• . Could group under headings? The instruction: Use
  • for any list of duties/requirements/benefits, and

    for prose. So we can have a

    for each major bullet group? Or we can just make a single
    with all items. But we have subheadings inside. Could we keep subheadings as

    bold? Not allowed? We could keep subheadings as

    with strong? But we must not invent headings. Probably better to just make a flat list of all responsibilities. However that loses grouping but still preserves all info. Could also keep subheadings as

    and then lists under them. That seems acceptable: use

    for prose (subheadings) and

    • for list items. Thus for Responsibilities section: we can have

      Campaign Strategy and Q4 Execution

      then
      with its items, then

      Lifecycle and Retention

      then
      , etc. Similarly for Requirements (What You Bring) list: - 5+ years in CRM, lifecycle, retention, or email and SMS marketing, with substantial consumer e-commerce experience. - Deep, hands-on Klaviyo experience building and troubleshooting flows, segments, campaigns, and reporting. - Experience leading a high-volume promotional calendar while protecting deliverability and customer experience. - Strong grasp of segmentation, testing, purchase cohorts, retention economics, and lifecycle measurement. - Experience with Shopify and comfort diagnosing customer data and event quality. - Strong project management, copy and creative judgment, attention to detail, and comfort making decisions under tight deadlines. - Experience managing or coaching a coordinator or small team. - Subscription, beauty or personal care, mobile app, and multichannel experience are pluses. We can just make a
      . Qualifications (Who You Are) content: "You combine commercial judgment with careful execution. You can build a flow yourself, challenge an unconvincing metric, give clear feedback, and catch a broken offer before it reaches customers. You take ownership of results and develop the people around you." That's prose, so

      . Now we need to output only HTML fragment, no /, no markdown. Thus:

      About the role

      ... combined text ...

      Responsibilities

      Campaign Strategy and Q4 Execution

      • Own the email and SMS calendar for launches, education, promotions, replenishment, and engagement.
      • Translate business priorities into briefs, audience plans, creative requirements, send schedules, and measurable goals.
      • Lead Black Friday/Cyber Monday and holiday CRM planning