Senior Manager, Lifecycle Marketing

We need to output HTML fragment with headings

for sections present: About the role, Responsibilities (maybe "What You'll Own"), Requirements/Qualifications/Skills (maybe "What You Bring"), Benefits, Pay, Schedule only if present. The posting includes description about role, responsibilities, what you'll own, what you bring, why this role, etc. No explicit Pay, Benefits, Schedule. So we should not create those sections. Also we need to include About The Role heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should create headings for sections that have content: About the role, Responsibilities (maybe "What You'll Own"), Requirements/Qualifications/Skills (maybe "What You Bring"). Also maybe "Why this role" could be considered part of About the role? But we can include as separate? The instruction says prefer a few substantive sections over many thin ones. So we could combine "About the role" and "Why this role" into About the role section. Or we could have About the role and Responsibilities and Requirements. Let's parse content. The posting includes: - Intro about Dataiku (company description) - maybe not needed as part of job posting? Could be considered boilerplate? It's not about the role. Might be considered company overview; we could keep as part of About the role? Probably we should keep substantive info about role, not company marketing fluff. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company description at start might be considered boilerplate? It's not exactly boilerplate but it's generic marketing. Might be considered part of job posting but not required. However we need to preserve substantive information about the role. The company description may be considered not substantive for the role; but it's not EEO etc. It's okay to keep? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It doesn't say remove company overview. So we could keep it as a paragraph before sections. But we need to output only HTML fragment; we can include a

for that overview. Then we have "About The Role" heading (in caps). Then description: "Dataiku is the platform for AI Success, helping organizations put AI to work across their business. The Growth team drives pipeline generation globally through paid media, content syndication, ABM, and marketing operations, and we're looking for a Senior Manager, Lifecycle Marketing to build and own the lifecycle function end to end. You'll work closely with the VP of Digital & Growth and cross-functional partners across Web, Content, Acquisition, Field, Marketing Ops, Sales and Customer Success, supporting a global organization across regions. We don't have a lifecycle function today. Email and nurture are secondary responsibilities inside other teams' jobs, so nobody owns what a prospect or customer hears from us, in what order, or how often. There are existing nurture workflows without a current owner and no single view of what runs where, so establishing that visibility is the first priority. You'll build the function from there: the strategy, the systems, the programs, and the team." Then "What You'll Own" with bullet-like paragraphs (but not actual list). We need to convert any list of duties/requirements/benefits into

