Behind the Curtain: How We Do Eval in Genie
Overview
| Experience | In Person |
|---|---|
| Track | Analytics & BI |
| Industry | Enterprise Technology |
| Technologies | Genie |
| Skill Level | Advanced |
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
Shanshan Zheng
/Sr Manager, Engineering
Databricks
Full Summary
How Genie Balances Speed and Accuracy for Enterprise Data Analytics
Generative AI can accelerate analysis and workflows, yet in enterprise settings even subtle mistakes can distort decisions. Plausible answers are not enough when a wrong SQL join still returns a pretty chart.
FAQ
They tend to measure plausibility, not grounded correctness. In data work a wrong query still returns numbers, so Genie is evaluated on whether answers are accurate within real business logic, not whether they read well.
Genie prefers a clarifying question or "I do not know" when prompts are vague or ambiguous. That choice avoids picking among equally plausible interpretations that would produce unstable or misleading results.
Benchmarks blend academic datasets mapped to functional skills, internal expert cases that mirror messy real schemas and business rules, and external vendor audits that deliver labeled query pairs at scale. LLM‑as‑judge augments coverage for complex cases, used primarily for consistent relative comparisons across versions.
Unity Catalog permissions are enforced end to end. If a user lacks access to a table or column, Genie cannot see or query it, so outputs respect existing data controls.
Variance is reduced with concrete few‑shot examples, narrow SQL patterns, and instruction constraints. When a question is too vague for a stable answer, Genie asks for clarification rather than guessing, and improvements are validated with confidence intervals to rule out noise.