Marketing Specialist - CRM
About the role
thenwith job purpose and maybe who we are? But we must not repeat job title as heading. It's okay. Responsibilities: list from Key Responsibilities. Requirements: required qualifications. Qualifications: maybe preferred? Could treat as Qualifications. Skills: maybe list specific skills like ESP/CRM proficiency, SQL, deliverability, etc. But those are already in requirements. Might be redundant. Better to not create thin sections. The instruction: Prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one section? But headings are predetermined; we can omit sections if no specific content. We could include Requirements (required) and Qualifications (preferred) as separate if they have content. That's okay. Skills: maybe we could extract skills from responsibilities and requirements: e.g., "ESP/CRM proficiency (Zeta, Salesforce Marketing Cloud, Hubspot)", "AMPscript/Liquid", "SQL for marketing", "Deliverability & compliance (SPF/DKIM/DMARC; CAN-SPAM/GDPR/CCPA; TCPA/10DLC)", "Project management", "Cross-functional collaboration", "Omni-channel 1:1 programs", "Dynamic content", "AI-assisted workflows", "Front-end fluency", "API/webhook literacy". That is substantive. Could create Skills section. Benefits: none. Pay: none. Schedule: we have in-office Monday-Friday in Plano, TX. That's schedule/location. Could put under Schedule. Thus output sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Schedule. We must not include empty sections. Now format: each heading
Heading
then content: for lists use- ... etc. For prose use
. We need to preserve all substantive information, not invent or summarize away detail. Must not omit details. Must include all details from posting. Let's extract details. Who We Are: Upbound Group, Inc. (NASDAQ: UPBD) is a technology and data-driven leader in accessible and inclusive financial solutions that address the evolving needs and aspirations of underserved customers. The Company’s customer-facing operating units include industry-leading brands such as Acima, Brigit, and Rent-A-Center that facilitate consumer transactions across a wide range of store-based and digital channels, including over 2,300 company branded retail units across the United States, Mexico, and Puerto Rico. Job Purpose: The CRM Platform Marketing Specialist will architect and launch retention programs that move customers to loyal advocates. This role blends CRM platform execution with data fluency to drive measurable lifts in engagement, conversion, and retention across channels. Key Responsibilities: list bullet points: - Orchestrate omni‑channel journeys, promotional and transactional campaigns across email, SMS, push, direct mail, and in‑app to deliver timely, personalized and dynamic messages powered by our CDP (Zeta Marketing Platform). - Be an expert in Rent-A-Center first‑party data using SQL‑driven, and rule-based logic (e.g. within Zeta) to segment and target behaviors and lifecycle stages; run A/B and multivariate tests to continuously optimize performance. - Personalize at scale using templating/scripting (e.g., AMPscript, Liquid) and real‑time data; set up, QA, and monitor automations and triggered campaigns. - Ensure campaigns deploy accurately and on time and communicate and troubleshoot with urgency when needed to assist in root cause analysis - Safeguard deliverability & compliance: manage list hygiene; follow SPF/DKIM/DMARC best practices; ensure CAN‑SPAM, GDPR/CCPA, and SMS compliance. - Collaborate cross‑functionally with Product pods, Data Services, Personalization, Legal, and CRM teammates to translate business asks into data requirements and flawless execution. - Gain knowledge on lifecycle KPIs, ensure campaigns are configured to translate into actionable reporting cuts with data analytics, including ad hoc or long-term holdbacks. - Continuously improve processes, tooling, and QA to increase speed, quality, and reliability of every launch. Job Requirements Required: - 3–5+ years hands‑on lifecycle/CRM/email experience in a fast‑paced environment, with strong project management and cross‑functional collaboration skills. - ESP/CRM proficiency (e.g., Zeta Marketing Platform, Salesforce Marketing Cloud, Hubspot) and dynamic content/personalization (AMPscript/Liquid). - SQL for marketing: audience creation, complex segmentation, and QA of lists/counts. - Deliverability & compliance know‑how (SPF/DKIM/DMARC; CAN‑SPAM/GDPR/CCPA; TCPA/10DLC for SMS). - Meticulous attention to detail and brand stewardship from build to deployment. - This position is in-office (Monday through Friday) in Plano, TX Preferred: - Experience orchestrating omni‑channel 1:1 programs and dynamic content across multi‑brand portfolios. - Working knowledge of AI‑assisted workflows for content, QA, or decisioning (with human‑in‑the‑loop controls). - Basic front‑end fluency beyond email (landing pages, tracking/UTMs) and light API/webhook literacy. Sponsorship: Applicants must be authorized to work for ANY employer in the U.S. We are unable to sponsor or take over sponsorship of an employment visa at this time. EEO statement: Upbound Group is an equal opportunity employer. We celebrate diversity and are committed to creating an inclusive environment for all employees. We must remove boilerplate: sponsorship, EEO, etc. Also remove navigation/legal etc. So we drop sponsorship and EEO lines. Now we need to map to sections. About the role: combine Who We Are and Job Purpose? Could be two paragraphs. Responsibilities: list as
- .
Requirements: required bullet list.
Qualifications: preferred bullet list.
Skills: maybe we could extract a list of skills from responsibilities and requirements, but that would duplicate content. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we create Skills section, we must not omit any info from other sections; we could still keep them in Requirements/Qualifications. Skills could be a summary but that would be summarizing. Better to avoid Skills section to avoid duplication or summarizing. However the instruction says we can include sections only when posting has real, specific content for it. It doesn't forbid overlapping content, but we should avoid summarizing away detail. If we create Skills section, we need to include the specific skills as listed, not summarizing. Could list them exactly as they appear in responsibilities/requirements. That would be duplication but not summarizing. However duplication may be okay? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is not summarizing away detail, it's repeating detail. Might be acceptable but could be considered redundant. The instruction also says "Prefer a few substantive sections over many thin ones." So maybe better to not create Skills section if it would be thin or duplicate. We can incorporate skills into Requirements and Qualifications.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Schedule.
Schedule: we have "This position is in-office (Monday through Friday) in Plano, TX". That's specific.
We must not include Benefits, Pay.
Now format.
We need to ensure we don't include any markdown fences. Just raw HTML.
Let's craft.
- Orchestrate omni‑channel journeys, promotional and transactional campaigns across email, SMS, push, direct mail, and in‑app to deliver timely, personalized and dynamic messages powered by our CDP (Zeta Marketing Platform).
- Be an expert in Rent-A-Center first‑party data using SQL‑driven, and rule-based logic (e.g. within Zeta) to segment and target behaviors and lifecycle stages; run A/B and multivariate tests to continuously optimize performance.
- Personalize at scale using templating/scripting (e.g., AMPscript, Liquid) and real‑time data; set up, QA, and monitor automations and triggered campaigns.
- Ensure campaigns deploy accurately and on time and communicate and troubleshoot with urgency when needed to assist in root cause analysis.
- Safeguard deliverability & compliance: manage list hygiene; follow SPF/DKIM/DMARC best practices; ensure CAN‑SPAM, GDPR/CCPA, and SMS compliance.
- Collaborate cross‑functionally with Product pods, Data Services, Personalization, Legal, and CRM teammates to translate business asks into data requirements and flawless execution.
- Gain knowledge on lifecycle KPIs, ensure campaigns are configured to translate into actionable reporting cuts with data analytics, including ad hoc or long-term holdbacks.
- Continuously improve processes, tooling, and QA to increase speed, quality, and reliability of every launch.
- 3–5+ years hands‑on lifecycle/CRM/email experience in a fast‑paced environment, with strong project management and cross‑functional collaboration skills.
- ESP/CRM proficiency (e.g., Zeta Marketing Platform, Salesforce Marketing Cloud, Hubspot) and dynamic content/personalization (AMPscript/Liquid).
- SQL for marketing: audience creation, complex segmentation, and QA of lists/counts.
- Deliverability & compliance know‑how (SPF/DKIM/DMARC; CAN‑SPAM/GDPR/CCPA; TCPA/10DLC for SMS).
- Meticulous attention to detail and brand stewardship from build to deployment.
- This position is in-office (Monday through Friday) in Plano, TX.
- Experience orchestrating omni‑channel 1:1 programs
About the role
Upbound Group, Inc. (NASDAQ: UPBD) is a technology and data-driven leader in accessible and inclusive financial solutions that address the evolving needs and aspirations of underserved customers. The Company’s customer-facing operating units include industry-leading brands such as Acima, Brigit, and Rent-A-Center that facilitate consumer transactions across a wide range of store-based and digital channels, including over 2,300 company branded retail units across the United States, Mexico, and Puerto Rico.
The CRM Platform Marketing Specialist will architect and launch retention programs that move customers to loyal advocates. This role blends CRM platform execution with data fluency to drive measurable lifts in engagement, conversion, and retention across channels.
Responsibilities
Requirements
Qualifications