SMS/TCPA Compliance Lead

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: About the role (the paragraph after "About The Role"). Responsibilities (the "What You'll Do" bullet list). Qualifications (the "Qualifications Required" and "Preferred" sections). Skills maybe implied but not explicit separate. Benefits, Pay, Schedule not mentioned. So we include About the role, Responsibilities, Qualifications. Possibly also Skills? Not explicit. We'll not create empty sections. We need to use

for section headings. Use

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

  for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate etc. The posting includes some fluff like "Millionaire Publishing is our research and education arm..." that's part of About Stockstotradecom, Inc. That is about the company, not role. Should we include? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The company description is substantive but not part of role? The role description includes "About Stockstotradecom, Inc" at top. It might be considered part of the posting. We should keep it but maybe as a paragraph before sections. Not a heading. So we can include a

  with that company description. We need to remove cookie/navigation/legal/EEO etc. Not present. We need to not repeat job title as heading. Not include Job ID. We need to format lists. Let's extract content. Company description: "About Stockstotradecom, Inc StocksToTrade is an all-in-one trading platform combining scanning, charting, and real-time data with live trader education. Millionaire Publishing is our research and education arm, publishing trader-written ideas and strategies with no fees taken from the companies we cover. Together, our webinars and lifecycle marketing reach a high-volume, highly engaged audience — which is where this role comes in." We can keep as a paragraph. About The Role: "You’ll sit on the Broadcast team alongside the Broadcast Manager, reporting to the Director of Day-to-Day Marketing Operations. Email deliverability is handled separately, including a dedicated deliverability partner — you may collaborate on shared suppressions and cross-channel hygiene, but this role is SMS/TCPA-first. We’re not looking for a dual email-and-SMS deliverability unicorn. You’ll be a primary point of contact with SMS platform vendors like Twilio, Iterable SMS, and Lime, managing escalations and configurations, and partnering with Legal/Compliance, Broadcast Ops, and RevOps to keep guardrails auditable and execution consistent." That's prose. What You'll Do (Responsibilities) list: - TCPA & SMS compliance — own consent management, revocation and any-reasonable-method STOP handling, quiet hours, frequency controls, and auditable SMS workflows with Legal/Compliance. - SMS list health & suppressions — maintain SMS suppressions across brands and projects, including dedicated marketing suppress floors, opt-in quality, and STOP/START lifecycle hygiene so blasts never hit the wrong person or the wrong sender. - Short codes / 10DLC / throughput — own short-code and 10DLC health (primary vs. VIP codes), throughput and MPS constraints, wrong-sender mapping risks, and vendor escalations when volume or registration blocks sends. - Systems & tools — system ownership for SMS platform configuration (Twilio, Iterable SMS, Lime as applicable): access, message types and senders, change documentation, and technical escalations. - Broadcast SOPs — write and maintain SMS/TCPA SOPs (consent, suppress packs, cadence, midweek inventory swaps, QA checklists) that Broadcast and Inventory can actually follow. - Vendor liaison — serve as the primary SMS vendor contact for support, compliance alignment, and new feature or policy rollouts. - Cross-functional support — give structured guidance to the Broadcast Manager and day-to-day team so live webinar, VIP, and lifecycle SMS sends match approved standards, with light coordination with email deliverability on shared suppressions only. - Monitoring & risk — define SMS compliance and deliverability KPIs (delivery, errors, STOP rates, complaint and risk signals), and spot and fix risks before they become incidents. We need to put each as

