Sr. Communications Manager - Science Media Relations
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should not repeat job title as heading. We should not include Job ID etc. Remove boilerplate, navigation, EEO, etc. Also remove duplicated lines, application instructions, etc.
We need to preserve all substantive information. So we need to extract Overview (intro) as maybe "About the role" or maybe just a paragraph. The instruction says use for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can create sections: About the role (overview), Responsibilities, Qualifications (maybe split into Required Qualifications and Preferred Qualifications), Benefits (maybe include Compensation & Benefits). Also maybe "Work-Life Harmonization" could be part of Benefits. But we need to only include sections when posting has real specific content. The posting includes Compensation & Benefits with salary range and benefits details. So we can have a Benefits section (including compensation details). Also maybe "Pay" separate? The instruction says we can have Pay section if posting actually states them. It does state salary range. Could create Pay section with salary range. But also benefits details. Could combine Pay and Benefits into one Benefits section? The instruction says prefer a few substantive sections over many thin ones. So maybe combine Pay and Benefits into a Benefits section that includes salary and benefits. Or we could have separate Pay and Benefits sections if both have content. The posting includes salary range and benefits details. So we could have Pay section with salary range, and Benefits section with benefits list. That would be two sections but both substantive. However instruction says prefer few substantive sections over many thin ones. Two sections is fine.
We also have Overview which could be About the role.
Responsibilities: we have a big list.
Qualifications: we have required qualifications (Bachelor's, 5 years etc.) and preferred qualifications (8 years, supervisory, etc.). Could combine into Qualifications section with subpoints? Could separate Required and Preferred as subheadings? But only allowed headings are those listed; we could still use for Qualifications and then inside have
for Qualifications and then inside have
or
- . Could separate required and preferred as separate
- .
Overview: we can put as
under About the role. We must exclude boilerplate: EEO, EOE, etc. Also remove lines like "Want to help get your resume to the top? Take a look at the experience we require:" maybe that's part of Qualifications intro; we can keep that as prose? It's basically a call to action; might be considered application instruction? It's not exactly instruction to apply, but it's encouraging to look at experience. Might be okay to keep as part of Qualifications intro. However we should remove duplicated lines. Also remove "Software Powered by ICIMS Default: Location : Location US-TX-Dallas Posted Date 6 hours ago (9/16/2026 11:15 AM) Requisition ID 2026-17834 Job Category Marketing, Communications & Public Relations Position Type Full Time". That's metadata; we should drop it. Also remove "Join our Talent Community! Join our Talent Community to receive updates on new opportunities and future events." That's boilerplate. Also remove "In accordance with local and state laws where applicable, qualified applicants with arrest or conviction records will be considered for employment. EOE/Protected Veterans/Persons with Disabilities". Remove. Also remove "This position not a match with your skills? Click here to see other opportunities." Remove. Also remove "#TheAHALife is more than a company culture; it is our way of life. It embodies our commitment to work-life harmonization and is guided by our core values where our employees can thrive both personally and professionally. Discover why you will Be Seen. Be Heard. Be Valued at the American Heart Association by following us on LinkedIn, Instagram, Facebook, X, and at heart.jobs." That's maybe part of overview but could be considered boilerplate? It's about culture; could be kept as part of About the role? It's substantive about company culture. Might be okay to keep. However it's somewhat promotional; but it's part of overview. We'll keep it as part of About the role. We need to preserve all substantive information: The overview includes founding statement, mission, etc. We'll keep that. Now craft HTML. Structure:
About the role
Overview text...
Responsibilities
- ... ...
Qualifications
Required Qualifications:
- ... ...
Preferred Qualifications:
- ... ...
Benefits
Pay: Salary range $86,000.00 to $102,000.00 (minimum to midpoint). Pay is commensurate with experience; geographic differentials may apply.
- Medical, dental, vision, disability, and life insurance
- Robust retirement program with employer match and automatic contribution
- Employee assistance program
- Employee wellness program
- Telemedicine and medical consultation
- Professional development via Employee Resource Groups (ERGs) and mentoring program
- Heart U online university with >100,000 resources
- Paid Time Off (PTO) minimum 16 days per year for new employees, increasing with seniority
- 12 paid holidays per year
- Tuition assistance for career development
- with headings? Might be okay to just list all qualifications in one list, but we need to preserve distinction? The instruction says preserve ALL substantive information; do not invent or summarize away detail. If we combine required and preferred into one list, we lose distinction between required and preferred. That's summarizing away detail? Might be considered losing detail. Better to keep them separate, maybe as two subsections under Qualifications using
? But only allowed headings are those listed; but we could still use inside? The instruction says use for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use for section headings (list). Likely they expect only those headings as . Using other headings may be okay but could be considered not following instruction. Safer to stick to those headings only. So we can have Qualifications section with two lists, each preceded by a indicating "Required Qualifications:" and "Preferred Qualifications:" as prose. That preserves detail.
Similarly Responsibilities: we have a list of duties. We'll put them in
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use for section headings (list). Likely they expect only those headings as . Using other headings may be okay but could be considered not following instruction. Safer to stick to those headings only. So we can have Qualifications section with two lists, each preceded by a indicating "Required Qualifications:" and "Preferred Qualifications:" as prose. That preserves detail.
Similarly Responsibilities: we have a list of duties. We'll put them in
. Using other headings may be okay but could be considered not following instruction. Safer to stick to those headings only. So we can have Qualifications section with two lists, each preceded by a indicating "Required Qualifications:" and "Preferred Qualifications:" as prose. That preserves detail.
Similarly Responsibilities: we have a list of duties. We'll put them in
indicating "Required Qualifications:" and "Preferred Qualifications:" as prose. That preserves detail. Similarly Responsibilities: we have a list of duties. We'll put them in