Our CEO Jordan Tigani asked a data engineer "how has AI changed your job?" Nicholas Ursa replied: “First time in my career with no backlog” But he’s also busier than ever. A question from the… | MotherDuck | 10 comments

Open original

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.

Nicholas Ursa, a data engineer at MotherDuck, told CEO Jordan Tigani that AI had given him his first stretch in his career with no backlog. That sounds like relief, but the post is clear he's busier than ever. Questions from the business used to arrive as tickets in his queue. Now the people asking them answer them on their own using agents, and Nick decides how much checking each answer needs. A rough number that doesn't matter much can run loose. A number headed to the board gets scrutinized at every step. The shift is from doing the work to deciding where verification effort goes. Tigani calls the role Nick has grown into a "data intelligence engineer." The person in it builds the frameworks, the data model, and the curated business context that let anyone, not just analysts, correctly answer questions, build interactive visualizations, create data-rich applications, and feed agents. Day to day that means preventing breakage, fixing things when they do break, running evals, and owning the key surfaces people rely on. The underlying point is that self-service doesn't remove accountability. When an answer informs a critical decision, someone still has to stand behind it, and at MotherDuck that someone is Nick. The replies from other data people add the practical caveats. One commenter says their company still calls the work data engineering, but the real change is accountability for evals and for the surfaces people trust. Another argues that self-serve offloads most request work but leaves you needing a revamped tracing and eval layer, and that unless engineers integrate that layer with existing checks and alerts, teams end up drowning in new definitions of "things that break," most of which now fail silently. Several people also commented on the naming itself, with the acronym for the role getting more groans than enthusiasm, and "context engineer" coming up as an alternative. The open question the post leaves is where the boundary sits: which decisions stay with the data team and which move to the builders.

Ask about this article