The AI TPM Landscape

Mar 9

If you search for "AI Technical Program Manager career advice," you'll find two things: job postings and generic reassurance that "your skills transfer." What you won't find is anyone mapping the actual landscape showing which companies expect what, and where your existing experience actually gets you.

I've spent the last three years at a cybersecurity company during its AI transformation, watching how AI products actually ship. I've analyzed job descriptions across dozens of companies spanning three tiers (Frontier AI, AI-Applied-to-Business, and AI-Powered Applications).

AI TPM roles vary more than the job titles suggest. Some require deep fluency in model development. Others require working knowledge of how to ship AI-powered products without building the models yourself.

This distinction matters because it defines the depth of your technical pivot. It determines whether you need to master the 'physics' of model development, the 'orchestration' of AI-powered systems, or the strategic integration of AI into existing workflows.

Where the AI Jobs Actually Are

According to Menlo Ventures' 2025 State of Generative AI report, enterprise AI spend on software and services hit $37 billion in 2025, up 3.2x year-over-year. This is the fastest-scaling software category in history.

That money flows to three types of work: building foundation models, applying AI to business problems, and integrating AI into existing products. But spending categories don't map cleanly to TPM roles. A Tier 1 company might need both deep model expertise and productization TPMs. A Tier 2 company might need everything from ML pipeline specialists to integration experts. The point is where the opportunity sits, not where the dollars flow.

76% of AI solutions are now purchased rather than built (up from 53% in 2024). Companies are buying AI capabilities, not building them from scratch. This means the majority of AI TPM roles are about integrating and operationalizing AI, not training foundation models.

But what does it actually take to succeed as an AI TPM? It starts with understanding what 'AI fluency' really means.

Defining AI Fluency

I define AI fluency for TPMs as: The ability to understand AI/ML concepts well enough to facilitate technical decisions, ask the right questions, and translate between ML engineers and business stakeholders. You're not building models. You're making sure the right models ship.

The required level of AI Fluency varies by tier.

The Three-Tier Framework

AI TPM roles fall into three distinct tiers. The skills gap between them is larger than the job titles suggest.

  
        Tier
        Role Type
        AI Fluency Required
      
        Tier 1: Frontier AI
        Research/Foundation Model teams (Anthropic, OpenAI, DeepMind)
        Deep: must understand model training, evals, compute
      
        Tier 2: AI-Applied-to-Business
        Product AI teams (Meta Ads Ranking, Stripe Risk, Netflix Recommendations)
        Working: understand ML pipelines, A/B testing, model metrics, prompt engineering, responsible AI, agent evaluation
      
        Tier 3: AI-Powered Applications
        AI feature integration (ServiceNow, Workday, Atlassian)
        Conversational: evaluate AI solutions, define quality gates, discuss features substantively

One clarification: a company's tier and a role's tier aren't the same. Meta built Llama, but the Ads Ranking TPM role is Tier 2. Google has DeepMind, but most roles across the company span the full range from Tier 1 research programs to Tier 2 product AI to Tier 3 platform work. The question isn't "Is this an AI company?" It's "What does this specific role require?”

Tier 1: Frontier AI (Deep Fluency Required)

These roles are at companies pushing the boundaries of AI capabilities. TPMs here work directly with researchers and need to understand:

Compute capacity planning: GPU allocation, training runs, inference costs
Model evaluation: Benchmarks, red-teaming, safety testing
Research-to-production handoffs: Translating breakthroughs into shippable products
Infrastructure management: Large-scale, complex environments that evolve rapidly and serve as the foundation for other teams' work
AI safety policies: Responsible scaling, RLHF (Reinforcement Learning from Human Feedback), alignment methodologies (e.g., constitutional AI)

From actual Anthropic JDs: "Drive execution of compute capacity planning and allocation"... "Orchestrating complex model launches"... "Contributing to initiatives related to the Security Commitments in Anthropic's Responsible Scaling Policy"

This is fundamentally different work. If you don't know what RLHF means or why compute allocation matters, you'll need to close that gap before these roles are realistic.

Tier 2: AI-Applied-to-Business (Working Fluency Required)

These roles apply AI/ML to core business problems. TPMs manage ML-powered products but don't work on foundational model development:

ML pipeline coordination: Feature engineering, model training, deployment
A/B testing at scale: Experimentation frameworks, statistical significance
Model performance metrics: Precision, recall, latency, business KPIs
Cross-functional execution: Still the core TPM job: roadmaps, dependencies, stakeholder alignment

From a Meta Ads Ranking TPM JD: "Partner with Monetization Engineering and ML Ranking teams"... "Develop strategies on how to measure and improve... revenue"... "Scale Ads Recommendation technologies"

Most of this is standard TPM work: roadmaps, stakeholder management, execution. The AI-specific piece is understanding ML pipelines well enough to make sound program decisions.

In practice, the fluency that matters at Tier 2 comes down to defining evaluation criteria that both ML engineers and sales leadership can align on, facilitating trade-off decisions between accuracy and latency, and building quality gates that predict production success. The ML team owns the models. The TPM owns the process that gets them shipped.

Tier 3: AI-Powered Applications (Conversational Fluency Required)

These roles are focused on adding AI features to existing products. TPMs here manage AI-enhanced programs but the core work is traditional:

