Adobe Email Marketing Specialist

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. We must not repeat job title. Must not include Job ID etc. Remove boilerplate. We need to parse the posting. First, there is an intro about Reingold (company description). That could be "About the role"? Actually "About the role" is a section heading for description of role. The company description could be placed under "About the role"? Usually "About the role" includes description of role and maybe company. We'll include a paragraph summarizing the role and company. Then "Essential Functions Here’s the work you’ll do:" list of duties. That's responsibilities. Then "This job description is not designed to cover..." ignore. Then "This role is a good fit for someone with these qualifications, experience and skills:" then "Required Qualifications" list. Then "Preferred Qualifications:" list. Then "Supervisory Responsibilities:" note no direct supervisory responsibilities. Then "Work environment and physical requirements:" sentence. Then "Additional Information": salary range, benefits, etc. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. - About the role: could include company description and role summary. - Responsibilities: the essential functions list (bulleted). - Requirements: maybe required qualifications. - Qualifications: maybe preferred qualifications? Or we could combine required and preferred under Qualifications? But we have both Requirements and Qualifications sections. Could treat Requirements as required qualifications, Qualifications as preferred qualifications. - Skills: maybe list of skills from required qualifications (SQL, JavaScript, etc.) but we could also put them under Requirements. However we need to avoid duplication. Could put skills under Skills section summarizing technical skills. - Benefits: from Additional Information: comprehensive health and wellness benefits, 401(k) employer contributions and matching, other benefits. - Pay: salary range $64,400 to $109,000, budgeted starting salary lower half. - Schedule: hybrid role requiring at least two days per week on site. We must not include sections with placeholder or vague content. Ensure each section has substantive content. We must not include boilerplate like EEO, legal, etc. We must not include duplicated lines. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like specific tasks, qualifications, etc. We need to output only HTML fragment, using

for section headings,

• for lists,

  for prose. We must not include markdown fences. Let's craft. First, About the role: combine company description and role summary. We can write a paragraph: "Reingold is a full-service marketing and creative firm in Alexandria, VA with over 40 years of experience helping government, nonprofit, and business organizations make the world a better place. The Adobe Email Marketing Specialist will build and run email and cross-channel campaigns using Adobe Campaign and Adobe Journey Optimizer, designing workflows, managing data models, ensuring deliverability, and executing campaigns end-to-end." That's substantive. Second, Responsibilities: list of essential functions. We need to extract each bullet from "Essential Functions Here’s the work you’ll do:" The text after colon includes many sentences separated by periods and em dashes. We need to break into list items. Let's parse: - Design, build, and maintain the Adobe Campaign workflows behind client programs — targeting, segmentation, enrichment, deduplication, scheduling, and recurring and continuous deliveries — and own them in production once they're live. - Write and optimize the SQL and JavaScript inside those workflows, and diagnose the queries that are quietly slowing a campaign down. - Extend and maintain the Campaign data model: custom schemas, input forms, navigation, and the mapping between Campaign and client-side data sources — making the calls on how campaign data is structured and consumed. - Build and maintain imports, exports, and integrations with CRM, web analytics, and client systems (SFTP, APIs, file-based feeds), and keep them running when the data on the other end changes. - Own the technical side of email deliverability — authentication (SPF, DKIM, DMARC), IP and domain warming, bounce and quarantine handling, suppression logic, and seed and inbox placement testing. - Execute the campaign calendar end to end: audience pulls, template builds, proofing, stakeholder approvals, scheduling, and deployment. - Manage lists, preference centers, subscription services, and unsubscribe handling in line with CAN-SPAM and client consent requirements. - Build and deliver campaign reporting, design and run A/B and multivariate tests, and turn the results into recommendations clients can act on — not just numbers forwarded along. - Maintain runbooks and documentation so campaign execution doesn't live in one person's head, and integrate AI into the daily workflow where appropriate to streamline the repetitive parts. We should keep each as

