Jobs · Marketing · New York

Enterprise AI Technical Product Marketing Manager

Meta · New York, NY · 1 mo ago
Marketing$160k–$224k/yrFull-time
We need to output HTML fragment with sections only if content present. The posting includes responsibilities, qualifications (minimum and preferred), about meta (maybe not needed?), pay range. Also maybe "About the role" not present; we have description at start. We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We need to decide which sections to include based on content. We have: - Intro paragraph describing role: could be "About the role". That's appropriate. - Responsibilities: bullet list under "Enterprise AI Technical Product Marketing Manager Responsibilities:" with bullet points. - Minimum Qualifications: list of qualifications. - Preferred Qualifications: list. - Skills: maybe combine technical fluency etc. Could be part of qualifications. But we have separate "Skills" section maybe not needed if content covered elsewhere. The instruction: prefer few substantive sections over many thin ones. So we could combine Minimum and Preferred Qualifications into a "Qualifications" section, with subheadings? But we only allowed headings from list; we cannot add custom headings. So we could have a "Qualifications" section containing both minimum and preferred, maybe separate with

indicating Minimum and Preferred. Or we could have two sections: "Requirements" and "Qualifications". The list includes both. Could map Minimum Qualifications to "Requirements" and Preferred Qualifications to "Qualifications". That seems reasonable. - Skills: maybe not needed separately. - Benefits: posting mentions benefits generally but not specific; we should not create Benefits section unless posting actually states them. It says "Meta offers benefits. Learn more about benefits at Meta." That's generic, not specific. According to rule: never create Benefits section unless posting actually states them. It does mention benefits but not specific; maybe we should not include Benefits section because it's not substantive detail. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits exist, but not detail. Might be considered stating them, but we need to decide. The instruction: "Prefer a few substantive sections over many thin ones." Benefits section would be thin (just mention benefits). Better to omit. - Pay: posting includes salary range "$160,000/year to $224,000/year + bonus + equity + benefits". That's specific pay info. So we should include Pay section. - Schedule: not mentioned; omit. Thus sections: About the role, Responsibilities, Requirements (minimum qualifications), Qualifications (preferred qualifications), Pay. We need to use

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

    for prose. We must preserve all substantive information; do not invent or summarize away detail. Remove boilerplate etc. We need to include the intro paragraphs as About the role prose. Let's extract About the role: first paragraph(s) before responsibilities: "This role will help drive global go-to-market strategy and execution for Meta's enterprise AI products, including agent platforms, models, and APIs. Aligned to enterprise technical audiences, this role lives at the intersection of technical marketing, product, sales and client enablement.You will be responsible for understanding technical stakeholders across the buying committee, from CIOs and CTOs who make decisions to the developers and architects who run proofs of concept, and for knowing how each of them finds, evaluates, and implements AI solutions. You will help build Meta's point of view on enterprise AI and use that POV to shape our go-to-market approach and product roadmap.Technical fluency is a requirement. You must be able to hold a credible conversation with a developer about APIs, integration patterns, and model behavior, and then turn around and make the governance and business case to a CIO. You will be expected to have or rapidly develop working knowledge of market-leading AI platforms, model capabilities, and integration protocols.Cross-functional leadership, executive communications skills, ability to manage multiple concurrent projects, and comfort with ambiguity are musts. You will be expected to develop knowledge of how large enterprises evaluate and adopt AI, including build versus buy dynamics, AI governance and procurement processes, and the technical criteria that determine whether a platform clears evaluation." That is a block of prose. We'll put that in

    . Then Responsibilities: list bullet points after "Enterprise AI Technical Product Marketing Manager Responsibilities:" We'll extract each line. Responsibilities bullet list: - Develop and own audience strategy for enterprise technical stakeholders, including CIOs, CTOs, information security, architects, and developers - Create technical content including demos, architecture overviews, whitepapers, security documentation, and competitive proof points - Build programs that support technical evaluation, including developer enablement, sandbox and POC frameworks, and self-serve onboarding paths - Craft narratives that explain Meta's AI platforms, models, and APIs credibly to technical audiences and to executive decision makers - Partner with product and engineering to translate platform capabilities into market-facing value, and to feed audience insight back into the roadmap - Guide and partner with cross-functional teams, both global and regional, in developing sales collateral and technical marketing content - Conduct market and competitive research on enterprise AI platforms to identify positioning gaps and opportunities We'll put each as

  • . Then Requirements (minimum qualifications): list bullet points after "Minimum Qualifications:": - BA/BS degree - 8+ years of experience in product marketing, product management, or technical sales/marketing - Technical fluency sufficient to speak credibly with developers about APIs, integrations, and platform architecture - Experience marketing or managing API-first products, developer platforms, AI/ML products, or comparable enterprise technology - Demonstrated understanding of how enterprise technical stakeholders find, evaluate, and implement technology solutions - Track record of collaborating with cross-functional/cross-org teams to drive results - Experience simplifying complex technical concepts and communicating effectively with different audiences (e.g. product, engineering, sales, executives, customers) - Experience contributing at both strategic and tactical levels - Project and program management skills We'll put as
    • . Then Qualifications (preferred qualifications): list bullet points after "Preferred Qualifications:": - Familiarity with enterprise AI governance, compliance requirements, and procurement processes - Engineering, computer science, or technical background - Experience adhering to and implementing responsible, ethical AI practices (e.g., risk assessment, bias mitigation, quality and accuracy reviews) - Experience with AI agent platforms, LLMs, or conversational AI products - Demonstrated ability to integrate AI tools to optimize/redesign workflows and drive measurable impact (e.g., efficiency gains, quality improvements) - Experience building developer enablement programs, POC frameworks, or technical documentation strategy - Data analytics skills - Demonstrated ongoing AI skill development (e.g., prompt/context engineering, agent orchestration) and staying current with emerging AI technologies We'll put as
      • . Then Pay: we have "$160,000/year to $224,000/year + bonus + equity + benefits". Also note: "Individual compensation is determined by skills, qualifications, experience, and location. Compensation details listed in this posting reflect the base hourly rate, monthly rate, or annual salary only, and do not include bonus, equity or sales incentives, if applicable." That's more detail about compensation. We should preserve all substantive info. So we need to include that explanation as prose in Pay section. Thus Pay section:

        Pay

        then

        with the salary range and note. We must not include boilerplate like About Meta, EEO, etc. Remove those. Now output HTML fragment only. Let's craft:

        About the role

        This role will help drive global go-to-market strategy and execution for Meta's enterprise AI products, including agent platforms, models, and APIs. Aligned to enterprise technical audiences, this role lives at the intersection of technical marketing, product, sales and client enablement. You will be responsible for understanding technical stakeholders across the buying committee, from CIOs and CTOs who make decisions to the developers and architects who run proofs of concept, and for knowing how each of them finds, evaluates, and implements AI solutions. You will help build Meta's point of view on enterprise AI and use that POV to shape our go-to-market approach and product roadmap. Technical fluency is a requirement. You must be able to hold a credible conversation with a developer about APIs, integration patterns, and model behavior, and then turn around and make the governance and business case to a CIO. You will be expected to have or rapidly develop working knowledge of market-leading AI platforms, model capabilities, and integration protocols. Cross-functional leadership, executive communications skills, ability to manage multiple concurrent projects, and comfort with ambiguity are musts. You will be expected to develop knowledge of how large enterprises evaluate and adopt AI, including build versus buy dynamics, AI governance and procurement processes, and the technical criteria that determine whether a platform clears evaluation.

        Responsibilities

        • Develop and own audience strategy for enterprise technical stakeholders, including CIOs, CTOs, information security, architects, and developers
        • Create technical content including demos, architecture overviews, whitepapers, security documentation, and competitive proof points
        • Build programs that support technical evaluation, including developer enablement, sandbox and POC frameworks, and self-serve onboarding paths
        • Craft narratives that explain Meta's AI platforms, models, and APIs credibly to technical audiences and to executive decision makers
        • Partner with product and engineering to translate platform capabilities into market-facing value, and to feed audience insight back into the roadmap
        • Guide and partner with cross-functional teams, both global and regional, in developing sales collateral and technical marketing content
        • Conduct market and competitive research on enterprise AI platforms to identify positioning gaps and opportunities

        Requirements

        • BA/BS degree
        • 8+ years of experience in product marketing, product management, or technical sales/marketing
        • Technical fluency sufficient to speak credibly with developers about APIs, integrations, and platform architecture
        • Experience marketing or managing API-first products, developer platforms, AI/ML products, or comparable enterprise technology
        • Demonstrated understanding of how enterprise technical stakeholders find, evaluate, and implement technology solutions
        • Track record of collaborating with cross-functional/cross-org teams to drive results
        • Experience simplifying complex technical concepts and communicating effectively with different audiences (e.g. product, engineering, sales, executives, customers)
        • Experience contributing at both strategic and tactical levels
        • Project and program management skills

        Qualifications

        • Familiarity with enterprise AI governance, compliance requirements, and procurement processes
        • Engineering, computer science, or technical background
        • Experience adhering to and implementing responsible, ethical AI practices (e.g., risk assessment, bias mitigation, quality and accuracy reviews)
        • Experience with AI agent platforms, LLMs, or conversational AI products
        • Demonstrated ability to integrate AI tools to optimize/redesign workflows and drive measurable impact (e.g., efficiency gains, quality improvements)
        • Experience building developer enablement programs, POC frameworks, or technical documentation strategy
        • Data analytics skills
        • Demonstrated ongoing AI skill development (e.g., prompt/context engineering, agent orchestration) and staying current with emerging AI technologies

        Pay

        $160,000/year to $224,000/year + bonus + equity + benefits. Individual compensation is determined by skills, qualifications, experience, and location. Compensation details listed in this posting reflect the base hourly rate, monthly rate, or annual salary only, and do not include bonus, equity or sales incentives, if applicable.

Similar jobs