Feature integration: Adding AI capabilities to existing product surfaces
Vendor management: Integrating third-party AI APIs (OpenAI, Anthropic)
Product launches: Standard NPI with AI-specific quality gates
Platform programs: Infrastructure, security, scalability, same as always

From a ServiceNow Senior Staff TPM JD: "Drive technical programs across platform engineering"... "Partner with engineering leadership on roadmap execution"... "Establish operating cadences and governance"

This is traditional TPM work with an AI layer. You need to understand what AI features do, evaluate vendor solutions, and define quality gates, but you're not managing ML pipelines.

What I Wish I’d Known

If you're an experienced TPM considering AI roles, here's what I wish someone had told me three years ago:

For Tier 3 (AI-Powered Applications): You probably already qualify. You need enough AI fluency to evaluate solutions and define quality gates, not ML expertise. A few weeks of focused learning and one hands-on project closes the gap.
For Tier 2 (AI-Applied-to-Business): You have most of what's needed. ML pipeline understanding, evaluation metrics, and A/B testing at scale are learnable in 3-6 months with focused effort.
For Tier 1 (Frontier AI): This requires genuine investment. Plan for 6-12 months of serious coursework and hands-on projects. Adjacent experience (ML platform, infra supporting research teams) helps significantly. It's achievable, but the bar is high.

The barrier depends entirely on which tier you're targeting. And here's the good news: most AI TPM jobs are Tier 2 and Tier 3. Frontier companies are growing fast but remain relatively small (Anthropic and OpenAI each have a few thousand employees). The real volume is in companies applying AI to business problems or adding AI features to existing products. That's where your traditional TPM skills translate most directly. It doesn't mean Tier 1 is out of reach; it means you have options while you build toward it.

Where This Is Heading

My honest answer: no one knows exactly how this shakes out. But I’m watching three forces.

The fine-tuning divide. Generic AI APIs lead to generic products. Companies serious about moat-building will fine-tune on proprietary data. This shifts them from Tier 3 to Tier 2. If you’re one of these companies, your fluency requirements just changed.

The orchestration Problem. As AI agents proliferate, the hardest work won’t be tuning individual models. It’ll be architecting how they work together. Think less ML pipeline TPM and more AI systems architect. This could become its own tier.

The ROI correction. After years of AI experiments, boards are demanding results. Some complex Tier 2 projects will get scrapped in favor of simpler integrations that actually move the needle. The question becomes "does this make us money?" instead of the current "how sophisticated is our AI?".

My bet: The TPMs who thrive will be architects of AI-powered systems, not just integrate AI services. But regardless of which prediction plays out, the TPM fundamentals (shipping, cross-functional alignment, knowing when to cut scope) become more valuable, not less. The models will evolve. The need for someone to align humans around them won't.

What's Next

This article mapped where the roles are and what they require. The next two articles go deeper: "AI Fluency by Tier" breaks down exactly what fluency looks like at each level, and "The AI Learning Roadmap for TPMs" gives you a practical plan to build it.

The AI TPM transition isn't about becoming an ML engineer. It's about building enough fluency to ship AI products using the TPM skills you already have. The models will keep changing. The need for someone to get them shipped won't.

Abdoul Wane is a Principal TPM who has shipped AI products generating tens of millions in new revenue and built TPM and Product Operations functions at companies scaling through the 1,000-to-10,000 employee inflection point. He writes about the intersection of AI and program management at abdoulwane.com.

---

Appendix: Job Descriptions Analyzed

Here are the roles I analyzed. Job postings were sourced from company career pages and LinkedIn (Q4 2025 - Q1 2026). Specific links are omitted as postings change frequently. Search each company's careers page for current openings.

Note: The same company can have roles across multiple tiers. A company like Meta has Tier 1 roles (AI Research TPM), Tier 2 roles (Ads Ranking TPM), and Tier 3 roles (internal tools). The tier reflects the role, not the company.

  
    
        Company
        Role Title
        Tier
        Key JD Language
      

    
        Anthropic
        TPM - API, Compute, Security, Trust & Safety
        Tier 1
        "Compute capacity planning", "Responsible Scaling Policy"
      

        Meta
        Technical Program Manager, Ads Ranking
        Tier 2
        "ML Ranking teams", "Ads Recommendation technologies"
      

        Netflix
        Technical Program Manager, GenAI (L7)
        Tier 2
        "AI/ML platform", "recommendation systems"
      

        Stripe
        Technical Program Manager, Risk
        Tier 2
        "ML-powered fraud detection", "risk models"
      

        DoorDash
        Technical Program Manager (various)
        Tier 2
        "ML-powered logistics", "pricing algorithms"
      

        Figma
        Technical Program Manager, AI Platform
        Tier 2
        "AI Platform", "TPM greenspace environment"
      

        ServiceNow
        Senior Staff Technical Program Manager
        Tier 3
        "Platform engineering", "roadmap execution"
      

        Atlassian
        Principal Technical Program Manager
        Tier 3
        "Compute, Data Platform", "leveraging AI to enhance productivity"
      

  

Sources

Menlo Ventures, "2025: The State of Generative AI in the Enterprise" (December 2025)
Job descriptions sourced from company career pages and LinkedIn (Q4 2025 - Q1 2026)

Abdoul Wane