← All speakers

Bio, Work & Ideas

Justin Muller

Conference affiliation: Amazon Web Services (AWS) · 2025

Justin Muller is an applied AI architect who helps organizations turn generative AI prototypes into production systems they can evaluate, debug, and operate efficiently. At Amazon Web Services, where he was a principal applied AI architect in 2025, he developed a practical approach to generative AI evaluations that identifies specific failures instead of merely scoring model outputs.

Trained in physics, mathematics, law, and business, Muller worked in natural language processing before specializing in generative AI. His AWS customer work encompassed document processing, weather summaries, and structured business data. He also co-created an open-source Amazon Bedrock image-generation application with Sindhu Jambunathan.

His writing maps an expanding approach to production AI: prompt decomposition in 2024; the human design challenges of text-to-SQL in early 2025; and rubric-based evaluation without conventional gold-standard answers later that year.

  • Evaluation as failure diagnosis. An overall accuracy score cannot explain which component failed or how to repair it. Muller favors explicit grading criteria, category-level error analysis, and rapid feedback, while examining both a model’s stated reasoning and the explanations generated by its evaluator.
  • Prompt decomposition. Breaking large prompts into independently testable stages reveals where failures originate and allows engineers to choose the appropriate tool. For weather summaries, numerical comparisons belong in deterministic Python, not in a language model.
  • Human-reviewed evaluation data. Synthetic answers are provisional until people verify them; otherwise, a model’s mistakes become embedded in the benchmark. Where reference answers are unnecessary, clearly specified rubrics can provide an alternative.
  • Semantic routing and right-sized models. Directing simpler requests to smaller models and harder ones to more capable systems helps control accuracy, cost, and latency. Muller also applies established measures such as precision, recall, and F1 when they answer the evaluation question more reliably.

Read the topics behind these talks

1 conference talk

Key ideas

Scroll to read ↓

A convincing prototype can still hide failures. Effective evaluations expose where a workflow breaks, guide model selection, and turn each prompt change into actionable feedback.

  • What keeps a promising prototype from scaling?
    0:13 ↗
  • Design for diagnosis, not just a score
    4:01 ↗
  • A correct answer can hide a faulty method
    8:32 ↗
  • Break the prompt where you need to measure
    11:12 ↗
  • Route tasks without carrying unused instructions
    13:51 ↗
  • Habit 1: Make feedback fast enough to use
    15:28 ↗
  • Habits 2 and 3: Quantifiable and numerous
    18:18 ↗
  • Habit 4: Make generation and judging explainable
    20:05 ↗
  • Habits 5 and 6: Segmented and diverse
    21:23 ↗
  • Habit 7: Keep traditional checks
    22:38 ↗
  • From trustworthy references to useful feedback
    23:23 ↗

References