← All speakers

Bio, Work & Ideas

Aman Khan

Conference affiliation: Arize · 2025

Aman Khan is an AI product leader at Google Cloud, working on the Gemini Enterprise Agent Platform and the evaluation, governance, and risk-management systems enterprises need to trust autonomous software. Previously head of product at Arize AI, he has built evaluation systems for self-driving cars, machine-learning products, and AI agents.

Khan began his career in engineering at Cruise before becoming a product manager for autonomous-vehicle evaluation systems. He then joined Spotify’s machine-learning platform organization, working on recommender systems, embeddings, and the Jukebox feature store. His product background also includes Apple and Zipline.

At Arize AI, Khan spent more than four years developing products for machine-learning observability, generative-AI evaluation, and agent development. He coauthored the launch of Alyx 2.0, a planning agent for AI development workflows, and contributed to work on hierarchical agent memory. He subsequently joined Google Cloud AI to work on its enterprise agent platform.

  • Evaluations as executable product requirements. Product managers should specify desired AI behavior through representative datasets, explicit grading criteria, and acceptance thresholds. Khan treats prompts, evaluation data, and user experience as shared responsibilities between product and engineering.
  • Evaluate the evaluator. Automated judges need their own quality controls: human-labeled examples, clearer grading instructions, lower-temperature model settings, repeated runs, and continued monitoring as production data changes. Direct code-based checks can replace model calls when requirements are straightforward.
  • Agent observability before optimization. A convincing answer can mask faulty routing, tool selection, or intermediate agent behavior. Khan’s multi-agent travel-planning demonstration shows how traces reveal interactions among research, budgeting, local-experience, and itinerary agents, enabling prompt changes to be tested against application data.
  • Evaluation datasets should evolve with failure modes. At Cruise, increasingly demanding scenarios progressed from straight roads to left turns and pedestrians. Khan applies that principle to AI agents: collect difficult production examples, revisit ambiguous cases, and continuously expand datasets as new weaknesses emerge.

Khan publishes AI Product Playbook and maintains personal-os, an open-source framework for an AI-powered personal operating system.

Read the topics behind these talks

2 conference talks

Key ideas

Scroll to read ↓

Scalable evaluation combines traces, human labels, model judgments and code checks, then uses that signal to improve applications, diagnose agent paths and refine the evaluators themselves.

  • When every trace needs many evaluations
    0:42 ↗
  • Observe the application at the level your team owns
    2:24 ↗
  • Choose the cheapest method that captures the signal
    4:08 ↗
  • Improve the application and the evaluator separately
    8:31 ↗
  • Evaluate the component, workflow, route and session
    10:34 ↗
  • Find failure modes across agent paths
    13:12 ↗
  • Compare what the agent did with the path it needed
    16:33 ↗
  • Put checks in the execution path deliberately
    18:20 ↗
  • Carry trace context across service boundaries
    20:39 ↗
  • Treat evaluator confidence as another signal
    22:18 ↗
  • Shorten the loop from feedback to a revised prompt
    23:20 ↗

Key ideas

Scroll to read ↓

A trip-planning agent becomes a practical evaluation system through traces, prompt experiments, human labels, and checks on the judges themselves.

  • What makes an AI prototype ready for production?
    1:30 ↗
  • Give the evaluator a task it can judge
    7:55 ↗
  • A seven-day Tokyo itinerary is only the beginning
    12:02 ↗
  • Trace where the itinerary comes from
    18:35 ↗
  • Replay the prompt with its actual context
    23:28 ↗
  • Turn traces into a repeatable experiment
    31:01 ↗
  • Measure the requirements separately
    39:53 ↗
  • Check the judge against human labels
    47:10 ↗
  • Make evaluation part of the product specification
    53:47 ↗
  • Improve the rubric, then rerun the comparison
    58:19 ↗
  • Keep finding the examples the dataset misses
    1:02:15 ↗
  • Extend the tests without losing ownership
    1:08:00 ↗
  • Capture telemetry that evaluations can use
    1:18:52 ↗
  • Build the next experiment from authorized data
    1:23:33 ↗

References