Senior PR & Communications Manager
The Business of HLTH Podcast · San Francisco, CA · 1 mo ago
Marketing$175k–$236k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (or Qualifications?), Skills, Benefits, Pay, Schedule. Use for each heading. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info.
We need to parse the posting.
First part: "About Mixpanel" description: that's company overview, not needed? Probably not a section. The instructions: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to extract content for each.
We have "About The Role" paragraph: that is about the role description. So we can put that under
for each heading. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info.
We need to parse the posting.
First part: "About Mixpanel" description: that's company overview, not needed? Probably not a section. The instructions: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to extract content for each.
We have "About The Role" paragraph: that is about the role description. So we can put that under About the role
with
content. Responsibilities: there is a big list with subheadings: Media relations, Product Launches & Company News, Agency & partner management, Internal communications, Crisis & issues management, Executive communications. Each has bullet-like sentences. We need to output
- for any list of duties/requirements/benefits. So we can create a
- with each responsibility as
- . Possibly we could keep subheadings inside li? But instructions: Use
- for any list of duties/requirements/benefits. So we can flatten.
We need to preserve all substantive info. So each bullet should contain the text from each responsibility section.
Let's extract:
Media relations:
- Cultivate and maintain relationships with journalists, editors, and producers covering enterprise tech, analytics, AI, data, and SaaS
- Drive earned media coverage in top-tier business and trade outlets
- Develop compelling story angles, press materials, pitches, and messaging frameworks
- Serve as a primary media contact and help prepare spokespeople for interviews and public presentations
- Establish and track metrics to monitor the health of Mixpanel’s coverage
Product Launches & Company News:
- Partner closely with Product Marketing to develop and execute PR strategies for major product announcements
- Manage PR and comms activities for company news and announcements
- Ensure messaging is consistent, differentiated, and resonant with technical and business audiences
Agency & partner management:
- Manage agency relationships in the US, EMEA, and APAC, setting clear priorities, KPIs, and workflows
- Serve as the internal contact and day-to-day liaison, ensuring agency output aligns with Mixpanel's voice and goals
Internal communications:
- Partner with the People team and leadership to craft internal announcements and other types of internal messaging
- Support the development of internal communication programs that keep employees informed and connected to the company's narrative
Crisis & issues management:
- Monitor the media and competitive landscape for potential reputational issues
- Support the development of crisis communications protocols and serve as a strategic voice in sensitive situations
Executive communications:
- Identify, pursue, and manage award submissions, podcast appearances, and speaking opportunities at key industry conferences and events
- Develop and maintain LinkedIn content strategies for executives, helping amplify their voice and build their professional presence
- Collaborate with executives on bylines and contributed articles, from ideation through to final draft
- Develop and execute broader thought leadership narratives and plans for executives and the company
Now Requirements/Qualifications/Skills: The posting has "We're Looking For Someone Who Has" list. That includes experience requirements etc. Also "Bonus Points For". So we can combine into Requirements (maybe Qualifications) and Skills. The instruction: Use headings for About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content.
We have content for Requirements: "7+ years of communications experience, with a strong preference for candidates who have worked both in-house at a B2B tech company and at a PR agencyExperience in one or more of the following spaces: analytics, data, AI, engineering, product development. You understand the audience and know how to translate technical concepts into stories that resonate.Exceptional writer and editor across formats: press releases, media pitches, executive messaging, bylines, internal announcements, and social contentStrong verbal communicator with confidence presenting to and advising senior stakeholdersStrong storytelling skills and news judgmentA track record of securing meaningful coverage in top-tier and tech outlets Experience managing external agencies and partners and working cross-functionally with various internal partnersComfortable working independently in an ambiguous, fast-moving environment — this is a building roleExperience working with PR agencies or teams outside of the United StatesJournalism training or prior experience as a reporter/editor is a genuine plus"
That's a block of text; we can split into list items.
Also "Bonus Points For" list: Familiarity with analyst relations (Gartner, Forrester, IDC) in a B2B SaaS contextExperience supporting a company through a major growth phase, rebrand, or category creation momentExperience working as a PR team of oneExisting relationships with reporters covering enterprise software, product management, data infrastructure, analytics, and/or AI
We could treat these as additional qualifications/skills. Could put under Requirements or Skills. Since we have both Requirements and Skills headings possible, we could put the core requirements under Requirements, and bonus points under Skills. Or combine.
Better: Requirements: the mandatory qualifications. Skills: the bonus points and maybe skill-based items like exceptional writer, etc. But the instruction: Prefer a few substantive sections over many thin ones. So maybe we just have Requirements (including both mandatory and bonus) and maybe Skills not needed. But we need to follow instruction: include a section ONLY when posting has real, specific content for it. So we can include Requirements and Skills if we have distinct content.
We have mandatory qualifications list; we also have skill-based items like exceptional writer, strong verbal communicator, storytelling skills, news judgment, track record, managing agencies, comfortable working independently, experience with non-US PR agencies, journalism training plus. Those could be considered skills. Bonus points are extra.
Thus we can have Requirements (mandatory experience) and Skills (writer, communicator, etc.) and maybe Bonus under Skills as well.
But to avoid too many sections, we could combine Requirements and Skills into one "Requirements" section that includes all. However the instruction says we can use those headings; not required to use all. So we can just have Requirements section with all qualification content. That would be substantive.
Benefits: The posting has "Benefits And Perks" list: Comprehensive Medical, Vision, and Dental Care, Mental Wellness Benefit, Generous Vacation Policy & Additional Company Holidays, Enhanced Parental Leave, Volunteer Time Off, Additional US Benefits: Pre-Tax Benefits including 401(K), Wellness Benefit, Holiday Break. Also note about contract positions varies (but we can ignore). So we have benefits content.
Pay: The posting has "Compensation" section with salary range $174,500 - $236,000 USD, plus equity, etc. So we have Pay content.
Schedule: The posting mentions "This role requires two days per week in our San Francisco or New York office." That's schedule info (hybrid). So we can include Schedule.
Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule.
We should not include Qualifications or Skills separately if we merged into Requirements.
Now we need to output HTML fragment only, no or . Use
for each heading. Use
for prose. Use
- for lists.
We need to preserve all substantive info; do not invent or summarize away detail. So we must include all details from each section.
Let's craft each.
About the role: The paragraph under "About The Role". It includes multiple sentences. We'll put as
. Responsibilities: We'll create
- with each bullet as
- . Should we keep the subheadings inside li? Probably we can include them as part of the li text. Eg: "
- Media relations: Cultivate and maintain relationships..." but we cannot add unless it's in original? The instruction didn't forbid adding markup for emphasis, but better to keep plain text. We can include the heading as part of the sentence: "Media relations: Cultivate and maintain relationships..." That preserves info.
Thus each li will be like: "Media relations: Cultivate and maintain relationships with journalists, editors, and producers covering enterprise tech, analytics, AI, data, and SaaS; Drive earned media coverage in top-tier business and trade outlets; Develop compelling story angles, press materials, pitches, and messaging frameworks; Serve as a primary media contact and help prepare spokespeople for interviews and public presentations; Establish and track metrics to monitor the health of Mixpanel’s coverage". But that's long; maybe better to split each bullet per sub-bullet. However the instruction says use
- for any list of duties/requirements/benefits. It doesn't forbid nested lists? Could do nested
- inside li for sub-bullets. But to keep simple, we can make each responsibility category as a li with its subpoints as separate sentences separated by semicolons. That preserves all info.
We need to ensure we don't lose any detail. Let's list each category with its subpoints.
Media relations subpoints:
- Cultivate and maintain relationships with journalists, editors, and producers covering enterprise tech, analytics, AI, data, and SaaS
- Drive earned media coverage in top-tier business and trade outlets
- Develop compelling story angles, press materials, pitches, and messaging frameworks
- Serve as a primary media contact and help prepare spokespeople for interviews and public presentations
- Establish and track metrics to monitor the health of Mixpanel’s coverage
Product Launches & Company News:
- Partner closely with Product Marketing to develop and execute PR strategies for major product announcements
- Manage PR and comms activities for company news and announcements
- Ensure messaging is consistent, differentiated, and resonant with technical and business audiences
Agency & partner management:
- Manage agency relationships in the US, EMEA, and APAC, setting clear priorities, KPIs, and workflows
- Serve as the internal contact and day-to-day liaison, ensuring agency output aligns with Mixpanel's voice and goals
Internal communications:
- Partner with the People team and leadership to craft internal announcements and other types of internal messaging
- Support the development of internal communication programs that keep employees informed and connected to the company's narrative
Crisis & issues management:
- Monitor the media and competitive landscape for potential reputational issues
- Support the development of crisis communications protocols and serve as a strategic voice in sensitive situations
Executive communications:
- Identify, pursue, and manage award submissions, podcast appearances, and speaking opportunities at key industry conferences and events
- Develop and maintain LinkedIn content strategies for executives, helping amplify their voice and build their professional presence
- Collaborate with executives on bylines and contributed articles, from ideation through to final draft
- Develop and execute broader thought leadership narratives and plans for executives and the company
We'll create li for each category, with subpoints as separate sentences.
Now Requirements: We'll extract mandatory qualifications.
The block: "7+ years of communications experience, with a strong preference for candidates who have worked both in-house at a B2B tech company and at a PR agencyExperience in one or more of the following spaces: analytics, data, AI, engineering, product development. You understand the audience and know how to translate technical concepts into stories that resonate.Exceptional writer and editor across formats: press releases, media pitches, executive messaging, bylines, internal announcements, and social contentStrong verbal communicator with confidence presenting to and advising senior stakeholdersStrong storytelling skills and news judgmentA track record of securing meaningful coverage in top-tier and tech outlets Experience managing external agencies and partners and working cross-functionally with various internal partnersComfortable working independently in an ambiguous, fast-moving environment — this is a building roleExperience working with PR agencies or teams outside of the United StatesJournalism training or prior experience as a reporter/editor is a genuine plus"
We need to split into sensible list items. Let's parse:
- 7+ years
- for any list of duties/requirements/benefits. It doesn't forbid nested lists? Could do nested
- for lists.
We need to preserve all substantive info; do not invent or summarize away detail. So we must include all details from each section.
Let's craft each.
About the role: The paragraph under "About The Role". It includes multiple sentences. We'll put as
- for any list of duties/requirements/benefits. So we can flatten.
We need to preserve all substantive info. So each bullet should contain the text from each responsibility section.
Let's extract:
Media relations:
- Cultivate and maintain relationships with journalists, editors, and producers covering enterprise tech, analytics, AI, data, and SaaS
- Drive earned media coverage in top-tier business and trade outlets
- Develop compelling story angles, press materials, pitches, and messaging frameworks
- Serve as a primary media contact and help prepare spokespeople for interviews and public presentations
- Establish and track metrics to monitor the health of Mixpanel’s coverage
Product Launches & Company News:
- Partner closely with Product Marketing to develop and execute PR strategies for major product announcements
- Manage PR and comms activities for company news and announcements
- Ensure messaging is consistent, differentiated, and resonant with technical and business audiences
Agency & partner management:
- Manage agency relationships in the US, EMEA, and APAC, setting clear priorities, KPIs, and workflows
- Serve as the internal contact and day-to-day liaison, ensuring agency output aligns with Mixpanel's voice and goals
Internal communications:
- Partner with the People team and leadership to craft internal announcements and other types of internal messaging
- Support the development of internal communication programs that keep employees informed and connected to the company's narrative
Crisis & issues management:
- Monitor the media and competitive landscape for potential reputational issues
- Support the development of crisis communications protocols and serve as a strategic voice in sensitive situations
Executive communications:
- Identify, pursue, and manage award submissions, podcast appearances, and speaking opportunities at key industry conferences and events
- Develop and maintain LinkedIn content strategies for executives, helping amplify their voice and build their professional presence
- Collaborate with executives on bylines and contributed articles, from ideation through to final draft
- Develop and execute broader thought leadership narratives and plans for executives and the company
Now Requirements/Qualifications/Skills: The posting has "We're Looking For Someone Who Has" list. That includes experience requirements etc. Also "Bonus Points For". So we can combine into Requirements (maybe Qualifications) and Skills. The instruction: Use headings for About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content.
We have content for Requirements: "7+ years of communications experience, with a strong preference for candidates who have worked both in-house at a B2B tech company and at a PR agencyExperience in one or more of the following spaces: analytics, data, AI, engineering, product development. You understand the audience and know how to translate technical concepts into stories that resonate.Exceptional writer and editor across formats: press releases, media pitches, executive messaging, bylines, internal announcements, and social contentStrong verbal communicator with confidence presenting to and advising senior stakeholdersStrong storytelling skills and news judgmentA track record of securing meaningful coverage in top-tier and tech outlets Experience managing external agencies and partners and working cross-functionally with various internal partnersComfortable working independently in an ambiguous, fast-moving environment — this is a building roleExperience working with PR agencies or teams outside of the United StatesJournalism training or prior experience as a reporter/editor is a genuine plus"
That's a block of text; we can split into list items.
Also "Bonus Points For" list: Familiarity with analyst relations (Gartner, Forrester, IDC) in a B2B SaaS contextExperience supporting a company through a major growth phase, rebrand, or category creation momentExperience working as a PR team of oneExisting relationships with reporters covering enterprise software, product management, data infrastructure, analytics, and/or AI
We could treat these as additional qualifications/skills. Could put under Requirements or Skills. Since we have both Requirements and Skills headings possible, we could put the core requirements under Requirements, and bonus points under Skills. Or combine.
Better: Requirements: the mandatory qualifications. Skills: the bonus points and maybe skill-based items like exceptional writer, etc. But the instruction: Prefer a few substantive sections over many thin ones. So maybe we just have Requirements (including both mandatory and bonus) and maybe Skills not needed. But we need to follow instruction: include a section ONLY when posting has real, specific content for it. So we can include Requirements and Skills if we have distinct content.
We have mandatory qualifications list; we also have skill-based items like exceptional writer, strong verbal communicator, storytelling skills, news judgment, track record, managing agencies, comfortable working independently, experience with non-US PR agencies, journalism training plus. Those could be considered skills. Bonus points are extra.
Thus we can have Requirements (mandatory experience) and Skills (writer, communicator, etc.) and maybe Bonus under Skills as well.
But to avoid too many sections, we could combine Requirements and Skills into one "Requirements" section that includes all. However the instruction says we can use those headings; not required to use all. So we can just have Requirements section with all qualification content. That would be substantive.
Benefits: The posting has "Benefits And Perks" list: Comprehensive Medical, Vision, and Dental Care, Mental Wellness Benefit, Generous Vacation Policy & Additional Company Holidays, Enhanced Parental Leave, Volunteer Time Off, Additional US Benefits: Pre-Tax Benefits including 401(K), Wellness Benefit, Holiday Break. Also note about contract positions varies (but we can ignore). So we have benefits content.
Pay: The posting has "Compensation" section with salary range $174,500 - $236,000 USD, plus equity, etc. So we have Pay content.
Schedule: The posting mentions "This role requires two days per week in our San Francisco or New York office." That's schedule info (hybrid). So we can include Schedule.
Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule.
We should not include Qualifications or Skills separately if we merged into Requirements.
Now we need to output HTML fragment only, no or . Use
- . Possibly we could keep subheadings inside li? But instructions: Use