• . The text includes several items separated by line breaks or sentences. We need to identify lists. The content after "What You'll Own" includes: - The lifecycle operating system - One authoritative email and lifecycle calendar across prospect, new-user and customer programs: what goes out, to whom, from which team, and when. - Frequency governance, suppression logic and deliverability standards, including being able to say how much of an audience a given send reaches. - Segmentation and audience standards, set with the web and marketing ops teams who manage list creation today. - A standard for what a lifecycle program needs before it launches: entry criteria, success metric, exit. - Prospect and new-user nurture - New-user onboarding and activation nurture: the sequences that move a first touch to an engaged, sales-ready account. - Account progression communication: the programs that move accounts from first engagement toward qualified opportunity. - Nurture designed around named-account cohorts, built alongside the integrated campaign work so the two don't duplicate each other. - Visibility for BDRs into what a lead has already received before they reach out. - Customer lifecycle, retention and expansion - You'll partner closely with Customer Success and Product on this. - Programmatic customer nurture: adoption, education, and the sequences that keep users active after initial deployment. - Retention and expansion programs, built on account signals rather than calendar cadence. - Automation, data and measurement - The lifecycle layer of the marketing automation stack end to end: HubSpot workflows, Salesforce integration, and account and intent data from 6sense. - Consolidating the existing nurture workflows into something documented and maintained. - Reporting lifecycle contribution in terms the business already uses: engagement progression, influenced pipeline, retention and expansion. - You'll build your own reporting rather than wait for a dashboard. - The data quality this function depends on, with marketing ops: deliverability, consent, record hygiene. - AI and agentic workflows - Lifecycle work inside agentic workflows, rather than AI as a separate experiment. Lifecycle is one of the clearest applications: audience assembly, copy variation, program QA, performance summaries. - A standard for what a well-built lifecycle agent looks like, and where human in the loop is required. - Building the function - This is the lead role for a function that doesn't exist yet. You'll build the team as the function develops. - Getting the rest of the organization aligned on what you're building. - Lifecycle touches Web, Content, Acquisition, Field, Marketing Ops, Sales and Customer Success. Thus we can treat each top-level bullet as a
• with nested
  for subpoints? The instruction: Use
  • for any list of duties/requirements/benefits. It doesn't forbid nested lists. We can create a
    with
    • items, and inside each
    • we can have a
      for subpoints. That seems acceptable. Then "What You Bring" section with requirements. We need to convert that into a list as well. Content under "What You Bring": - 6+ years in lifecycle, nurture, email or growth marketing in B2B, ideally enterprise software with long, multi-threaded buying cycles. - Hands-on marketing automation depth. You've built and owned complex nurture programs yourself. - HubSpot or Marketo depth, Salesforce fluency, and real comfort with the data model under both. - Command of deliverability, frequency capping, suppression, consent and list hygiene. This role exists partly because nobody has owned these. - Experience on both sides of the lifecycle, prospect and customer. If your background covers one, tell us how you'd approach the other. - Fluency with intent and account data (6sense, Demandbase or similar), and a view on where it should drive program entry rather than only reporting. - Comfort building with AI, expected rather than optional. No engineering background needed. You should already be using LLMs in your own work, with a view on where they belong in lifecycle programs and where human in the loop is required. - Analytical strength. You can define a metric, instrument it, and defend it, including when the honest answer is that the current number isn't reliable. - Comfort with a build role: ambiguity, direct conversations about tradeoffs, and establishing a function through influence before you have a team. - Experience working across regions in a global organization. - Excellent written English. Other languages welcome, not required. We can make each bullet a
      • . Then "Why this role" section: maybe we can incorporate into About the role or separate. Since we prefer few sections, we could add a short paragraph under About the role after the initial description. Or we could make a separate section "Why this role". But that might be thin. However it contains substantive info: "Lifecycle is unowned at Dataiku today. This role defines it, reporting to the VP who owns the function, with a mandate to build the team behind it. What are you waiting for! At Dataiku, you'll be part of a journey to shape the ever-evolving world of AI. We're not just building a product; we're crafting the future of AI. If you're ready to make a significant impact in a company that values innovation, collaboration, and your personal growth, we can't wait to welcome you to Dataiku! And if you’d like to learn even more about working here, you can visit our Dataiku LinkedIn page." That's motivational; could be considered part of About the role. We'll include as a paragraph after the initial description under About the role. We must not include EEO boilerplate etc. At the end there is EEO statement and fraud warning etc. We must remove those. Thus final HTML: start with a

        for company overview? Actually the company overview at start: "Dataiku is the Platform for AI Success, the enterprise orchestration layer for building, deploying, and governing AI. In a single environment, teams design and operate analytics, machine learning, and AI agents with the transparency, collaboration, and control enterprises require. Sitting above data platforms, cloud infrastructure, and AI services, Dataiku connects the full enterprise AI stack - empowering organizations to run AI across multi-vendor environments with centralized governance. The world’s leading companies rely on Dataiku to operationalize AI and run it as a true business performance engine delivering measurable value. For more, visit the Dataiku blog, LinkedIn, X, and YouTube." That's generic marketing; could be considered boilerplate? Not exactly EEO but it's promotional. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not those. So we keep it. Thus output:

        Dataiku is the Platform for AI Success, the enterprise orchestration layer for building, deploying, and governing AI. In a single environment, teams design and operate analytics, machine learning, and AI agents with the transparency, collaboration, and control enterprises require. Sitting above data platforms, cloud infrastructure, and AI services, Dataiku connects the full enterprise AI stack - empowering organizations to run AI across multi-vendor environments with centralized governance. The world’s leading companies rely on Dataiku to operationalize AI and run it as a true business performance engine delivering measurable value. For more, visit the Dataiku blog, LinkedIn, X, and YouTube.

        About the role

        Dataiku is the platform for AI Success, helping organizations put AI to work across their business. The Growth team drives pipeline generation globally through paid media, content syndication, ABM, and marketing operations, and we're looking for a Senior Manager, Lifecycle Marketing to build and own the lifecycle function end to end. You'll work closely with the VP of Digital & Growth and cross-functional partners across Web, Content, Acquisition, Field, Marketing Ops, Sales and Customer Success, supporting a global organization across regions. We don't have a lifecycle function today. Email and nurture are secondary responsibilities inside other teams' jobs, so nobody owns what a prospect or customer hears from us, in what order, or how often. There are existing nurture workflows without a current owner and no single view of what runs where, so establishing that visibility is the first priority. You'll build the function from there: the strategy, the systems, the programs, and the team.

        Lifecycle is unowned at Dataiku today. This role defines it, reporting to the VP who owns the function, with a mandate to build the team behind it. What are you waiting for! At Dataiku, you'll be part of a journey to shape