Senior CRM Marketing Manager

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No Job ID. Remove boilerplate like EEO, disclaimer, etc. Also remove navigation/cookie/legal. Keep substantive info. We need to parse the posting. Content: - Our Story (intro) about company: could be "About the role"? Actually "Our Story" is about the firm, not role. Could be placed under "About the role"? Usually "About the role" includes description of role and company. We'll include a paragraph summarizing the firm and the opportunity. - The Opportunity: description of role: building CRM Marketing Manager, etc. Could be part of responsibilities. - What You Will Own: list of duties (Platform Implementation and Configuration, Execute Engagement Journeys & Campaigns, Testing, QA, and Compliance, Reporting & Optimization, Collaboration and Growth). That's responsibilities. - Required: "What You Bring": list of experience requirements. Could be Requirements or Qualifications. We'll separate: Requirements (experience), Qualifications (maybe education? none), Skills (list of skills). The posting includes: 5+ years experience in CRM/lifecycle marketing, proven experience executing journeys in Braze, comfortable partnering with data/engineering, strong understanding of behavioral triggered multi-channel, detail-oriented QA, excellent cross-functional collaboration, experience in legal services etc is a plus. That's skills/requirements. - What We Offer: Base Salary range, bonus, benefits list. So Pay section: Base Salary: $105,700 and $173,400, commensurate with experience. Also mention performance-based bonus. Benefits: list. - Schedule: Not mentioned. No schedule info. So we should not include Schedule section. - Benefits: we have list. - Qualifications: maybe none explicit besides experience. Could combine with Requirements. We need to avoid filler like "commensurate with experience" is okay as it's specific? It's a phrase but it's actual content. It's not placeholder like "N/A". It's okay. We must not include sections with only filler. So include About the role, Responsibilities, Requirements, Skills, Benefits, Pay. Possibly Qualifications if we have any (maybe none). We'll omit Qualifications if no specific content beyond experience. We need to use

