Manager, Email & SMS

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. From posting: - About The Role: description of role, mission, etc. We'll put under

About the role

with paragraphs. - Responsibilities: The "Essential Job Duties And Responsibilities" section with subheadings: Email Programming & Automation, Channel Ownership, Platform, Deliverability & Compliance, Analytics, Testing & Reporting, Cross‑Functional Collaboration. We'll need to list duties as

• items. Could group under responsibilities. - Requirements: "Job Specifications REQUIRED EDUCATION AND EXPERIENCE:" includes bullet list: Bachelor’s degree, 3-5 years experience, hands‑on experience with enterprise-level ESPs and SMS platforms, demonstrated experience with segmentation, automations, testing, performance optimization. Also "Preferred Education And Experience" maybe separate but could be part of qualifications/skills. - Qualifications: maybe combine required and preferred? The instruction: Use headings for sections like Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what content goes where. We have "Competencies" list: Strong ownership mindset..., etc. That could be Skills. We have "Benefits": The "About The Tanger Perks" bullet list: Competitive salary, Generous Suite of Medical, Dental, and Vision Benefits, 401(k) match, Paid PTO and Holidays, Paid Volunteer Hours, Team Member Paid Leave Programs, Tuition Reimbursement, Wellness Incentives, Group Life and Disability Insurance, Voluntary Benefits, Team Member Discounts, And more… We have Pay: "Hiring Range: $78,000 - $110,000 per year". Also mention base salary range. So we can include Pay section. Schedule: Not mentioned. Travel up to 5% travel. That's not schedule. No schedule info. So we should not create Schedule section. We must not include boilerplate like EEO, accessibility, etc. We must not repeat job title as heading. We must not include Job ID etc. We must preserve all substantive information. We need to output only HTML fragment. Let's structure:

  About the role

  ... (combining About The Role paragraph plus maybe the first paragraph about mission? Actually About The Role includes: "In our continued mission to create shopping destinations that entertain, inspire, and bring communities together, Tanger is seeking a Manager, Email & SMS This role offers the opportunity to work both independently and collaboratively, supported by a flexible, Teams-driven workplace designed to empower connection, innovation, and impact across geographies." We'll put that. Also maybe include "About The Company" is not needed as heading? The instruction says use headings for section headings like About the role, Responsibilities, etc. About the company is not listed; we could omit or maybe include as part of About the role? Probably we should not include About the company as a separate heading because not in list. But we could incorporate some of that into About the role? The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., not exclusive. But we should only include sections when posting has real specific content. About the company is present but not in the list; we could still include but maybe better to omit because not requested. However we must preserve ALL substantive information. If we omit About the company, we lose that info. But maybe it's considered boilerplate? It's mission statement etc. Might be considered substantive. 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 we should follow the pattern. Safer to include About the company as a heading? But they didn't list it. However they said "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies those are examples; we could also use other headings if needed. But they also said "Prefer a few substantive sections over many thin ones." So maybe we can combine About the company into About the role or omit. I'd include About the company as a paragraph under About the role? Might be okay. But we need to preserve all substantive information. The About the company paragraph is mission, vision, values. Could be included as a preamble before About the role. Since we cannot add extra headings not in list? Not prohibited. I'll include a

  About the company

  maybe? But they didn't list it; risk of being considered not following instruction. However they said "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exhaustive. So we can add About the company. But to be safe, we could incorporate About the company into About the role section as a paragraph. That preserves info without extra heading. Let's do that. Now Responsibilities: We'll create

  Responsibilities

  then a
  with each duty as
  • . Might need to break down subpoints. Could keep each bullet as a duty. We have many duties; we can list them as separate
  • items. Let's extract: - Own the programming and configuration of email campaigns and automations within the Email Service Provider (ESP) and SMS platform, including: - Triggered and event‑based programs - Multi‑step customer journeys and workflows - Behavioral, transactional, and lifecycle automations - Build and maintain dynamic email content using: - HTML and ESP‑native templating tools - Conditional logic based on customer attributes, behaviors, and preferences - Personalization tokens, dynamic content blocks, and modular templates - Develop and manage audience segmentation logic, including: - Behavioral, transactional, and engagement‑based segments - Suppression logic and frequency controls - Testing segments to validate accuracy prior to deployment - Partner with Marketing, Loyalty, and Technology teams to: - Translate business and customer requirements into executable email logic - Implement data integrations, field mappings, and data hygiene best practices - Troubleshoot data, rendering, or automation issues impacting campaigns - Own automation QA and monitoring, ensuring: - Journeys fire correctly based on triggers and conditions - Content, links, and personalization render accurately - Ongoing validation of long‑running programs - Document email programs, templates, and logic to support: - Program scalability - Knowledge transfer and operational continuity - Faster onboarding of future team members or vendors - Channel Ownership: Own the email and SMS channels, including execution, lifecycle development, testing, and optimization. - Develop and maintain email and SMS lifecycles (onboarding, engagement, retention, and reactivation) aligned to customer segments and business priorities. - Define and manage send cadence, messaging frameworks, and channel best practices. - Provide strategic recommendations based on performance trends, testing results, and customer behavior analysis. - Platform, Deliverability & Compliance: Serve as the primary owner of Email Service Provider (ESP) and SMS platform operations, including configuration, troubleshooting, and vendor coordination. - Manage email and SMS deliverability, sender reputation, opt‑in/opt‑out flows, short codes, and domain configurations. - Ensure all programs comply with relevant regulations (CAN‑SPAM, TCPA, GDPR/CCPA, consent management standards). - Lead operational planning for ESP enhancements, migrations, or new feature adoption as required. - Analytics, Testing & Reporting: Establish and execute testing methodologies (A/B, multivariate, incrementality) to improve performance. - Analyze campaign and lifecycle results across key metrics (engagement, conversion, revenue lift). - Produce weekly, monthly, and quarterly performance reporting with clear insights and recommendations. - Partner with analytics and data teams to improve measurement, attribution, and actionable reporting. - Cross‑Functional Collaboration: Act as the voice of the Email and SMS channels in campaign planning, initiative reviews, and cross‑departmental discussions. - Partner closely with Marketing, Loyalty, Media, Technology, Legal, and Customer Care teams. - Maintain project plans, timelines, and dependencies using approved project management tools. - Create and maintain program documentation and playbooks to support scalability and continuity. We could flatten these into a list of responsibilities, each as
  • with maybe sub-bullets? But spec says use
    • for any list of duties/requirements/benefits. It doesn't forbid nested lists? Probably okay but safer to keep flat list. We could combine each bullet as a duty. Simplify: each top-level bullet as a duty. Thus:
    • Own the programming and configuration of email campaigns and automations within the Email Service Provider (ESP) and SMS platform, including triggered and event‑based programs, multi‑step customer journeys and workflows, behavioral, transactional, and lifecycle automations; build and maintain dynamic email content using HTML and ESP‑native templating tools, conditional logic, personalization tokens, dynamic content blocks, and modular templates; develop and manage audience segmentation logic including behavioral, transactional, and engagement‑based segments, suppression logic and frequency controls, testing segments prior to deployment; partner with Marketing, Loyalty, and Technology teams to translate business and customer requirements into executable email logic, implement data integrations, field mappings, and data hygiene best practices, troubleshoot data, rendering, or automation issues impacting campaigns; own automation QA and monitoring ensuring journeys fire correctly, content/links/personalization render accurately, ongoing validation of long‑running programs; document email programs, templates, and logic to support program scalability, knowledge transfer, operational continuity, and faster onboarding.
    • Own the email and SMS channels, including execution, lifecycle development, testing, and optimization; develop and maintain email and SMS lifecycles (onboarding, engagement, retention, and reactivation) aligned to customer segments and business priorities; define and manage send cadence, messaging frameworks, and channel best practices; provide strategic recommendations based on performance trends, testing results, and customer behavior analysis.
    • Serve as the primary owner of Email Service Provider (ESP) and SMS platform operations, including configuration, troubleshooting, and vendor coordination; manage email and SMS deliverability, sender reputation, opt‑in/opt‑out flows, short codes, and domain configurations; ensure all programs comply with relevant regulations (CAN‑SPAM, TCPA, GDPR/CCPA, consent management standards); lead operational planning for ESP enhancements, migrations, or new feature adoption as required.
    • Establish and execute testing methodologies (A/B, multivariate, incrementality) to improve performance; analyze campaign and lifecycle results across key metrics (engagement, conversion, revenue lift); produce weekly, monthly, and quarterly performance reporting with clear insights and recommendations; partner with analytics and data teams to improve measurement, attribution, and actionable reporting.
    • Act as the voice of the Email and SMS channels in campaign planning, initiative reviews, and cross‑departmental discussions; partner closely with Marketing, Loyalty, Media, Technology, Legal, and Customer Care teams; maintain project plans, timelines, and dependencies using approved project management tools; create and maintain program documentation and playbooks to support scalability and continuity.
    That covers responsibilities. Now Requirements: We'll create

    Requirements

    with
    • items: - Bachelor’s degree in Marketing, Communications, Business, or related field - 3-5 years of related experience in email and/or SMS marketing, lifecycle marketing, or digital channel management - Hands‑on experience with enterprise‑level ESP