Jobs · Marketing

Head of Demand Generation

Celigo · United States · 2 days ago
RemoteRemoteMarketingFull-time
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. Must not repeat job title. Must not include Job ID etc. Must not include boilerplate like EEO etc. Must preserve all substantive info. We need to parse the posting. Let's extract sections: - About the role: The first paragraph(s) describing role: "Integration meets Innovation... Celigo is seeking a proven, senior demand generation leader to own the full pipeline engine...". That's about the role. - Responsibilities: The bullet list under "What would you do if hired?" includes many items: Always-On Demand Generation (with subpoints), Content Strategy & Thought Leadership Promotion, Digital Human & Webinar Programs, SDR & AI SDR Leadership. Those are responsibilities. - Requirements: Possibly the "Who are we looking for?" includes Skills & Abilities, Education & Experience. Could split: Requirements maybe Education & Experience; Skills & Abilities maybe Skills. But we need to decide. The instruction: Use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content. - About the role: description of role and mission. - Responsibilities: the detailed duties list. - Requirements: maybe the Education & Experience bullet list (10+ years, Bachelor's degree, etc.) - Qualifications: maybe the "Skills & Abilities" list? Or could treat Skills & Abilities as Skills section. Qualifications could be something else like "Proven track record..." but that overlaps. We need to avoid filler sections. Must include only sections with real specific content. We have content for: - About the role: yes. - Responsibilities: yes. - Requirements: Education & Experience (10+ years, Bachelor's degree, etc.) plus maybe "Proven track record of building and scaling integrated demand programs..." That's also a requirement. - Qualifications: maybe "Skills": The "Skills & Abilities" list (energized by not knowing, etc.) That's skills. - Benefits: The list under "Here you’ll experience..." includes Remote-first culture, etc., plus benefits list: Three weeks of vacation, Wellness days, Parental leave, Monthly tech stipend, etc. Also "Competitive compensation and benefits". So we have benefits. - Pay: The posting includes "Celigo reasonably expects to pay a base salary between $XYZ and $XYZ per year for this position." That's pay info (though placeholder XYZ). It says actual starting base pay will be determined... This is pay info. Should we include Pay section? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state a base salary range (though placeholder). It's still stating a range. So we should include Pay section with that sentence. - Schedule: Not mentioned. No schedule info (remote-first culture maybe implies remote but not schedule). So we should not include Schedule. - Qualifications: Could be separate from Skills. But we have Skills & Abilities as skills. Qualifications could be the "Education & Experience" but we already used that for Requirements. Maybe we treat Requirements as "Education & Experience" and Qualifications as "Proven track record..." etc. However the instruction: Prefer a few substantive sections over many thin ones. So maybe combine Education & Experience and Proven track record into Requirements, and Skills & Abilities into Skills. Then we don't need Qualifications section. But we need to decide if we need Qualifications heading at all. If we don't have specific content for Qualifications, we should omit it. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay. Check if any other content like "Remote-first culture..." is benefits. Yes. Now we need to format: - Use