for section headings. Use

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

  for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like "Partner with data and engineering teams on the technical setup and configuration of Braze, including segmentation, channel setup, and data integration" etc. We need to ensure we don't repeat job title. The job title is CRM Marketing Manager (implied). Not to repeat as heading. We must remove boilerplate: Equal Opportunity Employer, Disclaimer, AI notice, etc. We must not include application instructions. Now craft HTML. Structure:

  About the role

  Our Story ... The Opportunity ...

  maybe combine. But we need to keep all substantive info. Let's extract paragraphs: Our Story TopDog Law is not your typical law firm. We're a nationally scaling personal injury firm built for impact and growth — owning the client experience end-to-end, from marketing and intake through litigation. We believe that world-class marketing, paired with exceptional legal talent and operations, creates better experiences and outcomes for clients and the business alike. Over the past three years, we've grown 2–3x year over year, setting a new standard on the marketing side of the personal injury space and proving what's possible when strategy, speed, and execution align. Now we're applying that same discipline and innovation to firm operations, case management, and national scale — intentionally building the infrastructure, systems, and teams to grow without sacrificing quality, culture, or accountability. We are a fully remote team that share trust, open communication, and a commitment to doing great work. If you love ownership, thrive in a fast-moving environment, and want to help build something exceptional, you'll feel right at home here. The Opportunity TopDog Law is building a best-in-class client engagement engine to strengthen retention and referral growth across the case lifecycle. We’re seeking a CRM Marketing Manager to execute the buildout of Braze as our core engagement platform, turning our client journey strategy into live, data-driven communications. Reporting to the VP of Client Marketing, this role will orchestrate TopDog Law’s client engagement communications across the case lifecycle. You’ll play an integral role in driving client loyalty and referral growth, using Braze to reduce client turnover, elevate client experience, and move Net Promoter Score at every stage of the case journey. This is a hands-on role for someone who wants to deepen their lifecycle marketing expertise, operate at high volume, and grow into larger ownership over time. We can put that in About the role paragraph(s). Could be two paragraphs. Now Responsibilities: from "What You Will Own" bullet points. We need to convert each bullet into list items. List: - Platform Implementation and Configuration - Partner with data and engineering teams on the technical setup and configuration of Braze, including segmentation, channel setup, and data integration - Define audience segments, event triggers, and data feeds required to support journey builds - Serve as the marketing-side point of contact to define data and integration requirements - Establish naming conventions, canvas structures, and QA processes for scalable journey builds - Execute Engagement Journeys & Campaigns - Build out client journeys per the defined case lifecycle communication strategy - Set up triggered, behavior-based communications (email, SMS, push) tied to case milestones - Test and iterate on journeys based on performance data - Testing, QA, and Compliance - Maintain a consistent QA checklist ensuring messaging, timing, and audience logic are executed accurately - Coordinate with legal/compliance stakeholders to ensure communications meet firm compliance standards - Apply data privacy and messaging regulations (TCPA, CAN-SPAM, CCPA/CPRA) to email and SMS builds - Maintain documentation of live journeys, logic, and compliance sign-offs to support audit readiness - Reporting & Optimization - Monitor journey performance against core lifecycle KPIs — client retention/turnover, NPS by stage, and referral rate — and report on downfunnel law firm metrics - Partner with the decision science team to maintain dashboards or reporting inputs used by the client marketing team - Use data to guide prioritization and execution decisions - Collaboration and Growth - Partner with data and engineering teams to ensure data flows correctly from case management platforms and Salesforce - Implement process improvements and systemization as the CRM program scales - Build toward expanded ownership over time through strong execution We need to decide if we want nested lists or just flat list. The instruction: Use
  • for any list of duties/requirements/benefits. Could be flat list; but we can also have sublists? Probably fine to have nested lists but still
    • . We'll keep flat list items each as a separate duty. Could combine subpoints into one li with semicolons? Better to keep each bullet as li. Thus we will produce a
      with each duty as
      • . Might be long but okay. Now Requirements: from "What You Bring". List: - 5+ years of experience in CRM/lifecycle marketing - Proven experience executing and launching customer/client journeys in Braze or a comparable platform - Comfortable partnering with data and engineering teams on technical implementation - Strong understanding of behavioral, triggered, and multi-channel campaign execution (email, SMS, push) - Detail-oriented with strong QA instincts and comfort managing multiple builds simultaneously - Excellent cross-functional collaboration skills; comfortable working with analytics, operations, product, compliance, and engineering teams - Experience in legal services, financial services, or another regulated/compliance-sensitive industry is a plus We could treat as Requirements. Qualifications: maybe none specific besides experience; we could omit. Skills: maybe we could separate technical skills vs soft skills. But we already have skills in Requirements. Could create Skills section listing: Braze expertise, segmentation, channel setup, data integration, email/SMS/push, TCPA/CAN-SPAM/CCPA, QA, cross-functional collaboration, etc. But that would duplicate. Better to keep Requirements as experience and Skills as specific competencies. However the instruction: Prefer a few substantive sections over many thin ones. So we might combine Requirements and Skills into one section called Requirements (or Qualifications). But we have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to include. We have substantive content for About the role, Responsibilities, Requirements (experience), Skills (maybe we can list specific skills), Benefits, Pay. We could put experience under Requirements, and specific competencies under Skills. Let's extract skills: Braze experience, segmentation, channel setup, data integration, audience segmentation, event triggers, data feeds, naming conventions, canvas structures, QA processes, triggered behavior-based communications (email, SMS, push), testing and iteration, QA checklist, legal/compliance coordination, TCPA, CAN-SPAM, CCPA/CPRA, documentation, monitoring KPIs, partnering with decision science, data-driven prioritization, partnering with data/engineering, process improvements, systemization, ownership mindset. That's a lot; could be considered skills. But we might just have Requirements (experience) and Skills (competencies). However to avoid too many sections, we could combine them into Requirements (including experience and skills). The instruction says prefer few substantive sections over many thin ones. So maybe we just have About the role, Responsibilities, Requirements, Benefits, Pay. That's four sections. That seems good. Thus we will not include Qualifications or Skills separate. Now Benefits: list: Medical, dental, and vision insurance, 401(k) with company match, HSA, life insurance, disability coverage, paid time off, and parental leave. Pay: Base Salary: $105,700 and $173,400, commensurate with experience. Eligible for performance-based bonus. Also note: "Our job postings reflect the compensation range for the specific market and location of each role. Ranges vary by geography based on local market rates and cost of labor." That's substantive; we can include in Pay section. Now we need to ensure we don't include boilerplate like "Equal Opportunity Employer", "Disclaimer", etc. Now produce HTML. We'll start with

        About the role

        then

        paragraphs. We need to preserve all substantive info; we can split into two paragraphs: first about company story, second about opportunity. Let's craft. Paragraph 1: Our Story TopDog Law is not your typical law firm. ... fully remote team ... If you love ownership, thrive in a fast-moving environment, and want to help build something exceptional, you'll feel right at home here. Paragraph 2: The Opportunity TopDog Law is building a best-in-class client engagement engine ... grow into larger ownership over time. Now Responsibilities:

        Responsibilities

        then
        with each duty as
        • . We'll need to keep the sub-bullets as part of each li maybe using semicolons. We'll produce each main duty as li with its subpoints separated by ; or line breaks? Since we cannot use
          inside li? We can but it's okay. We'll just use semicolons. Let's list: - Partner with data and engineering teams on the technical setup and configuration of Braze, including segmentation, channel setup, and data integration; define audience segments, event triggers, and data feeds required to support journey builds; serve as the marketing-side point of contact to define data and integration requirements; establish naming conventions, canvas structures, and QA processes for scalable journey builds. - Build out client journeys per the defined case lifecycle communication strategy;