Senior Demand Generation Manager
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but we can use other headings as needed? Probably we should stick to those headings where applicable. But we can also create custom headings? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are examples; we can use other headings if needed, but better to map content to those headings. Let's map:
- About Kestra -> maybe "About the role"? Actually "About the role" is a heading for role description. But we have "About Kestra" describing company. Could fit under "About the role"? Not exactly. Could use "About the role" for role description, but we have separate sections: "The Role", "What You'll Own", etc. Might be better to use headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". However the posting includes many details that map to responsibilities, requirements, etc. We need to preserve all substantive info. We can create sections: About the role (company overview), Responsibilities (What You'll Own), Requirements (What We're Looking For), Qualifications (maybe same as Requirements), Skills (maybe part of Requirements), Benefits (Compensation And Benefits), Pay (maybe not specified, but we have "Competitive compensation, performance bonus, and equity" - that's compensation detail, we can include under Pay or Benefits). Schedule (Location maybe remote, overlap etc). The instruction: "Prefer a few substantive sections over many thin ones." So we can combine.
We must not emit headings with filler text. So we need to ensure each section has real content.
Let's extract substantive content:
Company description: About Kestra paragraph.
Role description: The Role paragraph (Senior Demand Generation Manager...).
What You'll Own: bullet-like paragraphs describing demand plan, multi-threaded account programs, multi-channel programs, nurture and conversion, measurement.
What We're Looking For: bullet-like paragraphs describing experience, skills.
What Makes This Role Worth Your Time: bullet-like paragraphs.
Compensation And Benefits: list of benefits.
Location: United States — Remote, with overlap with European working hours, as Product, Engineering, and the founders are based in Europe. Some travel to customer and industry events and company off-sites.
We should drop AI note and Equal Opportunity.
We need to format using for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to decide which sections to output. Perhaps:
About the role
(company overview + role description?) Could combine About Kestra and The Role.
But we need to preserve all info. Let's create sections:
- About Kestra (maybe heading "About the role"? Not ideal). Could use "About the company". But instruction says use h3 for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but says use h3 for section headings (e.g. those). Likely they expect those headings. However we can still use other headings as long as they are h3. The examples are just examples. So we can use any heading we like as h3.
Thus we can use headings like "About Kestra", "Role Overview", "Responsibilities", "Requirements", "What Makes This Role Worth Your Time", "Compensation and Benefits", "Location". That seems fine.
We must not repeat the job title as a heading. The job title is "Senior Demand Generation Manager". We'll not use that.
We must not put Job ID/requisition numbers as headings (none present).
Now we need to convert lists to - . Identify lists:
Under What You'll Own: multiple paragraphs each starting with a bold phrase? Actually the text: "The demand plan and the number Build and own the demand-generation plan..." It's not bullet list but separate sentences. Could treat each as a paragraph. However instruction: Use
- for any list of duties/requirements/benefits. If not a list, we can use
. So we can keep as paragraphs.
Under What We're Looking For: similar.
Under Compensation And Benefits: list of benefits separated by commas: "Competitive compensation, performance bonus, and equityMedical, dental, and vision insuranceEmployer-paid life and disability insurance401(k)Fully remote, with home-office and equipment budgetLearning and conference budgetPaid time off, company holidays, and parental leave". This is a run-on list; we should split into items. Let's parse:
- Competitive compensation
- performance bonus
- equity
- Medical, dental, and vision insurance
- Employer-paid life and disability insurance
- 401(k)
- Fully remote, with home-office and equipment budget
- Learning and conference budget
- Paid time off, company holidays, and parental leave
We'll make
- for each.
Location: maybe a
.
Now we need to ensure we don't include filler like "commensurate with experience". Not present.
Now produce HTML fragment.
Let's craft:
About Kestra
Kestra is a unified orchestration platform. One engine runs data pipelines, infrastructure operations, the scheduled scripts scattered across a company that nobody wants to touch, business processes that pause for a human decision, and now agents choosing their next move — all as executions in the same place, with one history to search when something breaks and one set of rules deciding who may run what. More than four billion workflows a year run on Kestra, and more than ten Fortune 500 companies are customers. The open-source project has more than 27,000 GitHub stars and 2,000+ plugins, and the engine, interface, editor, and plugins stay open source under Apache 2.0. In March 2026, we closed a $25M Series A led by RTP Global, with participation from Alven, ISAI, and Axeleo. Enterprises run Kestra in production because it delivers what legacy schedulers and point automation tools can't: unified governance, hybrid execution, and engineering-grade reliability.
Role Overview
Kestra is hiring a Senior Demand Generation Manager to own the program layer that turns product and market signals into enterprise pipeline. You own the demand-generation plan, the multi-channel programs, and marketing’s contribution to the enterprise pipeline, with shared accountability alongside Sales. You translate Kestra's go-to-market strategy into campaigns that create and progress qualified enterprise opportunities. This is a senior individual contributor role reporting to the Head of Marketing. You partner closely with Sales, Product Marketing, Developer Advocacy, and Growth Engineering. Growth Engineering owns the outbound automation engine, data enrichment, and attribution instrumentation, and hands you a signal layer built from product usage, community activity, web and GitHub activity, and enrichment data. You take that layer and build the named target-account list and the programs that turn it into enterprise pipeline. You are not building that infrastructure and you are not maintaining it. We don't buy, we build, and this role is for a marketer who works the same way: automating and experimenting on modern, AI-native tooling. You'll join a small, senior enterprise marketing team where each person owns a function rather than a product line: this role owns demand and campaigns, a peer owns positioning and competitive, another owns customer evidence and content, and another owns technical proof and demos. Kestra's advantage is converting one of the strongest open-source communities in orchestration into enterprise pipeline. That motion doesn't look like standard top-down demand generation, and you'll help define it.
Responsibilities
What You'll Own
- Build and own the demand-generation plan against Kestra's enterprise go-to-market strategy, establishing program and pipeline targets in partnership with the Head of Marketing and Sales.
- Build Kestra's enterprise account-tiering model, translating product, community, and firmographic signals into target segments and account priorities, and align with Sales on the accounts that matter most.
- Bring today’s outbound campaigns under one coordinated demand strategy, so programs running across Marketing, Growth Engineering, and Business Development share target accounts, a common thesis, and measurable outcomes.
- Partner with Growth Engineering to identify open-source deployments showing production-scale, multi-user, enterprise-shaped usage, and build the programs that turn those signals into enterprise conversations.
- Build multi-threaded account programs that engage multiple members of the buying group across technical, operational, and economic roles, moving accounts from initial technical interest toward qualified enterprise opportunities.
- Design and run integrated campaigns across paid media, content, email, webinars, and events, coordinated toward pipeline rather than run as one-offs.
- Build and run paid acquisition directly in the platforms. You will be hands-on in LinkedIn Ads and Google Ads, owning targeting, creative testing, and spend pacing.
- Shape account-based and competitive-displacement strategy for market-shift moments, briefing the outbound automation engine and wrapping it with multi-channel air cover.
- Own the program execution behind our flagship legacy-displacement campaign: targeting, channels, sequencing, budget, and cadence.
- Own the campaign assets that carry your programs: landing pages, nurture copy, and conversion paths.
- Coordinate with business development on contact-level outreach so account-level programs and individual outreach reinforce each other.
- Build the nurture and lifecycle programs that move prospects and self-serve users toward enterprise conversations.
- Improve conversion across the funnel, from first touch to qualified opportunity.
- Instrument every program so you can tie its contribution to pipeline, working from the attribution and data foundation Growth Engineering maintains.
- Report in the terms the business runs on — qualified accounts created, pipeline generated and progressed, and program efficiency — for quarterly business reviews.
- Own demand-generation program budget and channel allocation, moving investment toward what is producing pipeline.
- Manage agencies and partners where they extend your reach.
Requirements
What We're Looking For
- Typically 6+ years in demand generation, growth, or account-based marketing in B2B SaaS, with direct ownership of pipeline targets and outcomes.
- Proven across the demand stack: multi-channel campaigns (paid, content, email, events), lifecycle and nurture, ABM strategy, and the marketing-to-sales handoff.
- Hands-on paid media experience. You have built and run campaigns yourself in LinkedIn Ads and Google Ads, and you can explain what you changed, why you changed it, and how it affected acquisition efficiency, account engagement, or pipeline.
- A builder who automates and treats every campaign as an experiment — comfortable partnering with a technical growth-engineering function rather than owning the tooling end to end.
- Analytically rigorous. You pull your own data, build your own views, and interrogate a pipeline report rather than forward it.
- You
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to decide which sections to output. Perhaps:
About the role
(company overview + role description?) Could combine About Kestra and The Role.
But we need to preserve all info. Let's create sections:
- About Kestra (maybe heading "About the role"? Not ideal). Could use "About the company". But instruction says use h3 for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but says use h3 for section headings (e.g. those). Likely they expect those headings. However we can still use other headings as long as they are h3. The examples are just examples. So we can use any heading we like as h3.
Thus we can use headings like "About Kestra", "Role Overview", "Responsibilities", "Requirements", "What Makes This Role Worth Your Time", "Compensation and Benefits", "Location". That seems fine.
We must not repeat the job title as a heading. The job title is "Senior Demand Generation Manager". We'll not use that.
We must not put Job ID/requisition numbers as headings (none present).
Now we need to convert lists to - . Identify lists:
Under What You'll Own: multiple paragraphs each starting with a bold phrase? Actually the text: "The demand plan and the number Build and own the demand-generation plan..." It's not bullet list but separate sentences. Could treat each as a paragraph. However instruction: Use
- for any list of duties/requirements/benefits. If not a list, we can use
. So we can keep as paragraphs.
Under What We're Looking For: similar.
Under Compensation And Benefits: list of benefits separated by commas: "Competitive compensation, performance bonus, and equityMedical, dental, and vision insuranceEmployer-paid life and disability insurance401(k)Fully remote, with home-office and equipment budgetLearning and conference budgetPaid time off, company holidays, and parental leave". This is a run-on list; we should split into items. Let's parse:
- Competitive compensation
- performance bonus
- equity
- Medical, dental, and vision insurance
- Employer-paid life and disability insurance
- 401(k)
- Fully remote, with home-office and equipment budget
- Learning and conference budget
- Paid time off, company holidays, and parental leave
We'll make
- for each.
Location: maybe a
.
Now we need to ensure we don't include filler like "commensurate with experience". Not present.
Now produce HTML fragment.
Let's craft:
About Kestra
Kestra is a unified orchestration platform. One engine runs data pipelines, infrastructure operations, the scheduled scripts scattered across a company that nobody wants to touch, business processes that pause for a human decision, and now agents choosing their next move — all as executions in the same place, with one history to search when something breaks and one set of rules deciding who may run what. More than four billion workflows a year run on Kestra, and more than ten Fortune 500 companies are customers. The open-source project has more than 27,000 GitHub stars and 2,000+ plugins, and the engine, interface, editor, and plugins stay open source under Apache 2.0. In March 2026, we closed a $25M Series A led by RTP Global, with participation from Alven, ISAI, and Axeleo. Enterprises run Kestra in production because it delivers what legacy schedulers and point automation tools can't: unified governance, hybrid execution, and engineering-grade reliability.
Role Overview
Kestra is hiring a Senior Demand Generation Manager to own the program layer that turns product and market signals into enterprise pipeline. You own the demand-generation plan, the multi-channel programs, and marketing’s contribution to the enterprise pipeline, with shared accountability alongside Sales. You translate Kestra's go-to-market strategy into campaigns that create and progress qualified enterprise opportunities. This is a senior individual contributor role reporting to the Head of Marketing. You partner closely with Sales, Product Marketing, Developer Advocacy, and Growth Engineering. Growth Engineering owns the outbound automation engine, data enrichment, and attribution instrumentation, and hands you a signal layer built from product usage, community activity, web and GitHub activity, and enrichment data. You take that layer and build the named target-account list and the programs that turn it into enterprise pipeline. You are not building that infrastructure and you are not maintaining it. We don't buy, we build, and this role is for a marketer who works the same way: automating and experimenting on modern, AI-native tooling. You'll join a small, senior enterprise marketing team where each person owns a function rather than a product line: this role owns demand and campaigns, a peer owns positioning and competitive, another owns customer evidence and content, and another owns technical proof and demos. Kestra's advantage is converting one of the strongest open-source communities in orchestration into enterprise pipeline. That motion doesn't look like standard top-down demand generation, and you'll help define it.
Responsibilities
What You'll Own
- Build and own the demand-generation plan against Kestra's enterprise go-to-market strategy, establishing program and pipeline targets in partnership with the Head of Marketing and Sales.
- Build Kestra's enterprise account-tiering model, translating product, community, and firmographic signals into target segments and account priorities, and align with Sales on the accounts that matter most.
- Bring today’s outbound campaigns under one coordinated demand strategy, so programs running across Marketing, Growth Engineering, and Business Development share target accounts, a common thesis, and measurable outcomes.
- Partner with Growth Engineering to identify open-source deployments showing production-scale, multi-user, enterprise-shaped usage, and build the programs that turn those signals into enterprise conversations.
- Build multi-threaded account programs that engage multiple members of the buying group across technical, operational, and economic roles, moving accounts from initial technical interest toward qualified enterprise opportunities.
- Design and run integrated campaigns across paid media, content, email, webinars, and events, coordinated toward pipeline rather than run as one-offs.
- Build and run paid acquisition directly in the platforms. You will be hands-on in LinkedIn Ads and Google Ads, owning targeting, creative testing, and spend pacing.
- Shape account-based and competitive-displacement strategy for market-shift moments, briefing the outbound automation engine and wrapping it with multi-channel air cover.
- Own the program execution behind our flagship legacy-displacement campaign: targeting, channels, sequencing, budget, and cadence.
- Own the campaign assets that carry your programs: landing pages, nurture copy, and conversion paths.
- Coordinate with business development on contact-level outreach so account-level programs and individual outreach reinforce each other.
- Build the nurture and lifecycle programs that move prospects and self-serve users toward enterprise conversations.
- Improve conversion across the funnel, from first touch to qualified opportunity.
- Instrument every program so you can tie its contribution to pipeline, working from the attribution and data foundation Growth Engineering maintains.
- Report in the terms the business runs on — qualified accounts created, pipeline generated and progressed, and program efficiency — for quarterly business reviews.
- Own demand-generation program budget and channel allocation, moving investment toward what is producing pipeline.
- Manage agencies and partners where they extend your reach.
Requirements
What We're Looking For
- Typically 6+ years in demand generation, growth, or account-based marketing in B2B SaaS, with direct ownership of pipeline targets and outcomes.
- Proven across the demand stack: multi-channel campaigns (paid, content, email, events), lifecycle and nurture, ABM strategy, and the marketing-to-sales handoff.
- Hands-on paid media experience. You have built and run campaigns yourself in LinkedIn Ads and Google Ads, and you can explain what you changed, why you changed it, and how it affected acquisition efficiency, account engagement, or pipeline.
- A builder who automates and treats every campaign as an experiment — comfortable partnering with a technical growth-engineering function rather than owning the tooling end to end.
- Analytically rigorous. You pull your own data, build your own views, and interrogate a pipeline report rather than forward it.
- You
for prose. We need to decide which sections to output. Perhaps:
About the role
(company overview + role description?) Could combine About Kestra and The Role. But we need to preserve all info. Let's create sections: - About Kestra (maybe heading "About the role"? Not ideal). Could use "About the company". But instruction says use h3 for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but says use h3 for section headings (e.g. those). Likely they expect those headings. However we can still use other headings as long as they are h3. The examples are just examples. So we can use any heading we like as h3. Thus we can use headings like "About Kestra", "Role Overview", "Responsibilities", "Requirements", "What Makes This Role Worth Your Time", "Compensation and Benefits", "Location". That seems fine. We must not repeat the job title as a heading. The job title is "Senior Demand Generation Manager". We'll not use that. We must not put Job ID/requisition numbers as headings (none present). Now we need to convert lists to- . Identify lists:
Under What You'll Own: multiple paragraphs each starting with a bold phrase? Actually the text: "The demand plan and the number Build and own the demand-generation plan..." It's not bullet list but separate sentences. Could treat each as a paragraph. However instruction: Use
- for any list of duties/requirements/benefits. If not a list, we can use
. So we can keep as paragraphs. Under What We're Looking For: similar. Under Compensation And Benefits: list of benefits separated by commas: "Competitive compensation, performance bonus, and equityMedical, dental, and vision insuranceEmployer-paid life and disability insurance401(k)Fully remote, with home-office and equipment budgetLearning and conference budgetPaid time off, company holidays, and parental leave". This is a run-on list; we should split into items. Let's parse: - Competitive compensation - performance bonus - equity - Medical, dental, and vision insurance - Employer-paid life and disability insurance - 401(k) - Fully remote, with home-office and equipment budget - Learning and conference budget - Paid time off, company holidays, and parental leave We'll make
- for each.
Location: maybe a
. Now we need to ensure we don't include filler like "commensurate with experience". Not present. Now produce HTML fragment. Let's craft:
About Kestra
Kestra is a unified orchestration platform. One engine runs data pipelines, infrastructure operations, the scheduled scripts scattered across a company that nobody wants to touch, business processes that pause for a human decision, and now agents choosing their next move — all as executions in the same place, with one history to search when something breaks and one set of rules deciding who may run what. More than four billion workflows a year run on Kestra, and more than ten Fortune 500 companies are customers. The open-source project has more than 27,000 GitHub stars and 2,000+ plugins, and the engine, interface, editor, and plugins stay open source under Apache 2.0. In March 2026, we closed a $25M Series A led by RTP Global, with participation from Alven, ISAI, and Axeleo. Enterprises run Kestra in production because it delivers what legacy schedulers and point automation tools can't: unified governance, hybrid execution, and engineering-grade reliability.
Role Overview
Kestra is hiring a Senior Demand Generation Manager to own the program layer that turns product and market signals into enterprise pipeline. You own the demand-generation plan, the multi-channel programs, and marketing’s contribution to the enterprise pipeline, with shared accountability alongside Sales. You translate Kestra's go-to-market strategy into campaigns that create and progress qualified enterprise opportunities. This is a senior individual contributor role reporting to the Head of Marketing. You partner closely with Sales, Product Marketing, Developer Advocacy, and Growth Engineering. Growth Engineering owns the outbound automation engine, data enrichment, and attribution instrumentation, and hands you a signal layer built from product usage, community activity, web and GitHub activity, and enrichment data. You take that layer and build the named target-account list and the programs that turn it into enterprise pipeline. You are not building that infrastructure and you are not maintaining it. We don't buy, we build, and this role is for a marketer who works the same way: automating and experimenting on modern, AI-native tooling. You'll join a small, senior enterprise marketing team where each person owns a function rather than a product line: this role owns demand and campaigns, a peer owns positioning and competitive, another owns customer evidence and content, and another owns technical proof and demos. Kestra's advantage is converting one of the strongest open-source communities in orchestration into enterprise pipeline. That motion doesn't look like standard top-down demand generation, and you'll help define it.
Responsibilities
What You'll Own
- Build and own the demand-generation plan against Kestra's enterprise go-to-market strategy, establishing program and pipeline targets in partnership with the Head of Marketing and Sales.
- Build Kestra's enterprise account-tiering model, translating product, community, and firmographic signals into target segments and account priorities, and align with Sales on the accounts that matter most.
- Bring today’s outbound campaigns under one coordinated demand strategy, so programs running across Marketing, Growth Engineering, and Business Development share target accounts, a common thesis, and measurable outcomes.
- Partner with Growth Engineering to identify open-source deployments showing production-scale, multi-user, enterprise-shaped usage, and build the programs that turn those signals into enterprise conversations.
- Build multi-threaded account programs that engage multiple members of the buying group across technical, operational, and economic roles, moving accounts from initial technical interest toward qualified enterprise opportunities.
- Design and run integrated campaigns across paid media, content, email, webinars, and events, coordinated toward pipeline rather than run as one-offs.
- Build and run paid acquisition directly in the platforms. You will be hands-on in LinkedIn Ads and Google Ads, owning targeting, creative testing, and spend pacing.
- Shape account-based and competitive-displacement strategy for market-shift moments, briefing the outbound automation engine and wrapping it with multi-channel air cover.
- Own the program execution behind our flagship legacy-displacement campaign: targeting, channels, sequencing, budget, and cadence.
- Own the campaign assets that carry your programs: landing pages, nurture copy, and conversion paths.
- Coordinate with business development on contact-level outreach so account-level programs and individual outreach reinforce each other.
- Build the nurture and lifecycle programs that move prospects and self-serve users toward enterprise conversations.
- Improve conversion across the funnel, from first touch to qualified opportunity.
- Instrument every program so you can tie its contribution to pipeline, working from the attribution and data foundation Growth Engineering maintains.
- Report in the terms the business runs on — qualified accounts created, pipeline generated and progressed, and program efficiency — for quarterly business reviews.
- Own demand-generation program budget and channel allocation, moving investment toward what is producing pipeline.
- Manage agencies and partners where they extend your reach.
Requirements
What We're Looking For
- Typically 6+ years in demand generation, growth, or account-based marketing in B2B SaaS, with direct ownership of pipeline targets and outcomes.
- Proven across the demand stack: multi-channel campaigns (paid, content, email, events), lifecycle and nurture, ABM strategy, and the marketing-to-sales handoff.
- Hands-on paid media experience. You have built and run campaigns yourself in LinkedIn Ads and Google Ads, and you can explain what you changed, why you changed it, and how it affected acquisition efficiency, account engagement, or pipeline.
- A builder who automates and treats every campaign as an experiment — comfortable partnering with a technical growth-engineering function rather than owning the tooling end to end.
- Analytically rigorous. You pull your own data, build your own views, and interrogate a pipeline report rather than forward it.
- You
- for each.
Location: maybe a
- for any list of duties/requirements/benefits. If not a list, we can use