← All speakers

Bio, Work & Ideas

Dat Ngo

Conference affiliation: Arize · 2026

On this page

Dat Ngo is an AI architect and director of solutions for Europe, the Middle East, and Africa at Arize AI, helping enterprises make AI agents and machine-learning systems observable, measurable, and reliable in production. His work combines applied statistics, practical evaluation design, and operational safeguards for systems whose behavior can change from one execution to the next.

From statistical modeling to AI infrastructure

Ngo holds a master’s degree in applied statistics from Texas A&M University and previously held data-science leadership roles at Wood Mackenzie, alliantgroup, and PointPredictive. At Arize, his work initially included fraud-model monitoring and drift detection, examining how production data diverges from training conditions and how those changes affect fraud prevention.

He subsequently extended those concerns to generative AI, working across Arize AX and Arize Phoenix, its open-source observability and evaluation platform. His work with Phoenix, Langflow, and NVIDIA demonstrates how teams can benchmark retrieval configurations and improve application quality through structured experimentation. His analysis of AI infrastructure in banking addresses the additional complications of distributed business units, governance requirements, and regulated environments.

How Ngo approaches reliable AI

  • OpenTelemetry-based agent observability: Traces and spans reveal which tools an agent called, where latency accumulated, and whether dependent steps occurred in the proper order. Comparing many executions exposes recurring failure patterns that an isolated successful answer can conceal.
  • Agent trajectory evaluation: Ngo evaluates individual model calls, interactions between components, complete tool-use sequences, and extended conversations separately. A convincing final response does not establish that an agent followed the correct process or satisfied its user, as he explains in his AI Engineer session on agent observability.
  • Calibrated, cost-aware evaluation: Human-labeled golden datasets help verify whether an LLM judge approximates trusted expert judgment. Schema validation, keyword checks, and other deterministic tests can answer narrower questions without adding unnecessary model cost or latency. Ngo also treats evaluators as systems requiring continuous correction, not fixed measures of truth.

Ngo’s longer-term focus is automated observability and evaluation: giving coding agents programmatic access to traces, diagnostics, and experiments so teams can identify failures, refine evaluators, and improve AI applications without manually inspecting every dashboard.

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 ↓

Agent reliability depends on connecting runtime telemetry to useful evaluation signals, then testing changes without losing sight of regressions.

  • How do you make AI work?
    0:31 ↗
  • Record execution, then follow state across runs
    2:50 ↗
  • Find the path that fails
    4:55 ↗
  • Choose the signal that answers the question
    6:49 ↗
  • Let domain experts define the intended experience
    8:44 ↗
  • Match evaluation scope to the evidence it needs
    9:59 ↗
  • Turn weak signals into experiments
    12:11 ↗
  • Move the workflow into the coding agent
    13:16 ↗
  • Local Phoenix and enterprise AX
    15:28 ↗

References