Senior Demand Generation Manager

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We need to parse the job posting. Key sections: - About the role: description of role, market, responsibilities? The posting includes "Most demand generation roles hand you a channel..." then description of role, what you'll be doing. That could be "About the role" or "Responsibilities". We need to decide. We have sections: "What you'll be doing" (list of duties). That's responsibilities. We have "What we're looking for" (requirements/qualifications/skills). That includes experience, etc. We have "Strong signals" (additional preferred qualifications). Could be part of qualifications. We have "Who does well here" (cultural fit). Could be part of qualifications or separate. We have "Why Resonate" (company description). Could be "About the company" but not required heading; we could put under "About the role"? Actually "Why Resonate" is about company; could be omitted if not needed but we can include as "About the company" but not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these. We have Pay: base salary range $120k-$140k, bonus program. We have Benefits: list of benefits. We have Schedule: maybe remote-first, travel 15% etc. Could be schedule. We have Location: remote-first, offices. Could be schedule? Not exactly. But we could put location under Schedule? Might be better to include as part of "About the role"? But we need to follow allowed headings. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can only use those headings. We need to include sections only when posting has real specific content for it. Thus we need to decide which sections to include: - About the role: could contain overview of role, market, mission, etc. We have description at start: "Most demand generation roles hand you a channel... At Resonate, we help enterprise brands... you'd own the growth engine for yours end to end..." That's about the role. So we can put that in About the role. - Responsibilities: "What you'll be doing" list. - Requirements: maybe "What we're looking for" core requirements (5+ years experience, enterprise, marketing to marketers, track record, ABM experience, hands-on campaign building, Salesforce/HubSpot, copywriting, analytical skills, generative AI, bachelor's degree). That's requirements. - Qualifications: maybe "Strong signals" (additional preferred qualifications) like experience marketing into agencies, politics, advocacy, data/martech/adtech background, comfort with intent/firmographic data platforms, familiarity with Pardot, Asana, WordPress, Google Analytics. Could be qualifications. - Skills: maybe overlapping with requirements; but we could separate skills like copywriting, analytical, AI, etc. However we already have those in requirements. Could combine. But we need to avoid thin sections. Perhaps we put skills under Requirements or Qualifications. But we need to follow instruction: Prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one section? But we have separate headings allowed; we could choose to include only Requirements and maybe Skills if distinct. Let's see. We have "Who does well here" (cultural traits). Could be part of Requirements or Qualifications? Might be better as a separate section like "About the role"? Not exactly. Could be omitted if we think it's thin? It's substantive though. Could be placed under "Requirements" as "Ideal candidate traits". But we need to keep content. We have "Why Resonate" (company description). Could be part of "About the role"? Might be okay. We have "Compensation & Benefits": Pay and Benefits sections. We have "Location": remote-first, travel 15% etc. Could be Schedule? Not exactly. Could be part of "About the role"? Might be better to include as "Schedule" (remote-first, travel). But schedule usually refers to work hours, remote, travel. We'll put location/travel under Schedule. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Possibly Qualifications if we separate strong signals. But we can incorporate strong signals into Requirements as "Preferred qualifications". That keeps fewer sections. Thus we will have:

About the role

... overview ...

Responsibilities

• ... each duty ...

Requirements

• ... core requirements ...

Preferred qualifications: ... strong signals ...

Benefits

• ... benefits ...

Pay

Base salary range $120,000 to $140,000, plus annual bonus program tied to company performance.

Schedule

Remote-first environment with flexibility; approximately 15% travel for company and client events.

