Product Marketing Manager- Intelligence

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 must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove scam warning about recruitment scams? That's boilerplate; remove. We need to parse the posting. Let's extract sections: Position summary: description of role, responsibilities, etc. We'll need to break into sections: About the role (maybe summary), Responsibilities (what you own), Requirements (must have), Qualifications (maybe nice to have?), Skills (maybe AI tools etc), Benefits (what we offer), Pay (maybe not specified? It says "Market competitive pay leveraging Carta data" - that's pay info, so we can include Pay section with that line). Schedule: maybe not specified; there is Unlimited PTO etc but that's benefits. No explicit schedule like full-time, remote etc. Not given, so we should not create Schedule section if no specific content. We need to avoid filler like "commensurate with experience". Not present. We need to include all substantive info. Let's extract: About the role: The position summary paragraph(s) describing role: "Momentum and Insights are where our AI strategy meets the person actually doing the fundraising, and this role owns how that story reaches the market. Momentum helps gift officers spend their time on relationships instead of data entry. Insights bring wealth, demographic, and prospect signals into the work. Together they're becoming the system of intelligence for fundraising teams, and this bundle is one of the most important revenue bets we have. This Product Manager owns why we built it. You own why it matters to the market, and you drive the campaign and pipeline motion that turns that story into bookings. This is a front-of-house role, not a back-office one. You're not the person maintaining a positioning wiki or writing internal docs; that's the PM's job. You're the person who can stand in front of a CAO or VP of Advancement and make the case, who builds the campaign that fills the pipeline, and who's in the room with Sales when a deal needs a push. You're half product marketer, half marketing manager: product-fluent enough to be credible, commercially wired enough to own a number." Also "How this differs from the Product Manager" etc. Could be part of responsibilities. Responsibilities: "What you own" bullet list: Go-to-market strategy for the surface. You define positioning, messaging, and the market narrative for Momentum and Insights, translating what the PM and engineering ship into a story that lands with CAOs, VPs of Advancement, and gift officers. The pipeline number. You own the S2 pipeline goal for the unit alongside Demand, and you're accountable for it, not just a contributor to someone else's report. If pipeline is short, that's yours to diagnose and fix. Campaign strategy. In partnership with Demand, you bring the audience, the message, and the campaign brief. The Demand team brings channel expertise and executes. You need to know which lever to pull and hold the plan accountable to the number. The bookings motion. In partnership with Sales, you work with the field team to understand what's landing and build what they need next: competitive positioning, objection handling, proof points, and pricing narrative. Launches. When Momentum or Insights ships something that matters to the market, you own the go-to-market plan for it: audience, message, channel plan, and how Sales talks about it. Market and competitive intelligence. You track how Momentum and Insights are positioned against competitors, and you make sure that intelligence shapes campaigns and sales conversations. Collaboration across PMMs. You stay connected to the other product-line PMMs so positioning stays coherent across Virtuous, and the work doesn't fragment. Also "How you work": Front of house by instinct. You'd rather be in the room with a prospect or customer than writing the deck about the room. Commercially minded. You think in pipeline, attach, win rate, and bookings, not just launches shipped. AI-forward operator. You use AI tools as a default part of research, content development, and campaign build. Partnership without authority. You don't own Demand's channels or Sales's quota, and you get results anyway by bringing them a plan worth executing. Product-fluent, not product-owning. You go deep enough to be credible, but you're not writing requirements or making roadmap calls. These could be responsibilities or qualifications. We'll treat them as responsibilities. Requirements: "You Must Have" bullet list: 5+ years in product marketing, field marketing, or a hybrid GTM role at a B2B SaaS company, with real accountability for pipeline or bookings. Experience owning go-to-market strategy end to end: positioning, messaging, campaign strategy, and sales enablement. Comfort partnering with a channel-execution team (paid, SDR, field, email, direct mail) without running those channels yourself. A track record of being in front of prospects, customers, or analysts, not just writing about them. Strong written and verbal communication skills; ability to brief a sales team and interface with executive leadership. Fluency with AI tools as part of your everyday research, positioning, and content workflow. Comfort with ambiguity and a lean team; you'll build some of this function as you go. Nice to have: Experience in nonprofit tech, higher ed, or relational verticals; marketing a multi-product platform; or building a PMM function from scratch. Skills: Could include AI tools fluency, communication, etc. But we already have them in requirements; maybe we can put Skills as a separate section summarizing key skills: product marketing, GTM, AI tools, communication, etc. However we must not duplicate content? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. We can keep them in Requirements and Nice to have; we could also have Skills section but that would duplicate. Better to keep Requirements and Nice to have as separate sections? The allowed headings include Requirements, Qualifications, Skills. We could put "Requirements" for must-have, "Qualifications" for nice-to-have, and "Skills" maybe for specific skills like AI tools, communication. But we risk duplication. However we could keep Requirements as must-have, Qualifications as nice-to-have, and Skills maybe omitted if not distinct. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine Requirements and Qualifications into one "Requirements" section that includes both must-have and nice-to-have? But we need to preserve all info; we can include both under Requirements with sub-bullets? Could separate with headings inside? Not allowed; only headings are those specific. Could use

