← All speakers

Bio, Work & Ideas

Ankur Goyal

Conference affiliation: Braintrust · 2025

Ankur Goyal is the founder and chief executive of Braintrust, which builds evaluation and observability infrastructure for AI applications. He treats AI evaluation as production infrastructure: a continuous feedback loop connecting model behavior, user experience, product requirements, and changing technical capabilities.

Goyal studied computer science at Carnegie Mellon and worked on distributed databases at MemSQL, later renamed SingleStore, where he became vice president of engineering. He subsequently founded Impira, an AI company focused on extracting information from documents. After Figma acquired Impira in 2023, he led its AI team. Building evaluation systems at both companies inspired Braintrust, whose earliest users included Zapier. In February 2026, the company announced an $80 million Series B.

  • Evaluation should determine what gets built. Goyal judges evaluations by whether they help teams investigate customer complaints, assess potential features before release, and adopt improved models quickly. He advocates testing ambitious capabilities that current models cannot handle, allowing developers to recognize immediately when a new release makes them practical. His practical framework for evaluations treats those tests as instruments of product discovery, not merely regression checks.
  • Datasets and scoring functions encode product judgment. Evaluation datasets must evolve with real customer behavior, while scoring functions should reflect an application’s specific requirements. Braintrust’s open-source Autoevals library supplies reusable evaluators, but Goyal expects advanced teams to customize their criteria. He also favors human review before converting complaints into test cases: dissatisfaction does not necessarily mean an answer was incorrect.
  • Context engineering extends to agent tools. An agent’s effectiveness depends on its complete context, including tool definitions, tool responses, and accumulated interactions. Goyal describes an internal experiment where replacing JSON with YAML improved a model’s ability to use a tool’s output, illustrating why interfaces designed for software may require redesign for language models.
  • Loop optimizes the whole evaluation system. Braintrust’s Loop evaluation agent improves prompts, datasets, and scoring functions together, presenting proposed edits visibly and supporting multiple model providers. Its premise is that weak results can originate in incomplete examples or flawed grading as readily as in the prompt.
  • Active observability makes production traces usable. Goyal’s more recent work on active observability emphasizes automatically clustering conversations, identifying recurring patterns, and surfacing problems in production. Braintrust’s Topics capability addresses the associated challenges of reconstructing conversation threads, managing inference costs, and analyzing large trace volumes.

Read the topics behind these talks

3 conference talks

Key ideas

Scroll to read ↓

Useful evals turn model releases and user feedback into product decisions. Building them requires engineering the data, scoring rules, tools, and optimization process together.

  • Can your evals support the next model release?
    0:19 ↗
  • Datasets and scorers are engineering work
    2:10 ↗
  • Tools construct the context the model sees
    4:05 ↗
  • Keep an eval for the feature that does not work yet
    6:38 ↗
  • Give the optimizer the data and scores
    9:09 ↗
  • Loop turns evaluation artifacts into working context
    10:21 ↗
  • Build the organization to act on the evidence
    12:21 ↗
  • Does adding user feedback cause overfitting?
    14:36 ↗
  • What the token percentages measure
    16:10 ↗
  • An accurate answer can still receive a thumbs down
    17:33 ↗
  • Model breakthroughs depend on the task
    17:57 ↗

Key ideas

Scroll to read ↓

Zapier’s path from prompt-generated workflows to an interactive Copilot shows how product criteria, regression tests and tracing make model changes measurable.

  • What makes a generated workflow correct?
    0:49 ↗
  • Turn a prompt-to-Zap demo into product criteria
    4:06 ↗
  • Seed, run and grade the suite
    5:55 ↗
  • Make regressions visible and actionable
    6:58 ↗
  • Trace the move from generation to conversation
    8:42 ↗
  • Compare models inside the application
    10:21 ↗
  • Follow falling scores into the prompt
    11:51 ↗
  • Recover quality, then adopt the faster model
    13:12 ↗

Key ideas

Scroll to read ↓

Braintrust’s Loop moves evaluation beyond inspecting scores, using frontier models to propose changes to prompts, datasets, and scorers while keeping those edits visible.

  • The dashboard still leaves the hard decision to you
    0:42 ↗
  • Evaluating models that improve evaluations
    2:00 ↗
  • Enabling Loop and choosing a model
    3:00 ↗
  • Keep proposed changes visible
    3:24 ↗
  • Evaluation becomes work for the agent, too
    4:10 ↗

References