• . Third, Requirements: Required Qualifications list. We need to extract each bullet. Required Qualifications: - At least 4 years of hands-on Adobe Campaign or AJO experience (Campaign Classic v7, Campaign v8, Campaign v8 Client Console, Campaign Standard, or the Campaign Web UI), including production ownership — you've built and run workflows people depended on, not just supported someone else's. - Demonstrated ability to build multi-step workflows independently, from targeting through delivery and post-processing, and to walk us through why each activity is there. - Strong SQL — joins, aggregations, subqueries, and enough comfort reading an execution plan to know why something is slow — plus JavaScript sufficient for Campaign's scripting contexts (workflow activities, personalization, JSSP). - Solid grasp of relational data modeling and how Campaign's schema layer sits on top of it. - Practical email deliverability knowledge: authentication, sender reputation, bounce handling, and list hygiene. - HTML and CSS for email, including responsive patterns and the quirks of major email clients. - Working knowledge of CAN-SPAM and consent and opt-out requirements. - Excellent oral and written communication skills, including the ability to explain technical constraints to non-technical stakeholders. We'll list each as
• . Fourth, Qualifications: Preferred Qualifications list. Preferred Qualifications: - Hands-on experience in AJO — building event-triggered, batch, and unitary journeys, including conditions, wait activities, and journey versioning. - Working knowledge of Adobe Experience Platform underneath AJO: XDM schemas, datasets, identities and identity graphs, unified profile, and audience definitions. - Message authoring in AJO across email, SMS, push, in-app, and web, including content templates, fragments, and personalization syntax; exposure to Decisioning, content experiments, or journey reporting is a plus. - An informed point of view on how Adobe Campaign and AJO coexist — where data flows between them, what each is better at, and what a phased migration actually involves. - Adobe certification in either platform — Adobe Certified Expert, Adobe Campaign Developer, or Adobe Certified Expert, Adobe Journey Optimizer Developer (AD0-E606), or the Professional-level equivalents. - Experience migrating from Campaign Classic v7 to Campaign v8, or working in the Campaign Web UI. - Experience with other Adobe platforms like AEP, AEM, Analytics/CJA, Audience Manager, or Target. - Public sector, government, nonprofit, association, or advocacy campaign experience. - Agency background — comfort with multiple concurrent clients, timesheets, and shifting priorities. - Familiarity with an adjacent ESP or marketing automation platform (Salesforce Marketing Cloud, Marketo, Eloqua, Braze) for context on trade-offs. We'll list each as
• . Fifth, Skills: maybe we could summarize technical skills not already covered? But we already covered many skills in Required and Preferred. Could we still have a Skills section? Might be redundant. The instruction: Prefer a few substantive sections over many thin ones. So maybe we skip Skills if content overlaps. But we need to include sections only when posting has real specific content for it. The posting does have skill mentions, but they are already in Required/Preferred. Could we still create a Skills section that extracts skill keywords? Might be considered summarizing. Better to omit Skills section to avoid thin duplication. Sixth, Benefits: from Additional Information: "Full-time employees are eligible for comprehensive health and wellness benefits, 401(k) employer contributions and matching, and other benefits." Also earlier: "We offer competitive salaries, a comprehensive benefits package, a dynamic hybrid work environment, a vibrant workplace and growth opportunities in a variety of specialty areas." That's benefits. We'll include bullet list: comprehensive health and wellness benefits, 401(k) employer contributions and matching, other benefits (maybe also dynamic hybrid work environment, vibrant workplace, growth opportunities). But those are more about work environment. Benefits section should focus on benefits. We'll list: comprehensive health and wellness benefits, 401(k) employer contributions and matching, other benefits. Also maybe mention competitive salaries but that's Pay. We'll keep Benefits as
  • Comprehensive health and wellness benefits
  • 401(k) employer contributions and matching
  • Other benefits
  . Seventh, Pay: salary range $64,400 to $109,000, budgeted starting salary in lower half. We'll put paragraph. Eighth, Schedule: hybrid role requiring at least two days per week on site at Reingold’s headquarters in Alexandria, VA. Also mention dynamic hybrid work environment earlier. We'll put paragraph. We must not include sections like "About Reingold" separate; we incorporated into About the role. Check for any boilerplate: we removed EEO, legal, accommodation, drug policy, visa, security clearance, equal opportunity, etc. Now produce HTML. Structure:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Requirements

  ...

  Qualifications

  ...

  Benefits

  ...

  Pay

  ...

  Schedule

  ...

  Make sure no extra whitespace? It's fine. Let's craft the paragraphs precisely. About the role paragraph: "Reingold is a full-service marketing and creative firm in Alexandria, VA with over 40 years of experience helping government, nonprofit, and business organizations make the world a better place. The Adobe Email Marketing Specialist will build and run email and cross-channel campaigns using Adobe Campaign and Adobe Journey Optimizer, designing workflows, managing data models, ensuring deliverability, and executing campaigns end-to-end." That's good. Responsibilities list: we need to keep the exact phrasing as much as possible. Let's copy each bullet. 1. Design, build, and maintain the Adobe Campaign workflows behind client programs — targeting, segmentation, enrichment, deduplication, scheduling, and recurring and continuous deliveries — and own them in production once they're live. 2. Write and optimize the SQL and JavaScript inside those workflows, and diagnose the queries that are quietly slowing a campaign down. 3. Extend and maintain the Campaign data model: custom schemas, input forms, navigation, and the mapping between Campaign and client-side data sources — making the calls on how campaign data is structured and consumed. 4. Build and maintain imports, exports, and integrations with CRM, web analytics, and client systems (SFTP, APIs, file-based feeds), and keep them running when the data on the other end changes. 5. Own the technical side of email deliverability — authentication (SPF, DKIM, DMARC), IP and domain warming, bounce and quarantine handling, suppression logic, and seed and inbox placement testing. 6. Execute the campaign calendar end to end: audience pulls, template builds, proofing, stakeholder approvals, scheduling, and deployment. 7. Manage lists, preference centers, subscription services, and unsubscribe handling in line with CAN-SPAM and client consent requirements. 8. Build and deliver campaign reporting, design and run A/B and multivariate tests