We need to ensure we preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO, legal, application instructions, cookie/navigation, duplicated lines. We must not repeat job title as heading. Not include Job ID. We must not create sections with filler like "commensurate with experience". We have actual content. We need to extract details precisely. Let's extract About the role content: From start: "Most demand generation roles hand you a channel and someone else's number. This one hands you a market. At Resonate, we help enterprise brands and agencies understand not just who their customers are, but why they behave the way they do, and what they'll do next. We run demand generation across three markets - brands, agencies, and politics and advocacy - and you'd own the growth engine for yours end to end: the strategy, the narrative, the program budget, and a quarterly pipeline target measured in ACV rather than lead volume. It's a business impact seat rather than a support one, and the people you're marketing to run campaigns for a living, which makes the job harder and a lot more interesting." That's the overview. We could also include "Why Resonate" but maybe not needed. Now Responsibilities: list from "What you'll be doing" bullet points (though not formatted as bullets in text). Let's parse: - Owning demand generation for your market - carrying a quarterly pipeline target measured in ACV rather than lead volume, and managing an allocated program budget across channels that you defend with conversion data - Translating company-wide go-to-market priorities into a demand strategy that actually fits your market - audience frameworks, key narratives, messaging, and nurture paths, built alongside Product Marketing and Content - Running integrated multi-channel campaigns end to end: planning, build, launch, measurement, and the honest follow-up conversation about what converted - Running account-based marketing against named target account lists and in-market accounts - mapping buying committees, reaching multiple buying teams inside large matrixed organizations, personalizing properly rather than at scale, and coordinating timing with BDR and Sales - Building and running always-on demand engines across the full buyer journey, from thought leadership, paid programs, and webinars through email and social to retargeting, ABM, and events, all laddering into one market narrative - Working with the Events Manager on which events are worth showing up to and what we're there to achieve, then making sure they produce meetings and pipeline rather than just presence - Owning funnel performance from ICP accounts showing intent through meetings, opportunities, and bookings - partnering with Marketing Ops on analytics, automation, segmentation, and lead flow, and delivering regular analysis on channel ROI with a clear recommendation attached We need to preserve each as

. Now Requirements: from "What we're looking for" paragraph: - You'll need 5+ years in B2B demand generation, growth, or marketing, aimed at enterprise buyers - Fortune 500 consumer brands or top-tier marketing agencies. Enterprise is the important word here: complex, matrixed buying decisions across a large organization rather than SMB - Experience marketing to marketers. Your buyers do this for a living, and they can tell within about ten seconds whether you understand their world - A track record of building data-driven demand programs that moved pipeline and revenue, not just top-of-funnel metrics - Account-based marketing experience against named account lists, with real personalization rather than personalization at scale - Hands-on campaign building and launching in B2B ad platforms such as LinkedIn, Meta, and Google Display - Salesforce or HubSpot. Salesforce is our stack, so if you've come up on HubSpot that's fine, you'll just be learning ours - Strong copywriting across email, landing pages, ad copy, and sales cadences - Strong analytical skills - you can work through a complex data set, find what's actually driving performance, and explain it simply. Comfortable in Excel with pivot tables and advanced functions - Generative AI in how you actually work. We're an AI-forward company and we use Claude, so bring examples of what you've built with these tools - projects, workflows you've automated, research or analysis you've reshaped - rather than prompts you've tried once - A bachelor's degree in marketing, communications, business, or a related field, or equivalent experience That's requirements. Now Strong signals (preferred qualifications): - Experience marketing or selling into agencies - Experience in politics, advocacy, or public affairs marketing - A background in data, martech, or adtech - Comfort with intent and firmographic data platforms such as ZoomInfo, Bombora, 6sense, or Demandbase, and the judgment to know which signals are worth acting on - Familiarity with Pardot, Asana, WordPress, and Google Analytics We can include as "Preferred qualifications" within Requirements section. Now Who does well here (cultural traits): - You like owning the whole thing. You want the market, the budget, and the number, and you're comfortable being the person who answers for all three. - You work on your own initiative, you see what's needed before someone asks, and you can hold several integrated programs in the air without dropping any of them. - You test, you read the data properly, and you're just as willing to say a program didn't work as you are to claim one that did. - You're a strong writer and a clear communicator, which matters here because you'll be aligning Product Marketing, Content, BDR, Sales, and events around one narrative without having authority over any of them. - And you're genuinely curious about the audience you're marketing to. We could incorporate into Requirements as "Ideal candidate traits" or maybe as a separate section but we want few sections. Could add to Requirements as bullet points. Now Why Resonate (company description) maybe not needed but could be part of About the role. However we already have About the role overview; we could add a paragraph about company: "Resonate is a leading provider of high-quality, AI-powered consumer data, intelligence, and technology, empowering marketers to create a more personalized world that increases customer acquisition and lifetime value. Our SaaS platform, Ignite, and our Data-as-a-Service (DaaS) offerings provide unparalleled insights into consumer motivations, values, and behaviors, enabling our clients to connect with their target audiences in more meaningful and effective ways. We are a dynamic and fast-growing company seeking passionate and innovative individuals to join our team!" plus Resonate Attributes list. That's a lot; but we need to preserve all substantive information. If we omit, we lose info. So we need to include that somewhere. Perhaps we can add a section "About the company" but not allowed heading. Could we put under