There's been so much talk about "AI taking over jobs." But here's what I've actually seen in my own work, not in a think-piece, but in production.
At Amdocs, I've worked on migrating 1000+ tables (45B+ records) from legacy on-prem warehouses to a cloud-native platform(Teradata -> Snowflake) for a Fortune 50 telecom, where performance, scalability, and cost efficiency were all critical and non-negotiable.
More recently, I worked on a project that leaned heavily on GenAI. The AI handled the modular coding tasks, while our team focused on the part that actually decides whether a system survives: orchestrating and scaling the workflow.
The results were clear:
Here's the part the "AI is coming for your job" narrative misses. Generating a block of code is the easy 80%. The hard 20%, the part that decides whether anything ships, is everything around it: how the pieces fit together, how the system behaves under load, what happens when a step fails, and whether someone can still maintain it six months from now.
That's orchestration, system design, and judgement. It's exactly the muscle data engineering has always built, and it's exactly what AI doesn't replace. AI amplifies the engineer who knows what good looks like; it doesn't manufacture that judgement from nothing.
So the lesson I keep coming back to: AI isn't here to replace data engineers, it's here to amplify what we already do best.
The future isn't AI vs humans. It's AI + humans, building smarter, faster, more resilient data platforms at enterprise scale.
I'm curious where you land: do you think GenAI will reshape the role of data engineers, or simply make us more productive?
I'm Yash Agarwal, a Data Engineer II at Amdocs in Pune, India. I write about building reliable, large-scale data platforms and working alongside AI in production. You can find more of my work on my portfolio or connect with me on LinkedIn.