← All speakers

Bio, Work & Ideas

Jerry Liu

Conference affiliation: CEO · LlamaIndex · 2026

Jerry Liu is the co-founder and chief executive of LlamaIndex, an open-source framework and enterprise platform that helps AI systems understand documents and automate knowledge work. He has helped turn retrieval-augmented generation from a basic chatbot technique into infrastructure for parsing, evaluating, searching, and acting on organizational information.

From machine learning to LlamaIndex

Liu graduated summa cum laude from Princeton University in 2017 with a computer science degree and a certificate in finance. He worked on feed ranking at Quora, researched autonomous-driving systems at Uber ATG, and later led machine-learning monitoring efforts at Robust Intelligence. His research included reactive planning and LiDAR compression.

In November 2022, while experimenting with GPT-3, he created GPT Index to help language models use information outside their training data. The project became LlamaIndex, which he developed into a company with Simon Suo, a former Uber colleague. Liu became chief executive and Suo chief technology officer; the founders announced an $8.5 million seed round led by Greylock.

The company expanded from open-source retrieval tooling into managed ingestion, LlamaParse and LlamaCloud, agent orchestration, and document automation. Liu favors developer-controlled infrastructure that can adapt to changing models, enterprise permissions, heterogeneous data, and specialized workflows.

  • Production-ready retrieval requires measurement. Liu separates ingestion, retrieval, and answer synthesis because each fails differently: missing evidence, irrelevant passages, stale documents, and flawed generation demand different remedies. His approach to production-ready RAG starts with task-specific benchmarks and independent retrieval evaluation, then improves chunking, metadata filters, hybrid search, and parsing before introducing more expensive agent architectures. With small-to-big retrieval, systems locate precise passages first and supply broader surrounding context for synthesis.
  • Document structure carries meaning. Tables, headings, page layouts, and images encode relationships that disappear when PDFs are flattened into undifferentiated text. Liu illustrates the problem with a Caltrain timetable: collapse its rows and columns, and a model can confidently return the wrong train time. LlamaParse preserves meaningful structure, while more advanced pipelines combine conventional parsing, language and vision models, and agentic validation.
  • Longer context windows still need retrieval. Larger prompts can reduce awkward chunking and support document-level reasoning, but they cannot make indiscriminate ingestion economical or transparent across large enterprise collections. Liu’s long-context retrieval work emphasizes selective access, source visibility, latency, and the appropriate amount of context for each task.
  • Document agents need complete toolboxes. Useful systems require enterprise connectors, synchronized permissions, parsing, indexing, semantic search, structured queries, and document manipulation. Liu distinguishes interactive assistants from more constrained background automations, with human review before consequential downstream actions. His spreadsheet agent interprets irregular Excel layouts, normalizes tables, and equips agents with spreadsheet-specific tools. He has also developed architectures in which specialist agents operate as independently orchestrated services.
  • Agent economics depend on the whole workflow. Liu’s LiteParse samples demonstrate fast, local, model-free document preparation. His two-pass document processing approach first processes large collections inexpensively, then applies costlier visual interpretation only to relevant pages. He also argues for model routing at the harness layer: optimizing accuracy and cost requires considering the complete combination of models, tools, orchestration, and task context.

On September 9, 2026, Liu announced a native LlamaParse connector for ChatGPT, following its Claude connector. His explanation separates specialized document parsing and extraction from the assistant’s higher-level reasoning: the connector exposes LlamaParse endpoints for preparing document context and extracting fields.

Talks by Jerry Liu

4 talks

Key ideas

Scroll to read ↓

