Senior CRM Specialist - Adobe Experience Cloud
Level Agency · United States · 3 days ago
RemoteRemoteOTHR$100k/yrFull-time
The user wants me to reformat a job posting into clean, well-structured semantic HTML. The posting is bilingual (English and French), but I should focus on the English version since the user provided the English text first and the French version appears to be a translation. The instructions say to output only the HTML fragment, no markdown code fences, no html/body tags.
I need to identify sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule, etc. Use h3 for section headings, ul/li for lists, p for prose. Do not repeat job title as heading. Do not put Job ID/requisition numbers as headings. Fold minor metadata into short p or drop. Preserve all substantive information. Remove boilerplate (cookie/navigation/legal/EEO/scam-warning). Remove duplicated lines and application instructions. Include section only when real specific content exists. No filler/placeholder text. No Pay/Schedule/Benefits sections unless posting actually states them.
Let's parse the English version:
- Title: "Senior CRM Specialist" (but we shouldn't repeat as heading)
- Metadata: "Remote - U.S. & Canada Only | Full-Time Compensation: $100K USD (U.S.-based candidates) $100K CAD (Canada-based candidates)" -> This is pay and schedule info. Should we include Pay and Schedule sections? The posting states compensation explicitly, so we can include a Pay section. Schedule: "Full-Time" and "Remote - U.S. & Canada Only". Could be a Schedule section or folded into a short p. The instructions: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state compensation and remote/full-time. So we can include Pay and Schedule sections.
- "About Level" section: descriptive prose about the company. Could be "About the Company" or "About Level". Use h3.
- "Your Role (and Impact)" section: describes the role. Could be "About the Role" or "Role Overview". Use h3.
- Then a list of bullet points under "Your Role (and Impact)"? Actually the text after "Your Role (and Impact)" is a paragraph then a list of duties. The duties are listed as bullet points in the original? In the provided text, they are separated by line breaks but not explicit bullet characters. However they are clearly a list of responsibilities. We should format as ul/li.
- "Skills & Qualifications" with "Must-Haves:" and "Preferred:" sublists. This is requirements/qualifications. Could be "Requirements" and "Preferred Qualifications". Use h3 for "Requirements" and maybe "Preferred Qualifications" as subheading? But instructions: use h3 for section headings. Could have "Requirements" and "Preferred Qualifications" as separate h3 sections, or combine under "Qualifications". I'll do "Requirements" for must-haves, and "Preferred Qualifications" for preferred.
- "Education & Experience" with "Must-Haves:" and "Preferred:" sublists. This is also qualifications. Could be separate section "Education & Experience". Use h3.
- "AI Expectations" section: describes AI proficiency expectations. Could be "AI Expectations" or "AI Proficiency". Use h3.
- "Our Core Values" section: list of values. Could be "Core Values". Use h3.
- "Perks & Benefits" section: list of benefits. Use h3 "Benefits".
- "Remote First" section: describes remote work, travel, visa sponsorship. Could be "Work Arrangement" or "Remote Work". Use h3.
- "Level Is Built on Inclusion" section: EEO statement. This is boilerplate? The instructions say remove EEO/equal-opportunity boilerplate. But this is a specific inclusion statement. Might be considered boilerplate. However it's part of the posting. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". So we should remove this section.
- "Ready to Apply?" section: application instructions. Remove.
- "AI HIRING DISCLAIMER" section: legal disclaimer. Remove.
Thus we will keep: Pay, Schedule (maybe combine), About Level, Role Overview, Responsibilities, Requirements, Preferred Qualifications, Education & Experience, AI Expectations, Core Values, Benefits, Remote Work.
But note: The instructions say "Prefer a few substantive sections over many thin ones." So we might combine some.
Let's structure:
- h3 "Pay" with p: "Compensation: $100K USD (U.S.-based candidates), $100K CAD (Canada-based candidates)."
- h3 "Schedule" with p: "Full-time, fully remote across the U.S. and Canada. Occasional travel may be required for company events and team working sessions. Visa sponsorship not available."
- h3 "About Level" with p describing the company.
- h3 "Role Overview" with p describing the role.
- h3 "Responsibilities" with ul of the bullet points.
- h3 "Requirements" with ul of must-haves.
- h3 "Preferred Qualifications" with ul of preferred.
- h3 "Education & Experience" with ul of must-haves and preferred? Could combine into two sublists. But we can have a single section with two sublists. Use h3 "Education & Experience" then maybe two ul with labels? But we need to use ul/li for lists. Could do a p for "Must-Haves:" then ul, then p for "Preferred:" then ul. That's acceptable.
- h3 "AI Expectations" with p and maybe ul? The AI expectations are listed as bullet points in the text. We'll format as ul.
- h3 "Core Values" with ul of values.
- h3 "Benefits" with ul of perks.
- h3 "Remote Work" with p (already covered in Schedule? But we have separate Remote First section. Could combine into Schedule. But the Remote First section includes additional details: "This role is open to U.S. and Canada residents and is fully remote. Occasional travel may be required for company events and team working sessions. We are unable to sponsor visas at this time." That's already in Schedule. So we can omit separate Remote Work section.
Now, ensure we don't include any filler. All content must be from posting.
Let's extract the responsibilities list from the text:
"Own the build, QA, and deployment of email campaigns in Adobe Campaign (Classic or Standard) and/or Adobe Journey Optimizer end to end, ensuring every send is accurate, on time, and on brand
Translate briefs and journey maps into working builds, filling gaps with sound judgment and raising questions early when a brief is incomplete or a requirement won't work as written
Configure audience targeting, personalization, and dynamic content within existing templates and data schemas to improve relevance and engagement
Manage the send calendar, including scheduling, dependency sequencing, and deployment-readiness checks for rendering, links, suppression, and compliance (CAN-SPAM, TCPA, CASL)
Configure and maintain multi-step, multi-channel journeys (email, plus SMS and push where in scope), implementing segmentation, flow control, and decision logic
Run journey QA on logic, timing, and audience entry/exit conditions before activation, so issues are caught before they reach customers
Audit existing campaign and journey builds, workflows, and data schemas, diagnose what is broken, redundant, or misconfigured, and fix it without disrupting live sends
Recommend improvements to journey logic, segmentation, and program performance, explaining the marketing rationale as well as the technical approach
Bring a proposed solution, not just the problem, when escalating structural or data-quality issues that require architecture-level decisions
Communicate clearly with internal teams and client stakeholders, setting expectations, flagging risks, and explaining technical trade-offs in plain language
Document builds and fixes so the team has a clean, reliable handoff trail"
That's 11 items.
Skills & Qualifications Must-Haves:
- Hands-on production experience in Adobe Campaign (Classic or Standard) and/or Adobe Journey Optimizer / Adobe Experience Platform
- A track record of owning CRM work end to end with minimal oversight; you are comfortable being the person who makes it work
- Proven ability to step into an existing instance built by others, diagnose problems, and repair prior configuration rather than only building greenfield
- Strong lifecycle marketing understanding: you can explain why a journey is designed a certain way and spot when it isn't serving the customer or the business
- Sound judgment on when to make a call yourself and when to escalate, with the confidence to push back on a brief that won't work
- Clear written and verbal communication, including explaining technical issues to non-technical stakeholders
- Working knowledge of HTML/CSS for email template troubleshooting and customization
- Working knowledge of email/SMS compliance regulations
Preferred:
- Hands-on experience in Salesforce Marketing Cloud (strongly preferred), such as Journey Builder, Email Studio, Automation Studio, AMPscript, and SQL query activities
- Experience with additional CRM and marketing automation platforms, such as Microsoft Dynamics 365, Klaviyo, or Braze
- Experience with Adobe Experience Platform segments, schemas, and audience activation
- SQL or scripting (JavaScript) for workflow customization and troubleshooting
- Telecom or B2C subscription-industry CRM experience
- Agency-side or client-facing experience
Education & Experience Must-Haves:
- Bachelor's degree in Marketing, Information Systems, Computer Science, Business, or a related field (or 4 additional years of equivalent professional experience)
- 5 to 8 years of hands-on CRM and lifecycle marketing experience, with significant production work in Adobe Experience Cloud email and journey platforms
Preferred:
- Adobe Certified Professional or Expert in Adobe Campaign or Adobe Journey Optimizer
- Salesforce Marketing Cloud certification (e.g., Email Specialist, Developer, or Consultant)
- Agency experience supporting CRM programs for multiple clients simultaneously
AI Expectations: bullet points:
- Experiment continuously with AI tools (e.g., ChatGPT, Midjourney, Claude, Perplexity) to improve the speed, quality, and impact of your work (e.g., draft briefs, summarize research, analyze data trends, generate initial strategic frameworks, identify patterns in large datasets)
- Proactively document and share what you learn—your prompts, process improvements, and use cases—so others can benefit and we can grow together
- Approach AI with an iterative mindset, refining how you apply it to your work over time. The first idea is rarely the best; testing, tweaking, and improving is part of the process
- Lean into discomfort, especially when tools or workflows feel unfamiliar. Growth happens when you're stretching beyond what's comfortable or routine
Core Values:
- No Ego, All In: We don't do "that's not my job." We win together, step in where needed, and care more about the outcome than the org chart
- Better Every Day: We want the feedback, even when it stings. We test, learn, adapt, and keep raising the bar
- Relentless for Results: Activity is nothing without outcomes. We care about the work that moves the business forward
- Driven by Truth: We challenge assumptions, follow the data, and tell clients what they need to hear, not just what is easy to say
Benefits:
- Fully remote across the U.S. & Canada, plus monthly WFH stipend and Summer Fridays
- Generous time off, including unlimited PTO (U.S.), competitive vacation (Canada), and parental/family leave options
- Comprehensive health benefits, mental health support, and company-paid disability & life coverage
- Employer retirement contributions (401(k) in the U.S., RRSP match in Canada)
- Quarterly performance reviews and career advancement opportunities
Now, we need to output HTML fragment.
We'll start with Pay section, then Schedule, then About Level, Role Overview, Responsibilities, Requirements, Preferred Qualifications, Education & Experience, AI Expectations, Core Values, Benefits.
We'll use h3 for each section heading.
We'll use p for prose, ul/li for lists.
Make sure not to include any markdown code fences.
Let's write