The “Data Intelligence Engineer” and the changing AI data role
The author proposes “Data Intelligence Engineer” as a name for an emerging role on AI-enabled data teams, using MotherDuck co-founder Nick Ursa’s experience to argue that agents are changing how data work is organized. The article says this role automates ingestion and analytics tasks while humans retain responsibility for data models, business context, quality control, and final accountability; it also promotes MotherDuck’s related tools and features.
The article offers a concrete framing for how data-engineering responsibilities may shift when agents perform more of the execution work while humans remain responsible for context and accuracy.
I asked Nick Ursa, our lead data engineer (and MotherDuck co-founder), how AI had changed his job. His answer: "This is the first time in my career with no backlog."
You'd think that would leave him with plenty of time on his hands, but he's busier than ever. While the backlog is gone, the answers still have to be right, and a human still has to decide how much quality control to do. Whereas once upon a time his job was to make sure the numbers he was computing were right, now his job is to make sure that the numbers that an LLM or agent comes up with are right.
That's a different job from working a ticket queue. At Data Outpost on November 4, I proposed a name for this new role: the Data Intelligence Engineer. I think it's now the emergent role on an AI-enabled data team, and I’d like to share why.
What a data team is for?
A data team has one job: enable the business to make good decisions. The faster they can make those decisions, based on a more accurate picture of what is happening, the better those decisions can be.