Director of Product Marketing
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No Job ID etc. Remove boilerplate. Must preserve all substantive info.
We need to parse the posting: It includes "Who We Are" (company description) - maybe not a required heading; but we can include as a section? The instruction says use headings for those specific headings; but we can also include other sections? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but likely we should stick to those. However we have "Who We Are" content; maybe we can put that under About the role? Actually "About The Role" is a heading present. We'll use that.
We need sections: About the role (description of role), Responsibilities (what you'll do), Requirements (what we're looking for), Qualifications maybe same as requirements? Could combine. Skills maybe part of requirements. Benefits: we have benefits listed under "Why You Will Flourish With Us". Pay: not specified. Schedule: not specified. So we should not include Pay or Schedule sections because no specific content.
We need to include Benefits section with the listed benefits.
We need to ensure we don't include filler like "commensurate with experience". Not present.
We need to preserve all substantive info: company description, role description, responsibilities bullet list, requirements bullet list, benefits bullet list.
We must not include application instructions, EEO, legal, etc. There's none.
We need to format using for each section heading, then content: either
for each section heading, then content: either
for prose,
- for lists.
We must not repeat job title. The job title is "Director of Product Marketing". Not to be used as heading.
We'll produce something like:
About the role
Heidi is building a platform of clinical AI tools designed to support clinicians across their workflows, and we’re looking for a Director of Product Marketing to shape how those products are positioned, launched, and brought to market. You’ll own positioning, messaging, go-to-market strategy, and sales enablement across Heidi’s most important products and launches. You’ll work closely with Product, Sales, and Marketing to understand what we’re building, what customers care about, and what wins in the market. This is a senior individual contributor role for someone equally comfortable setting the strategy and executing it. You’ll bring a strong point of view while staying hands-on enough to talk to customers, write the messaging, build a launch plan, or sharpen the story for an important sales opportunity. Your mandate: make Heidi’s products successful in the market – from how we position and launch them to how we help Sales win.
Then Responsibilities: we have "What you'll do" with bullet points. We'll extract each bullet as - . The bullet list includes: - Own positioning and messaging - Own positioning and messaging across Heidi’s product suite, defining what each product does, who it’s for, the problem it solves, and why it wins. - Build messaging for Heidi’s key audiences, from clinicians to clinical, operational, IT, and executive buyers. - Turn product capabilities, customer outcomes, and competitive differentiation into messaging used across campaigns, launches, sales materials, demos, and the website. - Lead product go-to-market - Own GTM strategy for major product launches, including target audience, positioning, launch plan, sales readiness, adoption, and measures of success. - Partner with Product early to bring customer, competitive, and commercial insight into what we build, who we build it for, and how we bring it to market. - Drive cross-functional launch execution and use adoption, customer feedback, and commercial performance to inform what comes next. - Own customer and market intelligence - Build a strong point of view on Heidi’s customers, buyers, competitors, and the clinical AI market. - Own customer research, win/loss analysis, and competitive intelligence, including competitive positioning and battlecards. - Turn those insights into recommendations that shape product, positioning, and GTM strategy. - Help Sales win - Own the core product marketing materials Sales needs to sell Heidi, including pitch decks, product collateral, solution briefs, and demo narratives. - Stay close to the field to understand what resonates, where deals get stuck, and what buyers need to believe to choose Heidi. - Turn customer outcomes into credible proof, including case studies, ROI stories, references, and validated proof points. - Support strategic deals with tailored messaging, competitive positioning, and objection handling. We can flatten or keep nested? Probably just a flat list of responsibilities; but we can keep sub-bullets as separate
- items.
We'll produce
- ... etc.
Then Requirements/Qualifications/Skills: The posting has "What we're looking for" with bullet points:
- 7+ years of product marketing experience, ideally in B2B SaaS, AI, healthcare, or another complex technology category.
- A track record of independently owning positioning, messaging, and go-to-market strategy from development through execution.
- Experience working closely with Product and Sales to launch products, influence product strategy, and support complex sales motions.
- Exceptional writing and storytelling skills, with the ability to make complex products clear, differentiated, and compelling.
- Strong customer and commercial instincts, with experience using customer research, market insights, and performance data to make decisions.
- Comfortable operating as a senior IC: setting direction, influencing across teams, and producing the work yourself.
- Comfortable moving quickly, making decisions with imperfect information, and operating in a high-growth environment.
- Bonus points:
- Experience in healthcare, health tech, or clinical software.
- Experience bringing AI products to market.
- Experience selling into health systems or other complex enterprise organizations.
We could separate Requirements (mandatory) and Skills (maybe the exceptional writing etc). But we can combine into Requirements and Skills sections. However we need to avoid thin sections. Perhaps we make one "Requirements" section containing all mandatory and bonus as separate lists? Or we could have "Requirements" for mandatory, "Skills" for exceptional writing etc, and "Qualifications" maybe not needed. But we must only include sections when there is real specific content. We have content for Requirements, Skills, maybe Qualifications (could be same as Requirements). To avoid duplication, we can make Requirements (mandatory), Skills (exceptional writing etc), and Qualifications (maybe combine with Requirements). But we risk thin sections. Let's think: The instruction says prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Skills into one section "Requirements". But they asked to use headings for those specific headings; we can still include them but if content is thin we should avoid. So we need to decide.
We have a lot of content for requirements/skills; we could put all under "Requirements". Then we could omit Skills and Qualifications sections. That would be fewer sections.
But the instruction says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we must use all; just that if we use a heading, it should be one of those. So we can choose to include only About the role, Responsibilities, Requirements, Benefits. That seems fine.
We need Benefits: list from "Why You Will Flourish With Us":
- Generous Healthcare, Dental, and Vision benefit options 90%+ paid for by Heidi
- 401k with 3% match
- $100/month Healthy Heidis budget
- $700/year learning & development budget
- Recharge Days after major pushes
- The rare chance to create a global impact as you immerse yourself in one of the leading healthtech startups
We'll put those as
- .
We must not include Pay or Schedule sections because no specific content.
We also need to include the "Who We Are" description? It's not under a heading; maybe we can include it as a preamble before About the role? The instruction says 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 descriptive paragraphs before headings. We could include a brief intro about the company as a
before the first heading. That would preserve substantive info. However the "Who We Are" is quite long; we could include it as a
before About the role. But we need to ensure we don't inadvertently create a heading for it. We'll just put it as a
before the first
. Thus final HTML:
Who We Are Healthcare needs a better rhythm: one that keeps care continuous and deeply human. Heidi is building an AI Care Partner that works alongside clinicians to make that possible. We’re a team of doctors, engineers, designers, researchers, and creatives building tools that help clinicians stay focused on what matters most: their patients. In just 18 months, Heidi has given back more than 18 million hours to healthcare professionals — supporting 73 million patient visits in 116 countries. Today, more than two million patient visits each week are powered by Heidi worldwide. Backed by nearly $100 million in funding, we’re growing in the US, UK, Canada, and Europe, partnering with leading health systems including the NHS, Beth Israel Lahey Health, and Monash Health.
About the role
Heidi is building a platform of clinical AI tools designed to support clinicians across their workflows, and we’re looking for a Director of Product Marketing to shape how those products are positioned, launched, and brought to market. You’ll own positioning, messaging, go-to-market strategy, and sales enablement across Heidi’s most important products and launches. You’ll work closely with Product, Sales, and Marketing to understand what we’re building, what customers care about, and what wins in the market. This is a senior individual contributor role for someone equally comfortable setting the strategy and executing it. You’ll bring a strong point of view while staying hands-on enough to talk to customers, write the messaging, build a launch plan, or sharpen the story for an important sales opportunity. Your mandate: make Heidi’s products successful in the market – from how we position and launch them to how we help Sales win.
Responsibilities
- Own positioning and messaging across Heidi’s product suite, defining what each product does, who it’s for, the problem it solves, and why it wins.
- Build messaging for Heidi’s key audiences, from clinicians to clinical, operational, IT, and executive buyers.
- Turn product capabilities, customer outcomes, and competitive differentiation into messaging used across campaigns, launches, sales materials, demos, and the website.
- Own GTM strategy for major product launches, including target audience, positioning, launch plan, sales readiness, adoption, and measures of success.
- Partner with Product early to bring customer, competitive, and commercial insight into what we build, who we build it for, and how we bring it to market.
- Drive cross-functional launch execution and use adoption, customer feedback, and commercial performance to inform what comes next.
- Build a strong point of view on Heidi’s customers, buyers, competitors, and the clinical AI market.
- Own customer research, win/loss analysis, and competitive intelligence, including competitive positioning and battlecards.
- Turn those insights into recommendations that shape product, positioning, and GTM strategy.
- Own the core product marketing materials Sales needs to sell Heidi, including pitch decks, product collateral, solution briefs, and demo narratives.
- Stay close to the field to understand what resonates, where deals get stuck, and what buyers need to believe to choose Heidi.
- .
We must not include Pay or Schedule sections because no specific content.
We also need to include the "Who We Are" description? It's not under a heading; maybe we can include it as a preamble before About the role? The instruction says 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
- ... etc.
Then Requirements/Qualifications/Skills: The posting has "What we're looking for" with bullet points:
- 7+ years of product marketing experience, ideally in B2B SaaS, AI, healthcare, or another complex technology category.
- A track record of independently owning positioning, messaging, and go-to-market strategy from development through execution.
- Experience working closely with Product and Sales to launch products, influence product strategy, and support complex sales motions.
- Exceptional writing and storytelling skills, with the ability to make complex products clear, differentiated, and compelling.
- Strong customer and commercial instincts, with experience using customer research, market insights, and performance data to make decisions.
- Comfortable operating as a senior IC: setting direction, influencing across teams, and producing the work yourself.
- Comfortable moving quickly, making decisions with imperfect information, and operating in a high-growth environment.
- Bonus points:
- Experience in healthcare, health tech, or clinical software.
- Experience bringing AI products to market.
- Experience selling into health systems or other complex enterprise organizations.
We could separate Requirements (mandatory) and Skills (maybe the exceptional writing etc). But we can combine into Requirements and Skills sections. However we need to avoid thin sections. Perhaps we make one "Requirements" section containing all mandatory and bonus as separate lists? Or we could have "Requirements" for mandatory, "Skills" for exceptional writing etc, and "Qualifications" maybe not needed. But we must only include sections when there is real specific content. We have content for Requirements, Skills, maybe Qualifications (could be same as Requirements). To avoid duplication, we can make Requirements (mandatory), Skills (exceptional writing etc), and Qualifications (maybe combine with Requirements). But we risk thin sections. Let's think: The instruction says prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Skills into one section "Requirements". But they asked to use headings for those specific headings; we can still include them but if content is thin we should avoid. So we need to decide.
We have a lot of content for requirements/skills; we could put all under "Requirements". Then we could omit Skills and Qualifications sections. That would be fewer sections.
But the instruction says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we must use all; just that if we use a heading, it should be one of those. So we can choose to include only About the role, Responsibilities, Requirements, Benefits. That seems fine.
We need Benefits: list from "Why You Will Flourish With Us":
- Generous Healthcare, Dental, and Vision benefit options 90%+ paid for by Heidi
- 401k with 3% match
- $100/month Healthy Heidis budget
- $700/year learning & development budget
- Recharge Days after major pushes
- The rare chance to create a global impact as you immerse yourself in one of the leading healthtech startups
We'll put those as