Session

Behind the Curtain: How We Do Eval in Genie

Overview

ExperienceIn Person
TrackAnalytics & BI
IndustryEnterprise Technology
TechnologiesGenie
Skill LevelAdvanced

Evaluating AI systems is notoriously challenging—especially when correctness isn’t binary. In this talk, we’ll walk through how the Genie engineering team approaches evaluation at scale, from defining what “good” looks like to building reliable, automated eval pipelines. We’ll cover our mix of offline benchmarks, human-in-the-loop validation, and production feedback loops, along with the tradeoffs we’ve encountered. The goal is to share practical patterns and lessons learned that can help teams move faster while maintaining trust in their models.

Session Speakers

Speaker placeholderIMAGE COMING SOON

Shanshan Zheng

/Sr Manager, Engineering
Databricks

Full Summary

How Genie balances speed and accuracy for enterprise data analytics

Generative AI can accelerate analytics, yet enterprises cannot afford plausible answers that are wrong. The video explains how Genie is engineered to prioritize correctness, determinism, and governance so business users can trust AI-generated insights.

FAQ


Genie constrains generation to the customer's governed domain, inherits Unity Catalog permissions, and opts to ask clarifying questions or say "I don't know" when a prompt is too vague. That combination reduces off-domain queries and limits exposure to unauthorized data.

Internal evaluations show LLM judges tend to overgrade numeric accuracy by 10 to 20 percent, so absolute scores are unreliable. The relative difference between model versions is consistent, which makes LLM grading useful for pairwise comparisons during tuning.

Responses are anchored with few-shot examples, constrained semantic scopes, and clear SQL templates. When ambiguity prevents a single correct answer, Genie requests more detail rather than guessing, which helps produce repeatable outputs for well-formed questions.

Live queries are analyzed to reflect real workflows and difficulty levels, and customer-flagged edge cases become permanent tests. The evaluation corpus is updated continuously so offline coverage tracks how users actually work.

Measurements are validated at strict confidence levels to account for sampling noise, novelty effects, and temporal variance that can shift a single score by about 10 percent. Only deltas that clear these thresholds are treated as genuine progress.