Product Marketing Manager

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. The posting includes: - About Improvado (company description) – not needed as heading? 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." The job title is not given explicitly but maybe "Product Marketing Manager" etc. Not needed. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to extract content for each. From posting: - "Why this role, now" – that's about the role context. Could be "About the role". We'll put that content. - "What you'll own" – responsibilities. - "What we're looking for" – requirements/qualifications/skills. - "How we measure success" – maybe part of responsibilities? Could be under "Responsibilities" or separate? But we only have limited sections. Could include under Responsibilities or maybe under "Qualifications"? Probably responsibilities. - "What We Offer" – benefits. - Pay and Schedule: Not explicitly mentioned. There's "Competitive compensation" but no specifics. The instruction: never create Pay/Schedule sections unless posting actually states them. It says "Competitive compensation" but not specific numbers or range. That's vague; maybe we should not create Pay section because it's not specific. Similarly schedule not mentioned (remote-first environment implies remote work but not schedule). So we omit Pay and Schedule sections. - Benefits: "Remote-first environment Competitive compensation Medical and dental benefits 401K plan Unlimited PTO Paid holidays Professional development reimbursement". That's specific enough for Benefits section. - Skills: maybe we can extract from "Nice to have" etc. But we need to decide if we have enough for Skills section. Could combine with Requirements/Qualifications. But we have separate sections; we can put skills under Skills if we have content. The posting includes: "Nice to have: hands-on SQL, dbt or BI, enough to validate a claim yourself. Experience marketing AI capabilities without hype. Analyst-relations experience. Agency-side or enterprise-brand background. Vertical depth in pharma and healthcare, financial services, retail and eCommerce, or gaming." Also earlier: "Category fluency in marketing data and measurement: attribution models, incrementality testing, MMM, data governance and taxonomy, warehouses and ETL/ELT — including where each is honestly weak". Also "Proof you have shipped, not just documented: positioning that changed the website and the pitch, battlecards reps actually opened, a win/loss program that survived past its second quarter". Also "Writing that survives contact with a skeptical technical buyer — claim and evidence, not adjective stacking". Also "Comfort operating close to Sales: weekly cadence, deal reviews, live calls, direct feedback". Those are skills/qualifications. We can split: Requirements (maybe years experience, category fluency), Qualifications (proof you have shipped etc), Skills (nice to have). But we need to avoid duplication. Let's craft:

About the role

... content from "Why this role, now" paragraph.

Responsibilities

• ... from "What you'll own" bullet points.

Requirements

• ... from "What we're looking for" bullet points about experience, category fluency, B2B SaaS, etc.

Qualifications

• ... from proof you have shipped, writing, comfort operating close to Sales.

Skills

• ... from Nice to have items.

Benefits

• ... remote-first, competitive compensation, medical/dental, 401K, unlimited PTO, paid holidays, professional development reimbursement.

We should not include Pay or Schedule. Make sure we preserve all substantive information, not invent. Let's extract exact sentences. About the role: "Why this role, now Our messaging is not aligned. Positioning, web, sales pitch, product and content each carry a different version of what Improvado is. The market categorizes us as "marketing ETL" while we position as an AI marketing analytics platform. That gap costs us deal quality and priceThe category is crowded and moving fast. Battlecards exist but decay, and nobody owns keeping them trueAttribution, incrementality and causal measurement is where deals are won and lost — and it is the hardest thing to argue credibly without hand-wavingAnalyst firms are a silent blocker. When an enterprise buyer asks Gartner or Forrester about Improvado, there is no briefed narrative waiting for them You would not start from a blank page. We already have a positioning registry, roughly 11 documented buyer personas, a pain-point and value-prop library, competitor intel reports and about 10 battlecards. They are inconsistent and under-used. Your first job is to make one version true and make people use it." We need to keep it as prose

. Might need to fix missing spaces: there are some missing spaces after periods. We'll keep as is but maybe add spaces for readability? The instruction: preserve ALL substantive information; do not invent or summarize away detail. We can keep the text exactly as given, but we could add spaces where missing? That would be altering. Better to keep exactly as given, but it's hard to read. However we can keep as is; it's still the same characters. We'll output exactly. Responsibilities: "What you'll own Positioning and messaging. Core positioning, category framing and message hierarchy across ICPs and personas. ICP and persona documentation that is used, not filed. The messaging layer of new product and feature launches, including the internal rollout that makes the field able to sell itCompetitive intelligence and win/loss. A structured win/loss interview program with quarterly readouts. Living battlecards. Monitoring competitor positioning, pricing and product moves, and driving our counter-positioningSales enablement. The core pitch narrative, demo storyline and objection-handling framework. The messaging components of new-rep onboarding. A standing weekly cadence with Sales leadership — not quarterly check-ins. Direct support on competitive and enterprise deals: RFPs, security and technical evaluations, displacement playsMarket and analyst relations. The Improvado narrative for Gartner, Forrester and category influencers, so that a buyer's analyst call becomes an accelerator rather than a blocker. Feeding structured market and buyer insight back into product prioritization" We need to split into list items. Each sentence after a period maybe. We'll create

