AI PMs sit at the intersection of research, product, and business. Day-to-day, you're doing:

• Defining evals — what does "good" mean for our model output?
• Model selection tradeoffs (accuracy vs cost vs latency)
• Data quality — sourcing, labeling, filtering training data
• Safety & red-teaming — what could go wrong, and how do we prevent it?
• UX for non-deterministic outputs (streaming, retries, error handling)

Table Stakes

• Comfort with model behavior — you should be able to reason about prompts, temperature, context windows
• Understanding of eval design — precision, recall, human-in-the-loop scoring
• Awareness of latency + cost tradeoffs at inference scale
• Basic understanding of RAG, embeddings, fine-tuning

The Bonus (Differentiators)

• Ability to write a small experiment yourself in Python
• Familiarity with popular eval frameworks (LangSmith, DeepEval)
• Publicly-shared AI product experiments (a working demo beats a resume line)
• Knowledge of the latest research — read one paper per week

1. Ship something with an LLM: A weekend project counts. Deploy it, share it, learn from real users.
2. Publish your evals: Write about how you measured "good" for your project — this is rare and hiring-managers love it.
3. Speak the language: Read the OpenAI docs cover-to-cover. Read Anthropic's constitutional AI paper. Have opinions.
4. Choose your niche: AI infra PM ≠ consumer AI PM ≠ enterprise AI PM. Pick one and go deep.

• Frontier labs: OpenAI, Anthropic, Google DeepMind, Cohere
• Enterprise AI: Databricks, Snowflake, Salesforce (Einstein), Adobe (Firefly)
• AI-native startups: Perplexity, Character.ai, Runway, Harvey, Sierra
• Big Tech AI teams: Google Search, Meta AI, Microsoft Copilot, Apple Intelligence

AI PM interviews add a new dimension on top of traditional PM interviews:

• Product sense — expect questions like "How would you evaluate Copilot?" or "Design an AI feature for X."
• Model reasoning — "Explain when you'd use fine-tuning vs RAG vs prompting."
• Safety scenarios — "Your model just gave a user harmful advice. What do you do next?"
• Metrics — "How would you measure success for an AI chatbot?" (Hint: it's not just conversation length.)