• for list; we could have two separate lists under same heading? Might be okay. But we need to follow the rule: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have multiple sections. We'll include About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Possibly Skills if we have distinct content not covered elsewhere. Let's see if we have distinct skills: "Fluency with AI tools as part of your everyday research, positioning, and content workflow." That's already in Requirements. "Strong written and verbal communication skills; ability to brief a sales team and interface with executive leadership." Also in Requirements. So Skills section would duplicate. Better to omit Skills. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Now Benefits: from "What we offer": Market competitive pay leveraging Carta data (but that's pay, we will put in Pay). Employee recognition through Bonusly (birthdays, anniversaries, achievements, etc.) 401(k) retirement plan with company matching- 50% match up to 6% of compensation after 90 days We value our employee’s work-life balance and encourage taking advantage of Unlimited PTO Supportive time off including paid volunteer days and company holidays Employer-contributed healthcare benefits, encompassing medical, dental, and vision coverage, with plans available for dependents and choices for Health Savings Accounts (HSA) and Flexible Spending Accounts (FSA). 12 weeks primary parent leave, 4 weeks secondary parent leave - full pay (adoption as well) We pride ourselves on Community and host exciting company outings and events. Thus Benefits section includes all except pay. Pay section includes "Market competitive pay leveraging Carta data". Also maybe mention that it's competitive. Now we need to ensure we don't include boilerplate like scam warning, EEO, etc. Remove that. Now produce HTML fragment. Structure:

  About the role

  ... (summary paragraph(s))

  Responsibilities

  • ...
  ...

  Requirements

  • 5+ years in product marketing, field marketing, or a hybrid GTM role at a B2B SaaS company, with real accountability for pipeline or bookings.
  • Experience owning go-to-market strategy end to end: positioning, messaging, campaign strategy, and sales enablement.
  • Comfort partnering with a channel-execution team (paid, SDR, field, email, direct mail) without running those channels yourself.
  • A track record of being in front of prospects, customers, or analysts, not just writing about them.
  • Strong written and verbal communication skills; ability to brief a sales team and interface with executive leadership.
  • Fluency with AI tools as part of your everyday research, positioning, and content workflow.
  • Comfort with ambiguity and a lean team; you'll build some of this function as you go.

  Qualifications

  • Experience in nonprofit tech, higher ed, or relational verticals.
  • Marketing a multi-product platform.
  • Building a PMM function from scratch.

  Benefits

  • Employee recognition through Bonusly (birthdays, anniversaries, achievements, etc.)
  • 401(k) retirement plan with company matching - 50% match up to 6% of compensation after 90 days
  • Unlimited PTO
  • Supportive time off including paid volunteer days and company holidays
  • Employer-contributed healthcare benefits, encompassing medical, dental, and vision coverage, with plans available for dependents and choices for Health Savings Accounts (HSA) and Flexible Spending Accounts (FSA)
  • 12 weeks primary parent leave, 4 weeks secondary parent leave - full pay (adoption as well)
  • Community and exciting company outings and events

  Pay

  Market competitive pay leveraging Carta data.

  We need to ensure we didn't miss any substantive info: The "About Us" paragraph about mission and values maybe could be part of About the role? It's about company. Could be included in About the role? The instruction: About the role heading for section headings (e.g. About the role, Responsibilities...). The "About Us" is not about the role but about company. Should we include it? It's substantive info about the company. Could be placed under About the role? Might be better to include as part of About the role? But the heading "About the role" suggests role description, not company. However we could still include company info under About the role? Might be misaligned. But we could create a separate section? Not allowed headings beyond those list. Could we put it under About the role as a paragraph? It's not about role but still could be included. The instruction: Use

  for section headings (e.g. About the role, Responsibilities