DON’T Become a Data Engineer - Do THIS Instead

Overview

The speaker argues that becoming a data engineer is increasingly becoming a career “trap.” The core reasons are that the market is shifting: entry-level opportunities are shrinking while expectations are rising, making it harder to build the experience required for remaining roles.

Key Points and Evidence

Hiring slowdown in data/analytics

The video claims that Indeed’s Hiring Labs report shows data and analytics job postings fell 15.2% year-over-year through 2025, representing the biggest decline among tech categories.

Automation of traditional entry-level work

The speaker argues that common data-engineering tasks—such as ETL work, SQL transformations, and pipeline scheduling/monitoring—are increasingly being automated by tools using generative AI, citing examples like:

• Databricks Lake Flow Designer: no-code/drag-and-drop ETL with a generative AI assistant
• Snowflake Cortex Analyst / Snowflake Intelligence: plain-English querying that generates and runs SQL

Entry-level roles are drying up

The speaker states that entry-level data engineering roles make up only about 2% of all data-related job postings, limiting access to the “experience” needed to qualify for the remaining positions.

Rising requirements: AI-heavy skill set

They claim that 45% of data and analytics job postings (as of Dec 2025) mention AI. These roles may require skills such as:

• LLMs
• RAG
• Vector databases
• ML pipelines
• Preparing and managing data for AI workloads

The speaker argues that truly mastering these areas often takes longer than 5–6 months.

Blind spot: limited cloud infrastructure depth

A major critique is that many data engineers lack deep knowledge of cloud architecture and security—including areas such as:

• Networking
• VPCs
• IAM
• Encryption
• Deployment details and costs

They describe consulting experience where engineers could build pipelines but didn’t understand AWS architectural fundamentals.

Proposed Alternative: “Sell the Shovels”

Instead of targeting data engineering as the primary entry point, the speaker recommends pivoting toward cloud engineering, including related paths such as platform engineering, SRE, and DevOps.

The rationale:

• Cloud architecture is the foundation for both data engineering and AI systems.
• The combination of data + strong cloud/infrastructure skills is framed as rare and future-proof.

Why Cloud Engineering (They Say) Has Clearer Demand

Clearer entry points and strong hiring signals

The speaker claims the cloud market is projected to grow dramatically—from ~\$900B to \$5.4T over the next decade—and cites strong current hiring volume, such as:

• “Over 1,000 jobs” in the USA listed within a 24-hour window
• Government roles that may require security clearance

Advisory for Current Data Engineers

If data engineers don’t expand into cloud/infrastructure skills, the speaker warns their abilities may become less valuable as demand shifts.

Overall Conclusion

The video’s main recommendation is:

• Don’t target data engineering as the primary entry point.
• Build cloud engineering skills first, then pivot into data/AI work later if desired—aiming for paths that are less vulnerable to automation and better aligned with current hiring needs.

Presenters / Contributors

• Sulaiman (speaker/host)