for section headings. - Use
  • for any list of duties/requirements/benefits. - Use

    for prose. We must not repeat job title. Must not include Job ID etc. Must not include boilerplate like EEO etc. Must preserve all substantive info. We need to extract prose for About the role: The first paragraph(s) up to "What would you do if hired?" maybe. Let's copy: "Integration meets InnovationAt Celigo, we believe integration should empower — not exhaust — innovation. As a modern Integration and Automation Platform (iPaaS), we’re on a mission to simplify how companies integrate, automate, and optimize processes. Powered by game-changing technology like runtime AI and prebuilt, mission-critical integrations, Celigo is redefining how businesses connect their world.Celigo is seeking a proven, senior demand generation leader to own the full pipeline engine from always-on digital programs to brand and thought leadership amplification, digital events, and sales development. The right candidate brings a track record of building integrated, data-driven marketing motions in fast-growing B2B SaaS companies and can operate at both the strategic and executional levels.You will report to the VP of Revenue Marketing and serve as a key GTM partner to Sales, RevOps, and Marketing leadership. This role carries direct accountability for the marketing-sourced and marketing-influenced pipeline across new-logo and expansion efforts." We need to ensure spacing. We'll output as a

    . Now Responsibilities: The list under "What would you do if hired?" includes headings: Always-On Demand Generation, Content Strategy & Thought Leadership Promotion, Digital Human & Webinar Programs, SDR & AI SDR Leadership. Each has subpoints. We need to output a

    • for any list of duties/requirements/benefits. Should we treat each heading as a list item with sublist? Probably we can make each heading a
    • and inside include subpoints as nested
        . That's acceptable. We must preserve all substantive information. So include all subpoints. Let's extract: Always-On Demand Generation: - Drive MQL-to-SQL conversion through full-funnel campaign architecture; from top-of-funnel awareness to qualified pipeline handoff - Partner with Marketing Ops and RevOps to ensure clean attribution, lead routing, and funnel reporting in HubSpot and Salesforce - Manage paid media budgets with a rigorous test-and-optimize cadence; own program ROI and CAC reporting - Develop programs in partnership with ABX Campaign Architecture to drive account engagement and pipeline acceleration for target ICP accounts Content Strategy & Thought Leadership Promotion: - Lead content distribution strategy across owned, earned, and paid channels ensuring thought leadership assets (research reports, Gartner MQ, analyst content) are activated across every demand motion - Collaborate with Product Marketing and Content teams to develop demand-generating content: webinars, whitepapers, case studies, solution briefs, and digital content sequences - Drive awareness and new logo pipeline through brand amplification programs, including employee advocacy, partner co-marketing, and executive visibility - Leverage editorial and content calendars to maintain consistent, campaign-integrated messaging across all channels Digital Human & Webinar Programs: - Own the webinar program end-to-end: strategy, topic selection, promotion, speaker coordination, production, and post-event lead nurture - Expand digital event programming including virtual summits, customer spotlights, and co-hosted partner webinars - Explore and pilot emerging digital human / AI avatar capabilities to scale thought leadership content delivery and engagement SDR & AI SDR Leadership: - Manage and develop the SDR team (and AI SDR platform, if applicable), setting quota frameworks, outreach sequencing strategy, and performance accountability - Implement and iterate on AI SDR tools (e.g., Unify, 11x, Clay) to expand outbound reach with high-quality, personalized messaging at scale - Build a tight inbound-to-SDR handoff process, ensuring SLA adherence and lead quality feedback loops with Marketing - Define territory and account coverage strategy in coordination with Sales leadership and RevOps - Maintain SDR dashboards and weekly reporting on meetings booked, pipeline contribution, and SDR-sourced revenue Now Requirements: Education & Experience bullet list: - 10+ years of B2B SaaS demand generation, growth marketing, or revenue marketing experience, with at least 4 years in a senior leadership role - Bachelor's degree in business, marketing, or a related field. - Proven track record of building and scaling integrated demand programs that deliver measurable pipeline growth in mid-market and enterprise sales motions - Experience managing or closely partnering with SDR or BDR teams, with a working understanding of the inbound and outbound pipeline model - Background in content-led and thought leadership demand programs, not just paid media - Hands-on experience with HubSpot and Salesforce, including attribution, lead routing, and funnel reporting We could also include "Proven track record of building integrated, data-driven marketing motions..." but that's similar. We'll keep as list. Now Skills: The "Skills & Abilities" list: - Genuinely energized by not knowing. The demand generation playbook is being rewritten right now, and you treat that as the most interesting part of the job rather than the unstable part. You ask the questions others skip past, even when it slows a decision down. - Energized by finding new ways to apply AI to your own work and your team’s, with the judgment to tell a real efficiency gain from a good demo. - Comfortable shipping a thoughtful first version and improving it on real feedback. You do not let a perfect program block pipeline this quarter, and when a bet does not land you recover fast, without drama. - Connect program decisions to the revenue outcome, and think a step ahead about second-order effects: what a routing change does to SDR capacity, what a budget shift does to next quarter’s coverage. - Treat a pipeline gap as your problem to solve regardless of which team owns the step that broke. You find the faster path and take it. - Build all of the above into the team. You grow SDRs and marketers who take ownership, stay curious through change, and move without waiting for direction. - Credible and data-driven in front of Sales, RevOps, and Marketing leadership, and equally comfortable in the campaign details. We'll output as
        • . Now Benefits: The list under "Here you’ll experience..." plus benefits list. Paragraph: "Here you’ll experienceRemote-first culture, built on trust, collaboration, and transparencyA high-growth, inclusive work environment where innovation thrives and ideas are implementedLightspeed learning opportunities to keep you at the leading edge of your fieldExceptional coworkers who challenge and inspire you dailyCompetitive compensation and benefits, including:Three weeks of vacation (starting year one)Wellness days and holidays to rechargeParental leave and a generous benefits packageMonthly tech stipendRecognition and career development opportunities" We need to split into list items. The prose before colon maybe part of benefits description. We'll make a

          for the intro sentence? Actually "Here you’ll experience" is a heading? Not exactly. We'll treat as a

          then a

            for the list. List items: - Remote-first culture, built on trust, collaboration, and transparency - High-growth, inclusive work environment where innovation thrives and ideas are implemented - Lightspeed learning opportunities to keep you at the leading edge of your field - Exceptional coworkers who challenge and inspire you daily - Competitive compensation and benefits, including: - Three weeks of vacation (starting year one) - Wellness days and holidays to recharge - Parental leave and a generous benefits package - Monthly tech stipend - Recognition and career development opportunities We could nest the sublist under the "Competitive compensation and benefits" item. Now Pay: The sentence: "Celigo reasonably expects to pay a base salary between $XYZ and $XYZ per year for this position. Actual starting base pay will be determined by skills, experience, geographic location, and other non-discriminatory factors permitted by law. Total compensation may also include variable incentives, benefits, or other perks as outlined in any formal employment offer made." We'll output as

            . Now we must not include any boilerplate like EEO etc. We'll omit the DEI and equal-opportunity paragraphs. Now ensure

Similar jobs