• for each distinct bullet. Let's parse: - Positioning and messaging. Core positioning, category framing and message hierarchy across ICPs and personas. - ICP and persona documentation that is used, not filed. - The messaging layer of new product and feature launches, including the internal rollout that makes the field able to sell it - Competitive intelligence and win/loss. A structured win/loss interview program with quarterly readouts. Living battlecards. Monitoring competitor positioning, pricing and product moves, and driving our counter-positioning - Sales enablement. The core pitch narrative, demo storyline and objection-handling framework. The messaging components of new-rep onboarding. A standing weekly cadence with Sales leadership — not quarterly check-ins. Direct support on competitive and enterprise deals: RFPs, security and technical evaluations, displacement plays - Market and analyst relations. The Improvado narrative for Gartner, Forrester and category influencers, so that a buyer's analyst call becomes an accelerator rather than a blocker. Feeding structured market and buyer insight back into product prioritization We could break further but okay. Requirements: "What we're looking for 4 to 8 years in product marketing, or an equivalent blend of product marketing with marketing analytics, marketing or data ops, sales engineering, analytics consulting, or product management on a data productCategory fluency in marketing data and measurement: attribution models, incrementality testing, MMM, data governance and taxonomy, warehouses and ETL/ELT — including where each is honestly weakB2B SaaS sold to marketing or data buyers. Marketing analytics, martech, measurement, CDP, BI and data-infrastructure vendors are the reference profileProof you have shipped, not just documented: positioning that changed the website and the pitch, battlecards reps actually opened, a win/loss program that survived past its second quarterWriting that survives contact with a skeptical technical buyer — claim and evidence, not adjective stackingComfort operating close to Sales: weekly cadence, deal reviews, live calls, direct feedback Nice to have: hands-on SQL, dbt or BI, enough to validate a claim yourself. Experience marketing AI capabilities without hype. Analyst-relations experience. Agency-side or enterprise-brand background. Vertical depth in pharma and healthcare, financial services, retail and eCommerce, or gaming. Not a fit if: your product marketing has been mostly launch logistics and content calendars; you need a fully staffed team and a finished brand system to be effective; you are uncomfortable being told in a deal review that your messaging did not work." We need to separate Requirements, Qualifications, Skills, maybe also "Not a fit if" could be part of Requirements? But we can keep as part of Requirements. Let's define: Requirements: core experience: 4-8 years product marketing etc, category fluency, B2B SaaS sold to marketing/data buyers. Qualifications: proof you have shipped, writing that survives contact, comfort operating close to Sales. Skills: Nice to have items. Not a fit if: maybe we can include under Requirements as disqualifiers. We'll create sections accordingly. Benefits: "What We Offer Remote-first environment Competitive compensation Medical and dental benefits 401K plan Unlimited PTOPaid holidays Professional development reimbursement Powered by JazzHR GrnM3lxGhR" We need to remove boilerplate like "Powered by JazzHR GrnM3lxGhR" maybe it's metadata; we can drop minor metadata. Keep benefits list. Let's craft HTML. We'll output:

  About the role

  Why this role, now Our messaging is not aligned. Positioning, web, sales pitch, product and content each carry a different version of what Improvado is. The market categorizes us as "marketing ETL" while we position as an AI marketing analytics platform. That gap costs us deal quality and priceThe category is crowded and moving fast. Battlecards exist but decay, and nobody owns keeping them trueAttribution, incrementality and causal measurement is where deals are won and lost — and it is the hardest thing to argue credibly without hand-wavingAnalyst firms are a silent blocker. When an enterprise buyer asks Gartner or Forrester about Improvado, there is no briefed narrative waiting for them You would not start from a blank page. We already have a positioning registry, roughly 11 documented buyer personas, a pain-point and value-prop library, competitor intel reports and about 10 battlecards. They are inconsistent and under-used. Your first job is to make one version true and make people use it.

  Responsibilities

  • Positioning and messaging. Core positioning, category framing and message hierarchy across ICPs and personas.
  • ICP and persona documentation that is used, not filed.
  • The messaging layer of new product and feature launches, including the internal rollout that makes the field able to sell it
  • Competitive intelligence and win/loss. A structured win/loss interview program with quarterly readouts. Living battlecards. Monitoring competitor positioning, pricing and product moves, and driving our counter-positioning
  • Sales enablement. The core pitch narrative, demo storyline and objection-handling framework