What is the difference between a data engineer and a data analyst CV?

A data engineer CV centres on building and running pipelines and platforms. A data analyst CV centres on questions answered and decisions supported.

Should I list every tool in the modern data stack?

No. List what you used in production and what the posting asks for, and show the main ones inside job entries.

How important is SQL for data engineering roles?

Very. Almost every posting asks for it. Show it through modelling, performance tuning or complex transformations you built.

Data

Data Engineer CV: what gets you shortlisted

Data engineers are judged on the pipelines and platforms that other teams rely on. Screeners want to know what data you moved, how much, how reliably and who used it. A list of tools without volumes, freshness or consumers is hard to assess.

Get my free score

One-time analysis • $1.99 • No subscription

What employers look for in a Data Engineer CV

Screeners check these first. Each one should be visible in your job entries, not only in a skills list.

Strong SQL and Python, used to build production pipelines rather than one-off scripts.
Batch or streaming pipelines you built, with volume, schedule and reliability.
Warehouse or lakehouse experience such as Snowflake, BigQuery, Redshift or Databricks.
Orchestration and transformation tools like Airflow, Dagster or dbt.
Data quality practices: tests, monitoring, lineage and handling schema changes.

Skills Data Engineer postings often ask for

Listing a skill is not the same as showing it. Resymetry counts a skill as matched only where your CV shows you used it.

SQL
Python
Apache Spark
Airflow
dbt
Snowflake
BigQuery
Kafka
Data modelling
AWS or GCP
Data quality testing

4 common Data Engineer CV mistakes and how to fix them

Pipelines described without size or frequency.
Fix: Add rows or GB per day, how often it runs and how fresh the data is.
No mention of who used the data.
Fix: Name the consumers: analysts, a product feature, finance reporting or a machine learning model.
Leaving out data quality work.
Fix: Mention tests, alerts or checks you added and what problems they caught.
Confusing the role with data analysis.
Fix: Lead with building and running data systems, not dashboards.

Weak and strong CV bullets

Illustrative examples, not real candidates. Use your own work and only numbers you can back up.

Weak: Built ETL pipelines.
Stronger: Built Airflow pipelines loading about 50 million events a day from Kafka into Snowflake, available to analysts within 15 minutes.
Weak: Used dbt for transformations.
Stronger: Rebuilt 60 reporting models in dbt with tests on key columns, ending the monthly mismatch between finance and product revenue figures.
Weak: Improved pipeline performance.
Stronger: Repartitioned a Spark job and removed a full-table join, cutting runtime from 4 hours to 35 minutes and halving its compute cost.

Know your chances for Data Engineer roles

Your score and your biggest problems are free. The full report is a one-time $1.99.