Jerry Liu explains how to diagnose retrieval failures, evaluate complete RAG pipelines, improve precision through chunking and metadata, and selectively introduce agents or fine-tuning.

  • Define a task-specific benchmark before changing the pipeline, and evaluate retrieval quality separately from complete query-to-answer performance. 4:55 ↗ 5:50 ↗ 6:45 ↗
  • Start with better parsing, chunk-size tuning, hybrid search, and metadata filters before introducing more complex retrieval or agent architectures. 8:34 ↗ 10:26 ↗ 11:20 ↗
  • More retrieved context and reranking do not automatically improve answers; measure their effects because context overload and lost-in-the-middle behavior can worsen results. 9:30 ↗ 10:26 ↗ 13:05 ↗
  • Use small-to-big retrieval to match precise, compact evidence first and then expand to the broader context needed for synthesis. 12:18 ↗ 13:05 ↗ 13:51 ↗
  • Reserve multi-document agents and fine-tuning for needs that justify their added complexity, latency, or cost; query-side adapter tuning can improve retrieval without re-indexing the full corpus. 9:30 ↗ 14:52 ↗ 16:44 ↗

Key ideas

Scroll to read ↓

Jerry Liu outlines a progression from reliable document processing to agentic query execution and coordinated agent services, with production readiness as the organizing constraint.

  • A useful knowledge assistant must handle varied tasks and output formats; basic RAG alone does not provide robust planning, service interaction, or conversational memory. 1:14 ↗ 2:12 ↗
  • Preserving document structure during parsing can prevent tables and schedules from becoming misleading model inputs, reducing hallucinations before more advanced retrieval is introduced. 4:11 ↗ 5:11 ↗
  • Agentic RAG extends retrieval with tool use, query planning, and persistent state, enabling workflows that span multiple documents and both structured and unstructured data. 6:57 ↗ 8:03 ↗
  • Specialist agents can avoid overwhelming one model with hundreds or thousands of tools and may create opportunities for parallel execution and lower-cost, faster models. 9:07 ↗ 10:04 ↗
  • A production-oriented multi-agent architecture treats agents as independent services coordinated through a message queue and control plane, with either explicit workflows or model-directed delegation. 11:00 ↗ 12:06 ↗ 13:00 ↗
  • The proposed Llama Agents architecture is explicitly alpha-stage, and reliable orchestration, service boundaries, communication protocols, and integration remain active design challenges. 10:04 ↗ 11:00 ↗ 14:54 ↗

Key ideas

Scroll to read ↓

Document automation needs more than retrieval: it needs tools that preserve document structure and workflows that connect analysis, human review, and action.

  • Does knowledge work automation just mean RAG chatbots?
    0:26 ↗
  • Tools expose capabilities; orchestration encodes the task
    2:20 ↗
  • Build the preprocessing layer behind the tools
    3:27 ↗
  • Preserve the structure that reasoning depends on
    5:56 ↗
  • A spreadsheet is not necessarily a table
    8:15 ↗
  • Turn spreadsheet structure into specialized tools
    10:17 ↗
  • Flexible assistants rely on human guidance
    11:10 ↗
  • Constrain automation and preserve an approval boundary
    12:41 ↗
  • Background automation can supply foreground assistants
    14:01 ↗
  • Financial due diligence combines ingestion and a copilot
    15:13 ↗
  • Enterprise search adds reasoning over collections
    15:59 ↗
  • Datasheet ingestion turns business rules into structured output
    16:30 ↗

Key ideas

Scroll to read ↓

Reliable enterprise RAG depends on how documents become usable context, how pipelines are evaluated, and how retrieval fits into deployment, conversation and agent workflows.

  • From a directory of files to an answer
    0:41 ↗
  • Why a working prototype is not enough
    2:33 ↗
  • Build application expertise; manage the data plumbing
    5:05 ↗
  • Where sensitive documents go
    10:28 ↗
  • What an ETL practitioner needs to learn
    11:25 ↗
  • Pipeline promotion and a bank’s shared CMS
    15:20 ↗
  • Support is part of the production contract
    18:33 ↗
  • Keep the relationships inside a table
    19:42 ↗
  • Long context changes the unit of retrieval
    21:29 ↗
  • Store more than one representation
    23:21 ↗
  • From retrieval tools to agent services
    24:06 ↗

References