AVP, Specialty & Wellness Marketing
Synchrony · Cincinnati, OH · 1 mo ago
MarketingFull-time
We need to output HTML fragment with sections: About the role? The posting includes Role Summary/Purpose, Essential Responsibilities, Qualifications/Requirements, Desired Characteristics, Grade/Level, Salary range, Our Way Of Working, Eligibility Requirements, Our Commitment, Reasonable Accommodation Notice, Job Family Group.
We must only include sections when posting has real specific content. We must not repeat job title as heading. Use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we need to map content to these headings. The instructions: "use
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we need to map content to these headings. The instructions: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings if appropriate. We need to decide which sections to include based on content.
We have:
- Role Summary/Purpose: could be "About the role".
- Essential Responsibilities: "Responsibilities".
- Qualifications/Requirements: "Qualifications" (or Requirements). There's also "Desired Characteristics": could be "Skills".
- Grade/Level: maybe not needed; but could be part of Qualifications? Not a standard heading; but we could include as part of Qualifications? Probably not needed.
- Salary range: "Pay".
- Our Way Of Working: maybe "Schedule"? Actually schedule refers to work schedule; but we have remote/hybrid info. Could be "Schedule" if they mention work location flexibility. Might be appropriate.
- Eligibility Requirements: could be "Requirements"? But we already have Requirements maybe for qualifications. However eligibility includes legal stuff, drug test, etc. Might be considered "Requirements". But we need to avoid duplication. Perhaps we can combine eligibility into a short paragraph under Requirements? But we must preserve all substantive info. Could create a separate section like "Eligibility" but not in allowed headings list. The instruction says use those headings as examples, but not limited? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings; we could also use other headings if needed? It says use those for section headings (e.g.) implying those are the allowed headings. Probably we should stick to those.
Thus we need to map content to those headings.
We have:
- About the role: Role Summary/Purpose.
- Responsibilities: Essential Responsibilities.
- Qualifications: Qualifications/Requirements (Bachelor's degree etc).
- Skills: Desired Characteristics (experience with multi-location, healthcare, Salesforce, etc).
- Pay: Salary range.
- Schedule: Our Way Of Working (flexibility, remote/hub).
- Benefits: Not explicitly listed; there is mention of bonus eligibility, but not benefits like health insurance. Could we create Benefits section? The posting mentions eligibility for annual bonus, but not benefits. Might be considered part of Pay? But we have Pay separate. Benefits could be omitted if not present. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. Benefits not stated, so omit Benefits.
We also have other info like Grade/Level, Eligibility Requirements, Our Commitment, Reasonable Accommodation Notice, Job Family Group. Those are not in allowed headings; maybe we can incorporate them into existing sections as paragraphs if relevant. For example, Grade/Level could be part of Qualifications. Eligibility Requirements could be part of Requirements? But we already have Requirements heading for qualifications; maybe we rename? Actually we have both Requirements and Qualifications headings. The example list includes both Requirements and Qualifications as separate. So we can use Requirements for eligibility/legal requirements, and Qualifications for education/experience. Skills for desired characteristics.
Thus:
- About the role: role summary.
- Responsibilities: essential responsibilities.
- Requirements: eligibility requirements (legal, drug test, background, etc) plus maybe grade/level? But grade/level is not eligibility; could be part of Qualifications. Let's put grade/level in Qualifications.
- Qualifications: education/experience requirements (Bachelor's degree or HS + 8 years, 4+ years multi-channel, client-facing, B2B, travel willingness).
- Skills: desired characteristics (multi-location, healthcare, Salesforce, digital savvy, project management, communication).
- Pay: salary range + bonus eligibility.
- Schedule: Our Way Of Working (flexibility, remote/hub, commute to hub).
We must not include boilerplate like EEO, legal accommodation notice, etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should omit Our Commitment, Reasonable Accommodation Notice, Job Family Group, EEO statements, etc.
Also remove duplicated lines.
Now we need to output HTML fragment only, no /, no markdown fences.
We'll produce:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings; we could also use other headings if needed? It says use those for section headings (e.g.) implying those are the allowed headings. Probably we should stick to those.
Thus we need to map content to those headings.
We have:
- About the role: Role Summary/Purpose.
- Responsibilities: Essential Responsibilities.
- Qualifications: Qualifications/Requirements (Bachelor's degree etc).
- Skills: Desired Characteristics (experience with multi-location, healthcare, Salesforce, etc).
- Pay: Salary range.
- Schedule: Our Way Of Working (flexibility, remote/hub).
- Benefits: Not explicitly listed; there is mention of bonus eligibility, but not benefits like health insurance. Could we create Benefits section? The posting mentions eligibility for annual bonus, but not benefits. Might be considered part of Pay? But we have Pay separate. Benefits could be omitted if not present. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. Benefits not stated, so omit Benefits.
We also have other info like Grade/Level, Eligibility Requirements, Our Commitment, Reasonable Accommodation Notice, Job Family Group. Those are not in allowed headings; maybe we can incorporate them into existing sections as paragraphs if relevant. For example, Grade/Level could be part of Qualifications. Eligibility Requirements could be part of Requirements? But we already have Requirements heading for qualifications; maybe we rename? Actually we have both Requirements and Qualifications headings. The example list includes both Requirements and Qualifications as separate. So we can use Requirements for eligibility/legal requirements, and Qualifications for education/experience. Skills for desired characteristics.
Thus:
- About the role: role summary.
- Responsibilities: essential responsibilities.
- Requirements: eligibility requirements (legal, drug test, background, etc) plus maybe grade/level? But grade/level is not eligibility; could be part of Qualifications. Let's put grade/level in Qualifications.
- Qualifications: education/experience requirements (Bachelor's degree or HS + 8 years, 4+ years multi-channel, client-facing, B2B, travel willingness).
- Skills: desired characteristics (multi-location, healthcare, Salesforce, digital savvy, project management, communication).
- Pay: salary range + bonus eligibility.
- Schedule: Our Way Of Working (flexibility, remote/hub, commute to hub).
We must not include boilerplate like EEO, legal accommodation notice, etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should omit Our Commitment, Reasonable Accommodation Notice, Job Family Group, EEO statements, etc.
Also remove duplicated lines.
Now we need to output HTML fragment only, no /, no markdown fences.
We'll produce:
About the role
... role summary ...
Responsibilities
- ... each responsibility ...
- Serve as the marketing owner and primary point-of-contact for assigned clients/partners; align marketing priorities to partner objectives and Specialty & Wellness growth goals; develop quarterly/annual client marketing plans, integrated calendars, and activation roadmaps; coordinate priorities with Sales and Client leaders; support partner operating rhythms including campaign plans, program updates, and QBR content.
- Lead end-to-end execution of multi-channel B2B and B2B2C campaigns to drive provider/location onboarding and engagement, consumer applications, approvals, and purchase volume growth, usage and retention through lifecycle motions; execute targeted account-based/segment-based marketing for priority partner segments and locations; drive point-of-sale/in-location conversion through toolkits, signage, scripts, and training/enablement materials that make financial conversations easier for front-line teams; build and optimize market acquisition and lifecycle communications including email automation and journey mapping (e.g., Salesforce Marketing Cloud or similar platforms) working with cross-functional teams; create and manage content to support acquisition and engagement objectives (case studies, webinars, one-pagers, playbooks, emails, partner toolkits).
- Use analytics, testing, and segmentation to optimize performance; recommend improvements to targeting, messaging, channel mix, and offers/promotions (where applicable); track and communicate outcomes against KPIs (e.g., lead volume, conversion, applications, approvals, purchase volume, usage, ROI).
- Influence and coordinate work across internal partners (Sales, Client Management, Lifecycle, Product, Operations, Risk/Compliance, Finance, Creative/Agency) to deliver quality work on time; perform other duties and/or special projects as assigned.