Demand Generation
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID etc. Remove boilerplate. Include only sections with real specific content. Avoid filler like "commensurate with experience". We need to parse the posting.
Company Overview: description of company. Could be "About the company" but not required heading? The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can include About the role (maybe overview of role). Responsibilities (What You'll Do). Requirements/Qualifications/Skills (Who You Are). Benefits (What We Offer). Pay and Schedule only if present. Pay: posting mentions "Competitive salary, comprehensive benefits, and meaningful equity". That's a statement about pay but not specific numbers. Should we include Pay section? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Competitive salary, comprehensive benefits, and meaningful equity". That's a statement about pay and benefits. Benefits we already have. Pay we could include but it's vague. The rule says avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". "Competitive salary" is vague but still a statement. Might be considered filler? It's not a specific number. The instruction: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". "Competitive salary" could be considered placeholder. Safer to omit Pay section. Schedule: not mentioned. So omit.
Thus sections: About the role (maybe Position Overview), Responsibilities (What You'll Do), Requirements (Who You Are), Benefits (What We Offer). Possibly Skills separate? Could combine Requirements and Skills. But we can have Requirements heading with list of qualifications. Skills maybe separate but we can incorporate.
We need to preserve all substantive information. Let's extract.
Company Overview: Not needed as heading? Could be part of About the role? But we can include a brief paragraph about company as part of About the role? The instruction: About the role heading for section headings (e.g. About the role, Responsibilities...). So we can put company overview under About the role? Might be better to have a short paragraph about the company under About the role heading. But the role overview is separate: "Position Overview We're hiring a senior individual contributor..." That's about role. So we can combine company overview and position overview under About the role? Might be okay.
But we need to preserve all substantive info: company overview details about Maven AGI, its AI agents, customers, results, founding, etc. That's substantive. Should be included. Where to put? Could be a preceding paragraph before headings? The instruction says output only HTML fragment, no extra. We can include a
for company overview before headings. That's allowed.
Then
About the role
with position overview paragraph.
Then Responsibilities
with - items from "What You'll Do". Need to capture each bullet.
Let's list responsibilities:
- Own the demand generation strategy and number: build and run multi-channel campaigns across inbound (paid ads, website conversion) and outbound (technographic targeting, sequences run with SDRs), with inbound as a primary driver of pipeline volume
- Partner with SDRs and AEs every day on campaign handoff, lead quality, and follow-through, with a tight feedback loop so what marketing sources actually converts
- Work hands-on in the platforms: own our lifecycle marketing program and performance marketing platforms, and be comfortable in Salesforce. You'll build the workflows, scoring, routing, and enrichment with your partners in GTM Systems
- Build and run ABM programs for strategic accounts: account selection and tiering, coordinated plays across paid, email, and outbound, and reporting on account-level engagement
- Work with field marketing on event strategy (conferences, dinners, sponsorships) and make sure field programs tie back to the same account and campaign framework as digital
- Define and own the metrics that matter (MQL-to-SQL conversion, pipeline sourced and influenced, CAC by channel, speed to lead) and build reporting that makes attribution something the team can trust
- Run a test-and-learn approach to new channels and formats, including AI-native and growth-style tactics (intent data, product signals, automated enrichment and personalization) where they fit our buyer
- Build the systems and playbooks that let demand generation scale without being rebuilt every quarter
We need to preserve all.
Now Requirements/Qualifications/Skills: "Who You Are" bullet list:
- 6+ years in demand generation, growth, or marketing operations at a B2B SaaS company, ideally including time at a startup or high-growth company
- You've built (not just run) a demand gen function or a major channel from the ground up, across both inbound and outbound
- Deep, hands-on platform experience: you've administered a marketing automation platform, built lead scoring and routing, and worked in tools like Clay without needing an ops team to do it for you
- Direct experience with SDR and AE teams: you've owned lead handoff, quality, and the feedback loop, rather than handing leads over a wall
- Comfortable in the data: you can pull your own reports, spot where the funnel is leaking, and explain it to sales leadership in plain terms
- Experience running ABM against a strategic or enterprise account list is a strong plus
- Bonus: experience marketing to technical or AI-forward buyers, or building GTM workflows that use AI and agentic tooling rather than just talking about it
Also "How You Show Up" values: customer champions, bold in action, data-driven and insight guided, stronger together. Those are cultural traits; could be included under Requirements or maybe separate section "Values". But not in prescribed headings. Could include under Requirements as part of "Who You Are". We'll keep as list items.
Now Benefits: "What We Offer" bullet list:
- 100% of medical, dental, and vision premiums covered for you, 80% for family
- HSA and FSA plans available
- Unlimited vacation and 100% paid parental leave
- Free lunches, onsite gym, and commuter benefits for in-office employees
- $1,000 home office stipend and $5,000/year for continuing education
- Competitive salary, comprehensive benefits, and meaningful equity
- ~130 people, built from zero in under three years — small enough that your work is visible, big enough to already be running at Dell- and Tripadvisor-scale
Also mention Maven AGI is an equal opportunity employer etc. That's boilerplate EEO; remove.
Now we need to avoid filler like "competitive salary, comprehensive benefits, and meaningful equity" maybe okay but it's vague. It's a benefit statement but not specific. Might be considered filler? The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state benefits. The line "Competitive salary, comprehensive benefits, and meaningful equity" is part of benefits. It's vague but still a statement. I'd include it as a benefit item.
Now we need to output HTML fragment only.
Structure:
Company overview paragraph.
About the role
Position overview paragraph.
Responsibilities
- ...
...
Requirements
- ...
...
Benefits
- ...
...
We need to ensure no extra headings like Skills, Qualifications, Pay, Schedule.
Now craft the paragraphs.
Company overview: combine sentences from "Company Overview Maven AGI sits at the center..." etc.
Let's write:
Maven AGI sits at the center of the hottest intersection in tech right now: AI and customer experience. While most "AI support" tools still focus on FAQs and deflection, Maven's agents actually do the work — autonomously interacting with customers, personalizing the conversation, and resolving complex issues, not just providing information. That's not a soft ROI story. It's the most direct cost-displacement case in enterprise software today: real human work, replaced, at a fraction of the cost — not "savings if you use it well," but savings because the agent did the ticket instead of a person. Founded in 2023 by executives from HubSpot, Google, and Stripe, Maven builds conversational AI agents that don't just answer customers — they act: going into a customer's account, finding the actual problem, and fixing it, with no human required. Customers like Dell, ServPro, HardRock, Tripadvisor, Clio, and Thumbtack rely on Maven, with independently verified results — customers report resolving 70–93% of interactions autonomously — and G2 has named Maven a High Performer and Best Meets Requirements across multiple categories this spring.
Now About the role paragraph: "Position Overview We're hiring a senior individual contributor to own demand generation at Maven. You'll set the strategy and own the number, and you'll also do the building yourself: configuring the platforms, launching the campaigns, writing the workflows, and pulling the data. We're looking for someone who enjoys hands-on work and doesn't see it as a step on the way to managing people. Our GTM motion runs on tight collaboration between marketing, SDRs, and AEs, and this role sits at the center of it. Day to day, you'll work closely with SDRs and AEs to make sure demand turns into real pipeline, not leads that sit in a queue. Inbound is a major part of the job, and you'll also drive outbound programs and ABM against our enterprise accounts. Given our stage, this role also leans toward growth. You should be comfortable going beyond traditional demand gen channels into experiment-driven tactics when they'll move the number, and comfortable building the systems that make those experiments cheap to run."
Now Responsibilities list as above.
Now Requirements list: include all bullet points from Who You Are plus How You Show Up values.
Let's list:
- 6+ years in demand generation, growth, or marketing operations at a B2B SaaS company, ideally including time at a startup or high-growth company
- You've built (not just run) a demand gen function or a major channel from the ground up, across both inbound and outbound
- Deep, hands-on platform experience: you've administered a marketing automation platform, built lead scoring and routing, and worked in tools like Clay without needing an ops team to do it for you
- Direct experience with SDR and AE teams: you've owned lead handoff, quality, and the feedback loop, rather than handing leads over a wall
- Comfortable in the data: you can pull your own reports, spot where the funnel is leaking, and explain it to sales leadership in plain terms
- Experience running ABM against a strategic or enterprise account list is a strong plus
- Bonus: experience marketing to technical or AI-forward buyers, or building GTM workflows that use AI and agentic tooling rather than just talking about it
- You put users at the center of your thinking, advocate for their needs, and design solutions that make their lives measurably better.
- You move with urgency and courage, unafraid to challenge convention and take smart risks in pursuit of meaningful outcomes.
- You make thoughtful decisions grounded in evidence, combining data with intuition to guide strategy and execution.
- You bring others along, value diverse perspectives, and contribute to a culture of trust and shared ownership.
Now Benefits list:
- 100% of medical, dental, and vision
for prose. Do NOT repeat job title as heading. Do NOT put Job ID etc. Remove boilerplate. Include only sections with real specific content. Avoid filler like "commensurate with experience". We need to parse the posting. Company Overview: description of company. Could be "About the company" but not required heading? The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can include About the role (maybe overview of role). Responsibilities (What You'll Do). Requirements/Qualifications/Skills (Who You Are). Benefits (What We Offer). Pay and Schedule only if present. Pay: posting mentions "Competitive salary, comprehensive benefits, and meaningful equity". That's a statement about pay but not specific numbers. Should we include Pay section? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Competitive salary, comprehensive benefits, and meaningful equity". That's a statement about pay and benefits. Benefits we already have. Pay we could include but it's vague. The rule says avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". "Competitive salary" is vague but still a statement. Might be considered filler? It's not a specific number. The instruction: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". "Competitive salary" could be considered placeholder. Safer to omit Pay section. Schedule: not mentioned. So omit. Thus sections: About the role (maybe Position Overview), Responsibilities (What You'll Do), Requirements (Who You Are), Benefits (What We Offer). Possibly Skills separate? Could combine Requirements and Skills. But we can have Requirements heading with list of qualifications. Skills maybe separate but we can incorporate. We need to preserve all substantive information. Let's extract. Company Overview: Not needed as heading? Could be part of About the role? But we can include a brief paragraph about company as part of About the role? The instruction: About the role heading for section headings (e.g. About the role, Responsibilities...). So we can put company overview under About the role? Might be better to have a short paragraph about the company under About the role heading. But the role overview is separate: "Position Overview We're hiring a senior individual contributor..." That's about role. So we can combine company overview and position overview under About the role? Might be okay. But we need to preserve all substantive info: company overview details about Maven AGI, its AI agents, customers, results, founding, etc. That's substantive. Should be included. Where to put? Could be a preceding paragraph before headings? The instruction says output only HTML fragment, no extra. We can include a
for company overview before headings. That's allowed. Then
About the role
with position overview paragraph. ThenResponsibilities
with- items from "What You'll Do". Need to capture each bullet.
Let's list responsibilities:
- Own the demand generation strategy and number: build and run multi-channel campaigns across inbound (paid ads, website conversion) and outbound (technographic targeting, sequences run with SDRs), with inbound as a primary driver of pipeline volume
- Partner with SDRs and AEs every day on campaign handoff, lead quality, and follow-through, with a tight feedback loop so what marketing sources actually converts
- Work hands-on in the platforms: own our lifecycle marketing program and performance marketing platforms, and be comfortable in Salesforce. You'll build the workflows, scoring, routing, and enrichment with your partners in GTM Systems
- Build and run ABM programs for strategic accounts: account selection and tiering, coordinated plays across paid, email, and outbound, and reporting on account-level engagement
- Work with field marketing on event strategy (conferences, dinners, sponsorships) and make sure field programs tie back to the same account and campaign framework as digital
- Define and own the metrics that matter (MQL-to-SQL conversion, pipeline sourced and influenced, CAC by channel, speed to lead) and build reporting that makes attribution something the team can trust
- Run a test-and-learn approach to new channels and formats, including AI-native and growth-style tactics (intent data, product signals, automated enrichment and personalization) where they fit our buyer
- Build the systems and playbooks that let demand generation scale without being rebuilt every quarter
We need to preserve all.
Now Requirements/Qualifications/Skills: "Who You Are" bullet list:
- 6+ years in demand generation, growth, or marketing operations at a B2B SaaS company, ideally including time at a startup or high-growth company
- You've built (not just run) a demand gen function or a major channel from the ground up, across both inbound and outbound
- Deep, hands-on platform experience: you've administered a marketing automation platform, built lead scoring and routing, and worked in tools like Clay without needing an ops team to do it for you
- Direct experience with SDR and AE teams: you've owned lead handoff, quality, and the feedback loop, rather than handing leads over a wall
- Comfortable in the data: you can pull your own reports, spot where the funnel is leaking, and explain it to sales leadership in plain terms
- Experience running ABM against a strategic or enterprise account list is a strong plus
- Bonus: experience marketing to technical or AI-forward buyers, or building GTM workflows that use AI and agentic tooling rather than just talking about it
Also "How You Show Up" values: customer champions, bold in action, data-driven and insight guided, stronger together. Those are cultural traits; could be included under Requirements or maybe separate section "Values". But not in prescribed headings. Could include under Requirements as part of "Who You Are". We'll keep as list items.
Now Benefits: "What We Offer" bullet list:
- 100% of medical, dental, and vision premiums covered for you, 80% for family
- HSA and FSA plans available
- Unlimited vacation and 100% paid parental leave
- Free lunches, onsite gym, and commuter benefits for in-office employees
- $1,000 home office stipend and $5,000/year for continuing education
- Competitive salary, comprehensive benefits, and meaningful equity
- ~130 people, built from zero in under three years — small enough that your work is visible, big enough to already be running at Dell- and Tripadvisor-scale
Also mention Maven AGI is an equal opportunity employer etc. That's boilerplate EEO; remove.
Now we need to avoid filler like "competitive salary, comprehensive benefits, and meaningful equity" maybe okay but it's vague. It's a benefit statement but not specific. Might be considered filler? The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state benefits. The line "Competitive salary, comprehensive benefits, and meaningful equity" is part of benefits. It's vague but still a statement. I'd include it as a benefit item.
Now we need to output HTML fragment only.
Structure:
Company overview paragraph.
About the role
Position overview paragraph.
Responsibilities
- ... ...
Requirements
- ... ...
Benefits
- ... ...