ETL Developer → Data Engineer
A realistic transition from ETL Developer to Data Engineer: transferable skills, the gaps to close, a step-by-step learning plan and alternative routes. Estimated skill overlap 62%. Difficulty: Easy.
Difficulty: Easy7 stepsDuration: 4 to 8 monthsOverlap: 62%
Transition from ETL Developer to Data Engineer.
Transferable skills
- SQL
- Orchestration (Airflow)
- Data modelling
- Cloud data platforms
Skills to learn
- Spark / distributed processing
- Streaming (Kafka)
- CI/CD & testing
Step-by-step learning plan
1. Build on your ETL Developer experience
2–4 weeks
Leverage
- SQL
- Orchestration (Airflow)
- Data modelling
- Cloud data platforms
Map transferable skills — SQL, Orchestration (Airflow), Data modelling — against what a Data Engineer needs.
2. Close the partial gaps toward Data Engineer
3–6 weeks
Improve
Raise Python to the level a Data Engineer relies on.
3. Learn the core of the Data Engineer role
6–10 weeks
Learn
- Spark / distributed processing
- Streaming (Kafka)
Technologies
TerraformKubernetesAWS
Cover the biggest gaps first: Spark / distributed processing, Streaming (Kafka).
4. Master advanced Data Engineer skills
6–10 weeks
Learn
Technologies
GCPParquetLinux
Handle the advanced topics: CI/CD & testing.
5. Get productive with the Data Engineer toolchain
4–8 weeks
Technologies
TerraformKubernetesAWSGCPParquetLinux
Be hands-on with Terraform, Kubernetes, AWS and the rest of the target stack.
6. Practise Data Engineer work in real conditions
4–8 weeks
Ship a portfolio project or take on Data Engineer tasks at work.
7. Get certified and position yourself as a Data Engineer
4–8 weeks
Technologies
Google Professional Data EngineerAWS Data Analytics Specialtydbt Analytics Engineering
Update your CV and LinkedIn around Data Engineer, then apply to target roles.