Social & Communications Manager
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should map content accordingly.
We need to include sections only when posting has real specific content.
We have:
- Who We Are: description of company. Could be "About the role"? Actually "Who We Are" is about company, not role. But we could treat as "About the role"? The instruction examples include "About the role". However we can also use other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings when appropriate. If we have content that matches those headings, we use them. For company description maybe we could put under "About the role"? But that's not accurate. However we could still use "About the role" heading and put company description there? Might be okay but could be considered filler? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." It doesn't forbid other headings besides those examples, but says use
for section headings (e.g. About the role, Responsibilities...). Likely they expect us to use those headings for sections we have. So we need to map content to those headings.
We have:
- Summary: description of role. Could go under "About the role". That seems appropriate.
- Responsibilities: list.
- Required Qualifications: could be "Requirements" or "Qualifications". We have both Required and Preferred Qualifications. Could combine into "Qualifications" section with required and preferred? Or separate "Requirements" and "Qualifications"? The examples include Requirements, Qualifications, Skills. We could put Required Qualifications under "Requirements" and Preferred under "Qualifications" or "Skills". But we need to avoid thin sections. Perhaps combine required and preferred into one "Qualifications" section with subheadings? But we cannot add extra headings besides . Could use
to differentiate. Better: Use "Requirements" for required qualifications, and "Qualifications" for preferred qualifications. Or "Skills" for skills. We have also "Compensation And Benefits" with salary range and benefits details. So we need "Pay" and "Benefits" sections. The instruction: include a section ONLY when posting has real specific content. We have salary range and benefits details, so we can include both Pay and Benefits. We also have "Relocation Assistance Offered Within Country" - that's a benefit maybe. Could be included in Benefits. We have no explicit Schedule info, so omit Schedule. We have no explicit Skills section separate; we could put skills under Qualifications. We need to preserve all substantive information, not invent or summarize away detail. So we must keep all details from the posting. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we must cut out the "Our Commitment to Inclusion", "Equal Opportunity Employer", "Reasonable accommodation..." etc. Also remove duplicated lines: there is a duplicated line "Lead the strategic direction of PR initiatives in partnership with our PR agency of record (AOR), ensuring campaigns align with overarching business and marketing objectives." appears twice in Responsibilities. We need to keep only one instance. Also remove "Job Number #176175 - New York, New York, United States" maybe as metadata; we can fold into a short
or drop it. Probably drop it. We need to keep "Relocation Assistance Offered Within Country" maybe as a benefit. Now craft HTML. Structure:
About the role
Summary paragraph: The Manager, PR & Communications will be a key leader on the Integrated Marketing team... (the summary paragraph). Also include Who We Are? Could be included in same paragraph or separate? The Who We Are is about company; maybe we can include as part of About the role? But it's not about role. However we could add another heading like "About Colgate-Palmolive"? Not in examples. But we could still include as a
under About the role? Might be okay but could be considered not specific to role. However we must preserve all substantive information; we cannot drop Who We Are. So we need to include it somewhere. Perhaps we can add a heading "About the company" but not in examples. The instruction says use
for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but says use for section headings (e.g...). It might be okay to use other headings as long as they are . Safer to stick to given headings. Could we incorporate Who We Are into About the role as a brief intro? It's not about role but we could still put it there; it's still substantive. Might be acceptable.
Alternatively we could create a section "About Colgate-Palmolive" using . The instruction didn't forbid that; it just gave examples. I think it's fine.
Thus we will have:
About Colgate-Palmolive
. Safer to stick to given headings. Could we incorporate Who We Are into About the role as a brief intro? It's not about role but we could still put it there; it's still substantive. Might be acceptable.
Alternatively we could create a section "About Colgate-Palmolive" using . The instruction didn't forbid that; it just gave examples. I think it's fine.
Thus we will have:
About Colgate-Palmolive
About Colgate-Palmolive
Who We Are content.
About the role
Summary content.
Responsibilities
- ... ...
Requirements
Required Qualifications content.
Qualifications
Preferred Qualifications content.
Pay
Salary range and details.
Benefits
- ... ...