← All speakers

Bio, Work & Ideas

Ben Squire

Conference affiliation: Neo4j · 2026

Ben Squire is a senior developer advocate at Neo4j specializing in graph data science, identity resolution, and enterprise AI. His work applies relationships between fragmented records to problems ranging from audience analytics to AI agents navigating complex business data.

Previously a senior data scientist at Meredith Corporation, Squire worked on audience analytics, recommendation systems, and customer segmentation. Meredith’s graph-based audience analytics connected cookies and behavioral records into pseudonymous profiles, using community detection to identify related audiences and assess questionable third-party data.

At Neo4j, his focus expanded to knowledge graphs, developer advocacy, and enterprise data platforms, including graph analytics and customer segmentation for Snowflake. His SumoDB writing applies graph modeling and analytics to professional sumo.

  • Identity resolution through connected behavior: Graph relationships and community detection help connect fragmented audience signals and expose unreliable records.
  • Graph analytics inside existing data platforms: Snowflake-centered workflows make relationship analysis and customer segmentation accessible within established enterprise data environments.
  • Graph-shaped context for enterprise AI: At AI Engineer World’s Fair 2026, Squire supported a lakehouse AI workshop alongside Zach Blumenfeld and Ryan Knight. The team demonstrated how warehouse metadata, document hierarchies, cross-references, and thematic clusters can help agents answer questions across structured and unstructured information without necessarily copying operational records into another database. Blumenfeld led the technical presentation; Squire helped attendees work through the material.
  • SumoDB: Squire uses relationships among competitors and events to make graph modeling concrete through an unconventional real-world dataset.

Read the topics behind these talks

1 conference talk

Key ideas

Scroll to read ↓

A repair copilot needs more than matching passages and valid SQL. Warehouse connections, navigable documents, and link communities give it different ways to assemble the context a question requires.

  • The repair history and the manual are only the beginning
    2:08 ↗
  • A graph, an agent, and a runnable workspace
    7:37 ↗
  • Connections: use a graph to choose the SQL
    21:57 ↗
  • When metadata is enough—and when to import records
    34:26 ↗
  • Table of Contents: preserve the structure documents already have
    43:40 ↗
  • Build an outline that can stop at the right depth
    52:48 ↗
  • Keep the vocabulary useful to the query author
    1:03:09 ↗
  • Search the text, then restrict it to a subtree
    1:08:47 ↗
  • Names, freshness, and references are part of retrieval quality
    1:14:38 ↗
  • Themes: discover groups through document links
    1:21:43 ↗
  • Community descriptions, changing data, and trust
    1:33:23 ↗
  • From a diagnostic code to a repair recommendation
    1:39:19 ↗
  • Find the mismatch between the library and the field
    1:45:31 ↗
  • Theme coverage and the join the agent still performs
    1:52:10 ↗

References