Back
4 min read

The Next Era of Data Engineering

AI Data Engineering Future of Work

I have been asked this question so many times recently during my conference talks, at work, and while mentoring junior engineers: Are LLMs going to put data engineers out of a job? Am I destined to become a glorified prompt engineer?

Having spent over a decade in the data trenches, from wrestling with legacy systems like Teradata and Informatica to building planetary-scale data architectures here at Google using BigQuery, let me give you my unfiltered and entirely candid take.

No, AI is not coming for your job. But it is coming for your boilerplate.

If your entire professional identity is wrapped up in manually writing routine MERGE statements, cleansing basic CSVs, or babysitting fragile and straightforward pipelines, then yes, you should be paying close attention. But if you are a true data engineer, this AI shift is the greatest career accelerator we have ever seen. Here is how I see our roles evolving and why the future of data engineering is vastly more interesting than its past.

The Myth of the Glorified Prompt Engineer

When people see an AI agent infer relationships and write an entire data pipeline on the fly, the immediate fear is obsolescence. But this fear fundamentally misinterprets what a data engineer actually does. We do not just write code. We design reliable systems.

Right now, everyone from product managers to software engineers is suddenly moving 10 times faster because of generative AI. Because they are moving faster, the volume of data, the complexity of system integrations, and the sheer demand for data products are skyrocketing.

I have never had more open roles on my team because demand for data engineering is so strong, and I am at a company that is literally building the AI that is supposed to put us all out of work. — Paul Elwood, Head of Data Engineering at OpenAI

AI is not replacing the need for engineering. It is changing the nature of the problems we have to solve. You will not be a glorified prompt engineer. You are going to be tackling emergent, massive-scale distributed systems challenges that simply did not exist when we were only moving at a human pace.

Moving Up the Abstraction Stack

So, if an AI can write the code and cleanse the data, what is left for us?

We are moving to a higher level of abstraction. For the last ten years, we have been mechanics, meticulously tightening the bolts on ETL pipelines and DAGs. Going forward, we are becoming the architects and the wardens of autonomous systems.

Here is what the day-to-day of an AI-era Data Engineer actually looks like:

1. Taming Probabilistic Chaos

AI agents are inherently probabilistic. They guess, they infer, and sometimes they hallucinate. Data systems, however, are relied upon to be strictly deterministic. A CFO does not want a probabilistic revenue dashboard. Bridging the gap between probabilistic AI tools and deterministic business requirements is a deeply technical, complex engineering challenge.

2. Building Guardrails, Not Just Pipelines

We will spend less time writing the mechanical steps of data movement and much more time building robust guardrails. How do you evaluate an AI model’s output continuously? How do you enforce strict data quality standards when autonomous agents are generating and moving data at lightspeed?

3. Owning the Semantics

As AI agents begin to query data autonomously, they need to know exactly what the data means. The AI does not inherently know the difference between an active user and a registered user. Defining, materializing, and enforcing those semantic contracts will be our primary directive.

The Survival of the Adaptable

In my career, I have seen technologies come and go. The engineers who survive and thrive are never the ones fiercely guarding a specific tool or a manual process. They are the ones who lean into the next wave.

Do not fear the automation of the mundane. Let the AI write the boilerplate. Let it do the initial data cleansing. By offloading the mechanical execution to AI, we finally have the bandwidth to tackle the deeply technical, architectural problems that actually drive our businesses forward.

Note: I used AI to help with grammar, structure, and formatting for this post.