Don't treat evals as a mere checklist. Instead, use them as a creative tool to discover opportunities. A well-designed eval can reveal that a product is underperforming for a specific user segment, pointing directly to areas for high-impact improvement that a simple "vibe check" would miss.

For product managers not yet working on AI, the best way to gain experience is to build simple AI tools for personal use cases, like a parenting advisor or a board game timer. Using no-code prototyping tools, they can learn the entire development lifecycle—from ideation to prompting and user feedback—without needing an official AI project at work.

With AI agents automating raw code generation, an engineer's role is evolving beyond pure implementation. To stay valuable, engineers must now cultivate a deep understanding of business context and product taste to know *what* to build and *why*, not just *how*.

To simulate interview coaching, feed your written answers to case study questions into an LLM. Prompt it to score you on a specific rubric (structured thinking, user focus, etc.), identify exact weak phrases, explain why, and suggest a better approach for structured, actionable feedback.

Perplexity's VP of Design, Henry Modiset, states that when hiring, he values product intuition above all else. AI can generate options, but the essential, irreplaceable skill for designers is the ability to choose what to build, how it fits the market, and why users will care.

When hiring for creative roles like AI Product Manager, the resume itself is evaluated as a product. A generic, plain-text resume signals a lack of creativity and product taste. The design, clarity, and cohesive narrative it tells are direct demonstrations of the candidate's core skills.

The key technical skill for an AI PM is not deep knowledge of model architecture but a higher-level understanding of how to orchestrate AI components. Knowing what AI can do and how systems connect is more valuable than knowing the specifics of fine-tuning or RAG implementation.

Technical implementation is becoming easier with AI. The critical, and now more valuable, skill is the ability to deeply understand customer needs, communicate effectively, and guide a product to market fit. The focus is shifting from "how to build it" to "what to build and why."

Instead of immediately building, engage AI in a Socratic dialogue. Set rules like "ask one question at a time" and "probe assumptions." This structured conversation clarifies the problem and user scenarios, essentially replacing initial team brainstorming sessions and creating a better final prompt for prototyping tools.