Senior Product Marketing Manager

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID/req numbers as headings; can fold minor metadata into short

or drop it. We need to parse the posting. Content: - Responsibilities: a block describing responsibilities, with bullet-like sentences. We'll need to put into

• for any list of duties/requirements/benefits. The responsibilities are prose but could be turned into list items. The instruction: Use
  • for any list of duties/requirements/benefits, and

    for prose. So we need to decide: responsibilities likely a list of duties; we can format each duty as

  • . The text includes sentences separated by periods. We can split into list items. - Education / Qualifications: includes bullet-like items: bachelor's degree, 5+ years, track record, sharp written and verbal communication, comfort working with global teams, ability to read marketing and business data, hands-on experience with Salesforce and a marketing automation platform. Also bonus points: direct experience marketing to asset-intensive industries, working knowledge of EAM/APM etc. Those could be qualifications/requirements/skills. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role? The posting includes "About Octave" repeated twice, and "Why work for Octave?" Also "Senior Product Marketing Manager Job Location (Short): Houston, United States | Madison, United States Workplace Type: Remote". That could be About the role? Actually "About the role" could be description of role and team. The first paragraph: "We’re hiring a Senior Program Manager to drive marketing for Octave Attune..." That's about the role. Also later "You’ll sit on the Global Portfolio Marketing team..." That's also role. So we can put that in About the role section. Responsibilities: we have "What You’ll Do:" list. Requirements: maybe education/qualifications? Could split: Requirements (hard requirements) and Qualifications (preferred). But we can combine? The instruction: prefer a few substantive sections over many thin ones. We could have About the role, Responsibilities, Requirements (including education, experience, skills), and maybe Benefits? There's no explicit benefits, pay, schedule. So we should not create those sections unless posting actually states them. There's no mention of benefits, pay, schedule. So we omit those sections. We also have "About Octave" and "Why work for Octave?" That's company info, not role. Could be part of About the role? Might be separate "About the company". But we only have allowed headings list; we could put that under About the role? Might be okay. Or we could create a section "About Octave" but not in allowed list; we must only use those headings. So we should incorporate that info into About the role or maybe omit? The instruction: "Prefer a few substantive sections over many thin ones." We could include About the role containing role description and company overview. That seems fine. We must not repeat job title as heading. So no

    Senior Program Manager. We must not put Job ID/requisition numbers as headings; we can drop them. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from responsibilities, qualifications, etc. We need to format lists with

    • . For prose, use

      . Let's extract sections: About the role: combine initial description and maybe "You’ll sit on the Global Portfolio Marketing team..." plus maybe "About Octave" and "Why work for Octave?" but that's company info; still substantive. We'll include as prose paragraphs. Responsibilities: list items from "What You’ll Do:" plus earlier responsibilities sentences before that? The earlier paragraph: "Your job is to make sure those operators... You’ll sit on the Global Portfolio Marketing team and own the conception, planning and execution of marketing programs for Octave Attune. You’ll partner with product management, solution design, demand generation, regional marketing and sales to set priorities, build go-to-market plans and run programs from kickoff to results." Those are also responsibilities. We'll include them as list items. Requirements/Qualifications/Skills: We have education/qualifications bullet list and bonus points. Could split into Requirements (hard) and Skills (preferred). But we can combine into one section "Requirements" containing all. However we have separate headings allowed: Requirements, Qualifications, Skills. To avoid thin sections, we could combine into Requirements (hard) and Skills (bonus). But we need to decide based on content. Let's identify hard requirements: bachelor's degree in marketing or related field; 5+ years in B2B marketing, product marketing or product management, ideally for software or technology; track record of running multi-channel marketing programs from strategy through execution, on a deadline, with multiple stakeholders pulling in different directions; sharp written and verbal communication; comfort working with global teams across regions and time zones, inside a large organization; ability to read marketing and business data, find the insight and act on it; hands-on experience with Salesforce and a marketing automation platform. Bonus points (preferred): direct experience marketing to asset-intensive industries; working knowledge of enterprise asset management, asset performance management, reliability or maintenance software categories. We could put hard requirements under "Requirements" and bonus under "Skills". Or we could put all under "Qualifications". But we need to follow instruction: prefer few substantive sections over many thin ones. Having two sections (Requirements and Skills) is okay. Could also have just "Requirements" containing both hard and bonus, but then we lose distinction but still fine. However we have headings for Qualifications and Skills; we could use them if we have content. Let's make: - Requirements: hard requirements (education, experience, track record, communication, global team comfort, data ability, Salesforce/MA experience) - Skills: bonus points (direct experience marketing to asset-intensive industries, working knowledge of EAM/APM etc.) We also might have a "Qualifications" section but we can skip if we think it's thin. But we have content for both Requirements and Skills; that's two sections. We also need to include location and workplace type? That's minor metadata; we can fold into a short

      maybe under About the role or drop. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

      or drop it. So location and workplace type is minor metadata; we can include a short paragraph under About the role or maybe after responsibilities. We'll include a

      with location and remote info. We must not include repetitive boilerplate like "Everyone is welcome..." etc. That's EEO/equal-opportunity boilerplate; we should remove it. The posting includes that repeated twice. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out the "Everyone is welcome..." paragraphs. Also remove duplicated "About Octave" and "Why work for Octave?" maybe keep one copy? The instruction: remove duplicated lines. So we should keep only one instance of each distinct substantive block. The posting has "About Octave" repeated twice, and "Why work for Octave?" repeated twice. We'll keep one each. Thus final HTML:

      About the role

      We’re hiring a Senior Program Manager to drive marketing for Octave Attune — Octave’s EAM and APM solutions for asset-intensive industries. The people you’re marketing to are running plants, fleets and facilities where uptime, reliability and safety aren’t talking points. They’re the business. Your job is to make sure those operators, maintenance leaders and reliability engineers see Octave as the partner that gets it. You’ll sit on the Global Portfolio Marketing team and own the conception, planning and execution of marketing programs for Octave Attune. You’ll partner with product management, solution design, demand generation, regional marketing and sales to set priorities, build go-to-market plans and run programs from kickoff to results. Senior Product Marketing Manager Job Location (Short): Houston, United States | Madison, United States Workplace Type: Remote

      But we should not repeat job title as heading; but we can include job title in prose? It's okay. The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid mentioning it in prose. So we can keep. But we might want to avoid repeating "Senior Product Marketing Manager" twice? It's okay. Now Responsibilities:

      Responsibilities

      • Build the marketing strategy for Octave Attune, translating product capabilities and customer pain points into messaging, positioning and value propositions that hold up in front of plant managers, reliability engineers, maintenance leaders and the executives who fund their work.
      • Plan and execute integrated campaigns across email, social, video, webinars and live and virtual events — covering net-new pipeline, customer expansion and product launches.
      • Develop go-to-market packages for new releases and major campaigns: launch narratives, sales talk tracks, customer-facing collateral, web copy, blog posts, case studies and analyst briefings.
      • Partner with the enablement team to equip sales, pre-sales and ADRs with the materials and product context they need to have substantive conversations with asset-intensive buyers.
      • Tap internal SMEs, external consultants and customer references to ground every asset in real industry context.
      • Track program performance against pipeline, engagement and revenue metrics, then bring sharp recommendations on what to double down on and what to stop.
      • Coordinate across key stakeholders to keep messaging consistent and execution aligned across regions and channels.
      Now Requirements:

      Requirements

      • A bachelor’s degree in marketing or a related field.
      • 5+ years in B2B marketing, product marketing or product management, ideally for software or technology.
      • A track record of running multi-channel marketing programs from strategy through execution, on a deadline, with multiple stakeholders pulling in different directions.
      • Sharp written and verbal communication.
      • Comfort working with global teams across regions and time zones, inside a large organization.
      • The ability to read marketing and business data, find the insight and act on it.
      • Hands-on experience with Salesforce and a marketing automation platform.
      Now Skills:

      Skills

      • Direct experience marketing to asset-intensive industries: oil and gas, power and utilities, manufacturing, mining, chemicals or transportation.
      • Working knowledge of enterprise asset management, asset performance management, reliability or maintenance software categories.
      We should not include Benefits, Pay, Schedule sections as they are not present. We must ensure no extra whitespace or markdown. Output only HTML fragment. Check for any leftover boilerplate: we removed EEO paragraphs. Also removed duplicated "About Octave" and "Why work for Octave?" We kept one each? Actually we didn't include any "About Octave" or "Why work for Octave?" in About the role section; we only included the role description. Should we include company info? It's substantive but not role. However we might need to include it somewhere; but we have no heading for company. Could we include it under About the role as extra paragraph? It's about the company, not the role, but still relevant. The instruction: "Prefer a few substantive sections over many thin ones." We could add a paragraph about Octave and why work for Octave under About the role. That would be substantive and not thin. Let's do that. Add after the role description a paragraph: "Octave provides mission-critical software that empowers organizations to make informed decisions across every stage of the asset lifecycle - Design, Build, Operate and Protect