Click any tag below to further narrow down your results
Links
A LinkedIn post from MotherDuck describes how data engineer Nick Ursa's job changed once business users started answering their own data questions with AI agents. His role is now to build the frameworks and data model that make those self-serve answers trustworthy, especially when they reach the board.
- Ticket queues have mostly disappeared; business users now answer questions themselves with agents, and the data engineer decides how much checking each answer needs.
- The new role, which MotherDuck's CEO Jordan Tigani calls "data intelligence engineer," covers building frameworks, curating context, running evals, and fixing things when they break.
- Commenters argue that the real burden is tracing and eval layers, because failures in agent-driven data pipelines often break silently.
+ motherduck
+ data intelligence engineer
+ jordan tigani
+ self service analytics
evaluation
agents
OpenAI’s data productivity team built Kepler, an AI agent that understands their data platform context and writes iterative SQL to answer complex data questions. It handles table discovery, query refinement, follow-up prompts and even visualizations, cutting analysis time and reducing errors.
- OpenAI built Kepler, an internal AI agent that writes iterative SQL to answer data questions across 70,000 datasets and 600 petabytes daily, deployed via Slack, IDEs, or web UI
- It doesn't just query once—it discovers tables, refines CTEs, verifies numbers against dashboards/Notion, and proposes hypotheses (e.g., duplicate logging) for anomalies like a WAU spike
- Memory for self-learning plus rigorous evals let it improve over time without regressing
- Rolled out to 80% of the company, turning multi-engineer, multi-hour investigations into minutes