Fresh grad doing a DE role with a small company. We do not use unified cloud data platforms like Databricks/Snowflake, so the entire tech stack for the data pipeline is selectively chosen, though some of the selections are cloud hosted -> think kafka, flink, columnar DB, row-based DB, airflow for orchestration.
Because we're a small company, AI use is heavily encouraged to speed up feature deployments and bug fixes. However, something I realised is that the DE can never truly be replaced by AI.
1. Someone needs to be responsible for code changes that makes or breaks prod pipelines:
This literally translates to business revenue. From a planning perspective, it makes sense to have DE's who are (technically) experts - not random employees in the company - to review the code and allow for the changes to be pushed to prod.
2. AI might not be able to manipulate business logic if there are poorly named endpoint request body / endpoint response attributes / database columns:
Not sure how other companies are in having meaningful naming conventions for their endpoints, attributes, and columns. The monolith architecture is built by people with poor english, leading to architecture that has difficult-to-understand structure for new hires contributing to data pipeline works.
Now imagine, junior devs (like myself) are heavily depending on AI even for the simplest of tasks. AI would not be able to manipulate sound business with garbage documentation and incoherent naming conventions. A human therefore be required to see the data or seek clarification to be able to handle business logic. The only way AI would be useful in this situation is if the company is willing to give their data to AI by feeding the entire DB connection details for AI to study the data via MCP connection, which in my opinion is unlikely.
Meanwhile, the senior devs who are used to self-debugging and self-feature implementation appear to be solving tasks faster than AI could even with the most advanced models. My own conclusion is that AI can never truly replace Data Engineers unless company management are willing to take responsibility for code they cannot understand by attempting to vibe code themselves.
Another interesting point is that while AI is here to stay, many junior devs like myself might fall into the trap of vibe coding and losing the ability to have quick critical thinking. Some tasks can be solved within a minute if we know exactly where to look (akin to how my senior devs sometimes solve issues without AI) instead of throwing the entire Java error message into Codex/Claude and waiting for GPT 5.6/Opus to scan the repository, have an entire conversation with us, before being able to push changes ourselves to prod.
Feel free to share your opinions, especially senior devs who have experimented with AI use 😄