Sr. Manager, Corporate Communications
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real, specific content. We must not repeat job title as heading. We must not put Job ID etc. Remove boilerplate like EEO, legal, etc. Must preserve all substantive info.
We need to extract content: About Pinterest (mission etc). That could be "About the role"? Actually "About the role" is generic; but we have "About Pinterest" describing company. Could map to "About the role"? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those headings if content matches. We have "About Pinterest" which is about company, not role. Could still use "About the role" heading and put that content? Might be okay. But we need to ensure we don't create filler sections. We have content for responsibilities (What You’ll Do). That's responsibilities. We have qualifications (What We’re Looking For) includes required and preferred qualifications. Could split into Requirements and Qualifications? The instruction says we can have both Requirements and Qualifications sections. We need to decide what goes where. Typically Requirements = mandatory qualifications; Qualifications = preferred? Or we could combine. But we have both required and preferred. We'll put required under Requirements, preferred under Qualifications. Also we have Skills maybe from required: strong media instincts, writing/editing, AI tools, etc. Could be Skills section. But we might avoid too many thin sections. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one? But we have headings list; we can choose to include only those with substantive content. We need to include sections only when posting has real, specific content for it. So we need to decide which sections we have content for.
We have:
- About the role / About Pinterest: we have introductory paragraph about Pinterest mission and AI etc. That's substantive.
- Responsibilities: "What You’ll Do" bullet list (actually sentences). That's substantive.
- Requirements: mandatory qualifications: 10+ years experience, strong media instincts, excellent writing/editing, experience using AI tools, Bachelor's degree. That's substantive.
- Qualifications (preferred): experience in-house at global publicly traded tech, supporting multiple business lines, advertising/monetization B2B storytelling, familiarity with policy/trust & safety/regulatory communications. That's substantive.
- Skills: could be overlapping with requirements; maybe we can skip separate Skills to avoid thin.
- Benefits: posting mentions equity eligibility, base salary range, relocation statement (not eligible), in-office requirement statement, culture and benefits link. It mentions "The position is also eligible for equity." and "In an effort to provide greater transparency, we are sharing the base salary range for this position." Also "Information regarding the culture at Pinterest and benefits available for this position can be found here." So we have some benefits info: equity eligibility, base salary range, maybe mention of benefits link. Also relocation statement (not eligible) and in-office requirement. Those could go under Benefits or Schedule? Actually schedule: in-office requirement statement about attendance varies. Could be Schedule. But we have no explicit schedule like full-time/part-time. The in-office requirement statement is about attendance. Could be Schedule. However we have also "Relocation Statement: This position is not eligible for relocation assistance." That's not schedule.
We have Pay: base salary range $146,561—$301,744 USD. Also equity eligibility.
Thus we can have Benefits section (equity, maybe mention of benefits link) and Pay section (salary range). Schedule maybe we can include in-office requirement statement. But we need to avoid filler like "not specified". We have specific statement: "While Pinterest operates in a flexible work environment, attendance in the office will vary based on responsibilities such as earnings or other key corporate engagements." That's specific enough for Schedule.
Thus we can include sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule.
We must not include headings with filler. Ensure we don't include empty sections.
Now we need to output HTML fragment only, no /, no markdown fences.
We'll structure:
About the role
About the role
... content ...
Responsibilities
- ... each duty ...
or
- ? It's a statement; we can put as
. Now About the role: we have introductory paragraphs about Pinterest mission, AI, interview philosophy, etc. Also the sentence: "Pinterest is looking for a Senior Corporate Communications Manager to help shape how our business, strategy and growth are understood by key external audiences." That's part of role description. We'll include that. We need to avoid repeating job title as heading; we are not. Now we must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes EEO statement, commitment to inclusion, etc. We must remove those. Also remove "Our Commitment To Inclusion" paragraph. Also remove "By submitting this application..." etc. Also remove "Visit our PinFlex page to learn more about our working model." That's maybe okay? It's about working model; could be considered part of benefits? But it's a link; we could keep as part of Benefits? It's not a benefit per se. Might be considered boilerplate? It's about working model; maybe we keep as part of Benefits? But it's a statement about working model; could be considered part of Benefits or Schedule? It's not strictly required. However we need to preserve ALL substantive information; this is substantive about working model. Could include under Benefits or Schedule. But we already have Schedule about in-office requirement. The PinFlex page is about flexible work model; we could mention under Benefits as "Learn more about our working model via PinFlex page." Might be okay. But we need to ensure we don't include EEO etc. So we will omit those paragraphs. Now we need to output only HTML fragment. Let's craft. We'll start with
About the role
...
We need to combine the introductory paragraphs: "About Pinterest Millions of people around the world come to our platform to find creative ideas, dream about new possibilities and plan for memories that will last a lifetime. At Pinterest, we’re on a mission to bring everyone the inspiration to create a life they love, and that starts with the people behind the product. Discover a career where you ignite innovation for millions, transform passion into growth opportunities, celebrate each other’s unique experiences and embrace the flexibility to do your best work. Creating a career you love? It’s Possible. At Pinterest, AI isn't just a feature, it's a powerful partner that augments our creativity and amplifies our impact, and we’re looking for candidates who are excited to be a part of that. To get a complete picture of your experience and abilities, we’ll explore your foundational skills and how you collaborate with AI. Through our interview process, what matters most is that you can always explain your approach, showing us not just what you know, but how you think. You can read more about our AI interview philosophy and how we use AI in our recruiting process here. Pinterest is looking for a Senior Corporate Communications Manager to help shape how our business, strategy and growth are understood by key external audiences. This person will play a central role in telling Pinterest’s corporate story across business, financial and advertiser audiences, while helping protect and strengthen the company’s reputation during high-stakes moments. This person will be a trusted thought partner and hands-on operator who can translate complex business priorities into clear, compelling narratives and lead execution across proactive and