Senior Retention Specialist, CRM

We need to output HTML fragment with sections: About the role (but note the page already shows job title, we shouldn't repeat job title as heading). The posting includes "About Darkroom" (company description) and "About The Role". Also "What It's Like to Work at Darkroom" includes benefits, compensation, etc. We need to include sections only when there is real specific content. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to parse content and map to these sections. We have: - About Darkroom (company overview) – maybe not needed as a section; but we could put under "About the role"? Actually "About the role" is separate. The company description could be omitted? 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 a company overview section, but we only have allowed headings list. Could we add a heading like "About Darkroom"? Not in allowed list. Probably we should not create extra headings beyond those listed. So we need to fit content into allowed sections. We have responsibilities: many bullet points under "A day in the life" and earlier description. We'll put those under

Responsibilities

as

• . Requirements/Qualifications/Skills: The posting lists qualifications: "3–5+ years of hands-on lifecycle, CRM, or email marketing execution..." etc. Also skills: knowledge of ESP, segmentation, deliverability, HTML/CSS, templating languages, data flows, troubleshooting, testing, communication. We can split into Requirements (experience) and Skills (technical). Qualifications maybe similar to requirements. We'll decide: Use Requirements for experience and qualifications; Skills for technical abilities. Benefits: The posting includes "Unlimited PTO + US holidays", "Remote-First Culture", "Health & Wellness", "Finances, growth, and retirement: 401(k) with match and profit-sharing", "Parental Leave", "Growth". Also compensation: "Compensation: The base salary range for this role is $60,000-$80,000 per year." That's Pay. Schedule: Not mentioned explicitly; maybe remote-first culture implies schedule? No explicit schedule. So we should not create Schedule section if no specific content. We must not include sections with filler like "commensurate with experience". We have actual content. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format as lists. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At end there is "Equal Opportunity Statement". That's boilerplate; we should remove it. Also "About Darkroom" maybe not needed as heading but we could incorporate into a short paragraph under maybe "About the role"? But we have no heading for company overview. Could we put it under a

  before sections? The instruction: Output ONLY the HTML fragment — no /. It didn't forbid a leading

  about company. So we can include a

  with the About Darkroom content before sections. That seems okay. We must not repeat job title as heading. So we won't. We'll produce:

  About Darkroom ...

  Then

  About the role

  maybe? Actually "About The Role" is a heading in posting. But allowed headings include "About the role". So we can use that. Then responsibilities

  Responsibilities

  . Then requirements

  Requirements

  . Then skills

  Skills

  . Then benefits

  Benefits

  . Then pay

  Pay

  . We must not include schedule. We need to ensure we don't create empty sections. Let's extract content. About Darkroom paragraph: "About Darkroom Darkroom is the leading next-generation growth marketing firm engineering the brands of tomorrow. Founded in 2017, we set out to redefine what a modern agency could be, by replacing the inertia of legacy advertising behemoths with a model built for speed, intelligence, and measurable impact. At our core, Darkroom is a human services company powered by Shadow, a universal AI commerce layer that integrates executive-level strategy with proprietary agentic technology. This fusion enables our teams to deliver outsized returns by enhancing creative output, operational efficiency, and revenue generation across every stage of the customer journey. Our track record speaks for itself: billions in attributable revenue driven across e-commerce marketplaces, media networks, DTC ecosystems, and social commerce platforms. Every engagement feeds into our proprietary data infrastructure, enabling a continuous feedback loop that accelerates growth, improves margins, and compounds results across our client portfolio. What began as a boutique design studio has evolved into one of the fastest-growing private companies in America (Inc. 5000) and among the most effective performance media agencies of the 2020s (Varos). Our founders were recognized by Forbes 30 Under 30 for advancing the intersection of technology, marketing, and advertising, cementing Darkroom’s role as a defining player in the future of media innovation." We'll put that as a

  . About the role: The paragraph after "About The Role": "We are looking for a deeply technical Senior Retention Specialist to own the CRM build for a high-growth consumer technology client. You will architect and implement the flows and automations that carry the program, own the segmentation logic behind them, and hold the channel KPIs that determine whether any of it lands in the inbox. You are standing this program up from the ground, not inheriting it. The list starts near 20,000 and scales rapidly behind a significant acquisition investment — which puts real pressure on deliverability, list hygiene, and data hygiene from day one. Volume ramps to 40–60 emails a month, and increasingly granular segmentation is what generates that output. Automation is the core of the program: lead capture, welcome series, and the first-conversion funnel first, then subscription activation, loyalty, repeat purchase, and win-back. You will work in an enterprise-grade platform — Braze, Salesforce Marketing Cloud, Iterable, Customer.io, or comparable. You are the person who knows the platform better than anyone else on the team. When something does not fire, does not render, or does not deliver, you find out why. You should apply if this sounds like you You are hands-on in the ESP every day and you like it there. You enjoy building a journey with real conditional logic, and you get genuine satisfaction from tracking down why one segment stopped converting." We can keep that as prose under About the role. Responsibilities: from "A day in the life" bullet-like sentences: "Build and QA the flows, automations, and campaigns that run your client's program — from lead capture and welcome through activation, loyalty, repeat purchase, and win-back. Implement the segmentation and audience logic behind the calendar, and build the dynamic content that makes personalization work at volume. Own the technical setup and health of the client's ESP instance: integrations, data feeds, event tracking, templates, and modules. Monitor and own channel performance and deliverability, escalating and fixing issues before they affect the program. Troubleshoot anything that misfires — a flow that does not trigger, a segment that under-populates, a template that breaks in Outlook — and document the fix. QA every build end to end before launch: logic, rendering, links, personalization, suppression. Design and run the testing roadmap with your Associate Director, and report results honestly. Partner with the Copy & Content Specialist to get copy and creative into the build accurately and on schedule. Build and maintain the reporting your Associate Director needs for client KPI reviews." We'll put each as

• . Requirements: The bullet list after "You should apply if this sounds like you" actually includes qualifications: "3–5+ years of hands-on lifecycle, CRM, or email marketing execution, with deep expertise in at least one enterprise-grade ESP — Braze, Salesforce Marketing Cloud, Iterable, Customer.io, or comparable. You have built complex, event-triggered journeys from scratch: multi-branch logic, wait steps, conditional splits, holdouts, and cross-channel orchestration across email, SMS, push, and in-app. You are fluent in advanced segmentation — behavioral and product-event based, computed attributes, dynamic and personalized content — and you have scaled a program where segmentation drove a real increase in send volume. You have built the funnel that matters here: lead capture forms and opt-in logic, welcome series, first-conversion sequences, and subscription activation journeys. You have implemented loyalty, rewards, and win-back programs, and you treat driving repeat purchase and long-term value as a core outcome rather than a nice-to-have. You own deliverability as a discipline: domain warming and authentication (SPF, DKIM, DMARC, BIMI), sending reputation, list hygiene, sunset policies, and what to do when a list grows very fast. You own the channel KPIs — open, click, click-to-open, conversion, deliverability, bounce, spam complaints, unsubscribe — and you can diagnose a drop in any of them. You are comfortable with HTML and CSS for email, and you know how to build templates and modules that render correctly across clients. Liquid, Handlebars, AMPscript, or a similar templating language is a strong plus. You understand data flows into the ESP: API-based events, webhooks, ETL or CDP integrations, and product event streams. You can hold a technical conversation with a client's engineering team. You are a systematic troubleshooter — you isolate variables, you check the data before the theory, and you document what you find. You design and execute proper tests: A/B and multivariate, with honest reads on significance. Excellent written communication and the ability to explain a technical problem to a non-technical audience clearly and without condescension." We can split: Requirements: experience (years, expertise). Skills: technical abilities (ESP, segmentation, deliverability, HTML/CSS, templating, data flows, troubleshooting, testing, communication). But many overlap. We'll put experience bullets under Requirements, and technical skill bullets under Skills. Let's define Requirements bullets: - 3–5+ years of hands-on lifecycle, CRM, or email marketing execution - Deep expertise in at least one enterprise-grade ESP — Braze, Salesforce Marketing Cloud, Iterable, Customer.io, or comparable Maybe also "You have built complex, event-triggered journeys from scratch..." could be skill. But we can keep under Requirements as experience. Skills bullets: - Built complex, event-triggered journeys from scratch: multi-branch logic, wait steps, conditional splits, holdouts, cross-channel orchestration across email, SMS, push, in-app - Fluent in advanced segmentation — behavioral and product-event based, computed attributes, dynamic and personalized content; scaled program where segmentation drove real increase in send volume - Built funnel: lead capture forms and opt-in logic, welcome series, first-conversion sequences, subscription activation journeys - Implemented loyalty, rewards, and win-back programs; treat driving repeat purchase and long-term value as core outcome - Own deliverability: domain warming and authentication (SPF, DKIM, DMARC, BIMI), sending reputation, list hygiene, sunset policies, handling fast list growth - Own channel KPIs — open, click, click-to-open, conversion, deliverability, bounce, spam complaints, unsubscribe; diagnose drops - Comfortable with HTML and CSS for email; build templates/modules rendering across clients - Knowledge of Liquid, Handlebars, AMPscript, or similar templating language (strong plus) - Understand data flows into ESP: API-based events, webhooks, ETL/CDP integrations, product event streams - Able to hold technical conversation with client engineering team - Systematic troubleshooter: isolate variables,