• . Qualifications Required: "Required A process-driven operator who knows both the legal and technical sides of SMS governance. Deep experience in SMS/TCPA compliance — consent, opt-outs, quiet hours, carrier and 10DLC realities. Email deliverability experience is a nice-to-have, not the core hire bar. Hands-on with high-volume SMS stacks such as Twilio, Iterable SMS, and/or Lime or similar. A strong SOP writer, comfortable influencing Broadcast and Legal without needing a big team underneath you. Technical enough to own configuration decisions and work with engineering and RevOps when APIs or mappings break." Preferred: "Preferred 3–5+ years in SMS compliance, messaging ops, or marketing ops with a clear SMS/TCPA focus. Direct experience with Twilio and an ESP SMS layer such as Iterable. Strong working knowledge of U.S. TCPA and related state rules; CAN-SPAM/email familiarity helpful for cross-channel overlap only. Proven ability to write and maintain operational documentation and compliance-focused SOPs." We can combine Required and Preferred into a list? The instruction: Use
  • for any list of duties/requirements/benefits. So we can make a list for qualifications. Could separate Required and Preferred as subheadings? But we only have heading Qualifications. Under that we can have paragraphs for Required and Preferred, or we can make a list. Better to keep prose for Required and Preferred as paragraphs, but we could also bullet each requirement. However the instruction says use
    • for any list of duties/requirements/benefits. The qualifications are a list of items; we could bullet them. But we must preserve all substantive information; bulletizing is okay as long as we don't lose detail. Let's bullet each distinct requirement. Let's extract items: Required: - Process-driven operator who knows both the legal and technical sides of SMS governance. - Deep experience in SMS/TCPA compliance — consent, opt-outs, quiet hours, carrier and 10DLC realities. - Email deliverability experience is a nice-to-have, not the core hire bar. - Hands-on with high-volume SMS stacks such as Twilio, Iterable SMS, and/or Lime or similar. - Strong SOP writer, comfortable influencing Broadcast and Legal without needing a big team underneath you. - Technical enough to own configuration decisions and work with engineering and RevOps when APIs or mappings break. Preferred: - 3–5+ years in SMS compliance, messaging ops, or marketing ops with a clear SMS/TCPA focus. - Direct experience with Twilio and an ESP SMS layer such as Iterable. - Strong working knowledge of U.S. TCPA and related state rules; CAN-SPAM/email familiarity helpful for cross-channel overlap only. - Proven ability to write and maintain operational documentation and compliance-focused SOPs. We could have two sublists: Required and Preferred, but we only have Qualifications heading. Could embed headings inside? Not allowed to create extra headings besides the specified ones? The instruction only says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but better to stick to those. We could include paragraphs labeling "Required:" and "Preferred:" inside the Qualifications section. Thus Qualifications section will have

      Required:

      then

      list, then

      Preferred:

      then
      list. Now we need to output only HTML fragment. Let's craft:

      About Stockstotradecom, Inc StocksToTrade is an all-in-one trading platform combining scanning, charting, and real-time data with live trader education. Millionaire Publishing is our research and education arm, publishing trader-written ideas and strategies with no fees taken from the companies we cover. Together, our webinars and lifecycle marketing reach a high-volume, highly engaged audience — which is where this role comes in.

      About the role

      You’ll sit on the Broadcast team alongside the Broadcast Manager, reporting to the Director of Day-to-Day Marketing Operations. Email deliverability is handled separately, including a dedicated deliverability partner — you may collaborate on shared suppressions and cross-channel hygiene, but this role is SMS/TCPA-first. We’re not looking for a dual email-and-SMS deliverability unicorn. You’ll be a primary point of contact with SMS platform vendors like Twilio, Iterable SMS, and Lime, managing escalations and configurations, and partnering with Legal/Compliance, Broadcast Ops, and RevOps to keep guardrails auditable and execution consistent.

      Responsibilities

      • TCPA & SMS compliance — own consent management, revocation and any-reasonable-method STOP handling, quiet hours, frequency controls, and auditable SMS workflows with Legal/Compliance.
      • SMS list health & suppressions — maintain SMS suppressions across brands and projects, including dedicated marketing suppress floors, opt-in quality, and STOP/START lifecycle hygiene so blasts never hit the wrong person or the wrong sender.
      • Short codes / 10DLC / throughput — own short-code and 10DLC health (primary vs. VIP codes), throughput and MPS constraints, wrong-sender mapping risks, and vendor escalations when volume or registration blocks sends.
      • Systems & tools — system ownership for SMS platform configuration (Twilio, Iterable SMS, Lime as applicable): access, message types and senders, change documentation, and technical escalations.
      • Broadcast SOPs — write and maintain SMS/TCPA SOPs (consent, suppress packs, cadence, midweek inventory swaps, QA checklists) that Broadcast and Inventory can actually follow.
      • Vendor liaison — serve as the primary SMS vendor contact for support, compliance alignment, and new feature or policy rollouts.
      • Cross-functional support — give structured guidance to the Broadcast Manager and day-to-day team so live webinar, VIP, and lifecycle SMS sends match approved standards, with light coordination with email deliverability on shared suppressions only.
      • Monitoring & risk — define SMS compliance and deliverability KPIs (delivery, errors, STOP rates, complaint and risk signals), and spot and fix risks before they become incidents.

      Qualifications

      Required:

      • Process-driven operator who knows both the legal and technical sides of SMS governance.
      • Deep experience in SMS/TCPA compliance — consent, opt-outs, quiet hours, carrier and 10DLC realities.
      • Email deliverability experience is a nice-to-have, not the core hire bar.
      • Hands-on with high-volume SMS stacks such as Twilio, Iterable SMS, and/or Lime or similar.
      • Strong SOP writer, comfortable influencing Broadcast and Legal without needing a big team underneath you.
      • Technical enough to own configuration decisions and work with engineering and RevOps when APIs or mappings break.

      Preferred:

      • 3–5+ years in SMS compliance, messaging ops, or marketing ops with a clear SMS/TCPA focus.
      • Direct experience with Twilio and an ESP SMS layer such as Iterable.
      • Strong working knowledge of U.S. TCPA and related state rules; CAN-SPAM/email familiarity helpful for cross-channel overlap only.
      • Proven ability to write and maintain operational documentation and compliance-focused SOPs.
      No Benefits, Pay, Schedule sections. Check that we didn't include any boilerplate. Good.