← All speakers

Bio, Work & Ideas

Michael Hunger

Conference affiliation: Neo4j · 2025

Michael Hunger is Neo4j’s Head of Product Innovation and Developer Strategy, developing practical ways for generative AI to retrieve connected, explainable information. His work on GraphRAG addresses a fundamental limitation of conventional retrieval: finding semantically similar passages does not necessarily uncover the relationships needed to answer complex questions.

Hunger has spent more than three decades in software development and approximately 15 years working with Neo4j. Earlier, he led Spring Data Neo4j, worked on cloud-hosting initiatives, and created an open-source CSV batch importer. His responsibilities expanded into developer relations, open-source ecosystem development, and product innovation, with projects spanning graph algorithms, GraphQL, Spark and Kafka integrations, APOC procedures, and database connectivity. A technical author, former InfoQ editor, and Java Champion, he is coauthoring GraphRAG: The Definitive Guide with Stephen Chin and Jesús Barrasa.

Building AI around connected knowledge

  • Connected context improves retrieval. Hunger’s work on graph-enhanced retrieval combines semantic search with relationships among documents, people, products, and other entities. Following those connections helps answer multi-hop questions and exposes the information supporting a generated response.
  • Knowledge graphs need deliberate construction. His approach starts with a lexical graph representing documents and their internal structure, adds domain-specific entities through schema-guided entity extraction, and enriches the result with graph algorithms and cross-document summaries. Existing customer records or product catalogs can anchor extraction and improve grounding. His AI Engineer technical walkthrough demonstrates how these layers become connected retrieval pipelines.
  • Developer tools make GraphRAG operational. Hunger has helped advance the LLM Knowledge Graph Builder and NeoConverse, tools for turning source materials into knowledge graphs and querying them conversationally. His GraphRAG ecosystem overview also covers integrations with established AI development frameworks. He contributed import functionality connecting Microsoft’s independently developed GraphRAG output to Neo4j.
  • Agents benefit from bounded graph operations. His work on Model Context Protocol integrations gives AI systems explicit tools for neighborhood lookup, shortest-path discovery, and domain-specific queries, making the context behind an answer more visible and controllable.

Read the topics behind these talks

2 conference talks

Key ideas

Scroll to read ↓

Build a retail graph, search product descriptions, personalize results through purchase paths, and use graph embeddings to supply recommendations for a seasonal email.

  • Prepare the notebook and graph database
    0:26 ↗
  • Find an item, personalize it, then suggest what goes with it
    5:59 ↗
  • Build the customer–article–product graph
    11:56 ↗
  • Generate embeddings before creating the index
    26:57 ↗
  • Wrap retrieval without coupling it to one storage layout
    35:47 ↗
  • Derive a peer group from shared purchases
    45:18 ↗
  • Rerank semantic matches without losing cold-start results
    57:39 ↗
  • Turn co-purchase structure into reusable recommendation links
    1:09:33 ↗
  • Refresh embeddings and choose their size
    1:20:07 ↗
  • Use graph queries for questions similarity cannot answer
    1:23:44 ↗
  • Feed two retrieved product lists into one email prompt
    1:29:30 ↗
  • Change the customer, then change the season
    1:37:04 ↗

Key ideas

Scroll to read ↓

GraphRAG combines index search with explicit relationships, preserving document structure and enterprise entities so retrieval can return the context an answer needs.

  • Why similar text is not enough
    1:20 ↗
  • Who owns the car, and who drives it?
    3:11 ↗
  • What the cited results actually measure
    5:06 ↗
  • Build the graph before querying it
    6:56 ↗
  • Keep the structure around each chunk
    9:09 ↗
  • Connect source text to entities and recurring topics
    10:38 ↗
  • Find entry points, then follow relationships
    12:50 ↗
  • Inspecting the evidence behind a DeepMind answer
    14:30 ↗
  • Turn domain queries into agent tools
    17:06 ↗
  • Construction and retrieval in Python
    18:25 ↗

References