MANAGER, DIRECT MARKETING TECHNOLOGY AND DATA STRATEGY

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job posting. Key info: - Work Location: US - Atlanta, GA (also remote possible location) - Type of Post: Not Applicable (ignore) - Funding: APPROVED (ignore) - Expected Travel: up to 10% (maybe schedule? Not exactly schedule; travel is not schedule; but we could include under maybe "Schedule"? Not appropriate. Travel is not schedule. Could be omitted if not schedule. The instruction: include Pay/Schedule/Benefits only if posting actually states them. Travel is not schedule. So we may not include schedule. - Type of Contract: (blank) - Language Requirement: English (maybe under Requirements? Could be a qualification) - Application Deadline: (blank) - Employee Duration: Full-Time (maybe schedule? Actually schedule could be full-time; but schedule section is for work schedule like hours, shift. Could include "Full-Time" under Schedule? The instruction: include Schedule section only if posting actually states them. It states Employee Duration: Full-Time. That's about duration, not schedule. Might be considered schedule? Probably not. We'll omit schedule unless we have explicit schedule like "Monday-Friday, 9am-5pm". Not present. - Pay Range Details: $81,083.95 - $113,112.11 Annually USA Grade F Starting salaries are based on various factors... So we have pay info. So we need a Pay section. - Benefits: Not explicitly listed. There's no benefits description. So we should not include Benefits section. - About the role / Who We Are: There's a "Who We Are" paragraph. Also "What We Are Looking For". Also "Job Summary". So we can have an "About the role" section combining Who We Are, What We Are Looking For, Job Summary. - Responsibilities: There's a big block under Responsibilities with multiple subpoints. We'll output as

• each bullet. - Requirements: There's "Required Qualifications" and "Preferred Qualifications". Also maybe "Language Requirement: English". So we can have a Requirements section (maybe split into Required and Preferred? But we only have one heading for Requirements. Could list both required and preferred as list items, maybe with notes. Or we could have separate sections: Requirements and Qualifications? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Requirements and Qualifications sections if content exists. Required Qualifications and Preferred Qualifications could go under Requirements (or Qualifications). Since we have both, we could put Required under Requirements and Preferred under Qualifications. Or we could combine. Let's decide: Use Requirements for required qualifications, Qualifications for preferred qualifications. Also Skills maybe from required/preferred? There's no explicit skills list besides experience. Could put skills under Qualifications? But we have Qualifications heading for preferred qualifications. We'll follow that. - Skills: Not explicitly listed separate; we could omit Skills section if no specific skills beyond experience. The instruction: prefer few substantive sections over many thin ones. So maybe we combine Required and Preferred into Requirements and omit Qualifications. But we have both required and preferred; we could list them under Requirements with subheadings? But we cannot add extra headings besides the allowed ones. We could embed both in a single Requirements section, using

  or

  with notes. That would be fine. Thus sections: About the role, Responsibilities, Requirements, Pay. We need to preserve all substantive information. Must not invent or summarize away detail. Must not include boilerplate like EEO, scam warning, legal, etc. Must remove duplicated lines. We need to include location info? Possibly under About the role? Could include a short paragraph with location and remote possibility. The instruction: do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short

  or drop it. So we can include location in a short

  within About the role or separate? Probably include in About the role as a sentence. We need to include "Type of Contract: Language Requirement: English" maybe as part of Requirements. We need to include "Expected Travel: up to 10%" maybe as part of Responsibilities? Not exactly. Could be a note under About the role? Might be considered part of job details. Could include in About the role as a sentence. We need to include "Funding: APPROVED" maybe minor metadata; could drop. We need to include "Type of Post: Not Applicable" drop. We need to include "Other Possible Location: Remote Work Location" maybe include location note. We need to include "Employee Duration: Full-Time" maybe include in About the role. We need to include "Starting salaries are based on various factors..." that's part of Pay details. We need to include "Salaries listed only apply to jobs based in the US." also part of Pay. We need to include "Starting salaries are based on internal equity, candidate experience, and the cost of labor where the job is based." duplicate; we can keep one. We need to include "Who We Are" paragraph. We need to include "What We Are Looking For" paragraph. We need to include "Job Summary" paragraph. We need to include responsibilities as list. We need to include required qualifications: High School Diploma, GED, or equivalent required; Minimum of 8-10 years’ experience working with data strategies and business processes for complex direct marketing programs in a nonprofit environment; Experience translating the business needs of a fundraising team to ensure the technical teams are positioned to meet needs effectively; Experience in troubleshooting data, process or platform issues which could be creating problems for direct marketing fundraising programs with a focus on creating solutions. Preferred qualifications: Salesforce Certification a plus; Salesforce Certification for Admin, User, and/or Marketing Cloud a plus. Language Requirement: English. We need to include "Type of Contract: Language Requirement: English" maybe as part of Requirements. We need to ensure we don't repeat the job title as a heading. We need to output only HTML fragment. Let's craft:

  About the role

  Location: US - Atlanta, GA (with remote work possible). Full‑time position with up to 10% travel. CARE is a global leader in humanitarian and development work, delivering support to millions each year. The organization seeks individuals who align with its mission of equality and excellence, and who are passionate about collaborating, learning, innovating, and delivering results. At CARE we value diverse talent and encourage applicants who meet the minimum qualifications; preferred qualifications strengthen an application.

  Reporting to the Chief Individual Fundraising Officer, the Manager of Direct Marketing Technology & Data Strategy will be the key technical partner supporting CARE's Mass Market/Mid Level (MM/ML) fundraising team, which raises $60M+ annually. The role focuses on business processes and data that enable the MM/ML strategy across four donor segments (President’s Circle, Inner Circle, Core, Partners for Change) and roughly 20 revenue channels, using tools such as Salesforce NPSP, Snowflake, Luminate, and Salesforce Marketing Cloud. The manager will understand data flow, serve as a subject‑matter expert, translate business rules for technical teams, and work with staff, agencies, and stakeholders to ensure technology meets program needs.

  Responsibilities

  • Understand and manage the business rules and data processes for the four primary donor segments in Mass and Mid programs as they exist in NPSP (CRM) and Snowflake (data mart), including new, current, and lapsed donors, lead generation, and acquisition mail lists.
  • Translate marketing business logic used by the Mass/Mid team for discussions with the CRM team around technical business rules in NPSP.
  • Understand and manage the business rules and data processes for sustaining donors as they exist in Luminate, NPSP and Snowflake.
  • Serve as subject matter expert (SME) for all business and data rules for Mass and Mid strategies and how they are represented in the various technology platforms that CARE uses; translate these concepts to Mass/Mid team members through onboarding and ongoing training.
  • Monitor and alert to any changes in data rules, platforms (Luminate and Marketing Cloud primary) and CRM releases that could disrupt data management for direct mail, email, or telephone marketing.
  • Serve as primary point of contact when working with reporting/analytics teams and technology teams at CARE.
  • Identify potential issues or disconnects as they arise and provide potential solutions.
  • General understanding of how Salesforce NPSP/Snowflake or similar databases gather information in support of reporting and analysis needed for the Mass/Mid team.
  • Work closely with the CRM team, the Cloud for Good team, and the analytics partner, Integral, to understand how data is translated across tools to enable performance management, KPI monitoring, and modeling for future improvement.
  • Understand the reporting logic used for individual Mass/Mid program managers as it relates to data in the reporting/analysis database (Integral’s One‑Click Reporting [OCR]) as well as NPSP/Snowflake.
  • Due to understanding of business rules from NPSP/Snowflake and the impact on reporting/analysis, be able to quickly interpret issues and potential fixes to the appropriate audience (CRM team, analytics partner, program managers).
  • Identify potential issues or disconnects as they arise and provide potential solutions.
  • Serve as the strategy/business‑side owner for Salesforce Marketing Cloud (SFMC), Luminate Online (LO), and Tatango, providing oversight of their data and functionality as a super user, partnering with the CRM counterpart to advise teams of new capabilities as they are released.
  • Act as a communication conduit between the various parties involved as new requirements or issues arise.
  • Serve as primary point of contact for Managed Services vendor, working with the vendor to ensure high‑quality and timely deliverables, and escalating/resolving issues from business teams as necessary.
  • Work with the IT/Digital CRM team to document and implement SFMC/LO/MC policies and procedures.
  • Responsible for ensuring the Development Systems roadmap reflects the needs of the Mass/Mid strategies; in partnership with the IT/Digital CRM team, participate in planning for future phases of systems development to ensure tools continue to evolve to meet the rapidly changing needs of Mass/Mid fundraising.

  Requirements

  • High School Diploma, GED, or equivalent is required.
  • Minimum of 8‑10 years’ experience working with data strategies and business processes for complex direct marketing programs in a nonprofit environment.
  • Experience translating the business needs of a fundraising team to ensure the technical teams are positioned to meet needs effectively.
  • Experience in troubleshooting data, process or platform issues which could be creating problems for direct marketing fundraising programs, with a focus on creating solutions.
  • Language requirement: English.
  • Preferred qualifications: Salesforce Certification (Admin, User, and/or Marketing Cloud) a plus.

  Pay

  Salary range: $81,083.95 – $113,112.11 annually (USA Grade F). Starting salaries are based on factors such as candidate experience, education, knowledge, skills, and the cost of labor where the job is based; the listed range applies only to jobs based in the US.

  We need to ensure we didn't include any boilerplate like EEO, scam warning, legal, etc. We removed those. Check for duplicated lines: we have some repeated sentences about identifying potential issues; we included twice (once under