Foundation
- Python and SQL
- Relational modeling
- Linux and Git
Work With Data · Career guide
Data Engineering
Build reliable pipelines and data models so analysts, products and ML systems can trust their inputs.
Career snapshot
A work-pressure profile, not a personality score
Three dots never means ‘better.’ It only means this dimension appears more often in the work.
Coding
Mathematics
Systems depth
Investigation
Creativity / design
Communication
Production responsibility
What would I actually do?
The work behind the title
- Ingest data from imperfect sources.
- Model warehouse tables and contracts.
- Schedule and monitor pipelines.
- Investigate missing, late or duplicated data.
- Balance cost, freshness and correctness.
Reality check
Finishing a tutorial and owning production consequences are different skills. The point is to see the gap, not hide it with hype.
You might enjoy this if…
Signals worth noticing
- You like making messy systems predictable.
- SQL feels expressive rather than boring.
- You care where data came from and whether it can be trusted.
You might dislike this if…
The uncomfortable part
- Invisible infrastructure gives you little satisfaction.
- You dislike investigating upstream failures you did not cause.
- Schema details and operational repetition drain you.
A realistic day
No day is identical, but the pressure may feel like this
This is a plausible mix of recurring tasks, not a scripted career fantasy.
Investigate why yesterday’s orders arrived twice.
Review a new event contract with backend engineers.
Backfill safely and add a regression check.
What should I learn?
A layered sequence, not a technology dump
Core
- Batch pipelines
- Data quality and contracts
- Warehouses and file formats
Practical
- Build an idempotent pipeline
- Add quality checks
- Document lineage
Later
- Orchestration
- Streaming
- Distributed processing
What not to learn yet
Not yet—because sequence matters
- Streaming before a reliable batch pipeline.
- A cloud certification without building a pipeline.
- Every warehouse tool shown in one architecture diagram.
Future You says
‘Later’ does not mean useless. It means you will learn it faster once you have a real problem for it.
AI & this career
Task Automation Exposure
This is not a replacement probability. Capabilities will change, so separate tasks, judgment and responsibility.
Writing routine transformations
AI is strong at familiar SQL and mapping patterns.
Student response: Validate grain, null behavior and edge cases with tests.
Diagnosing data-quality failures
AI can query clues but lineage and business semantics are local.
Student response: Learn profiling, reconciliation and contract design.
Owning trustworthy data definitions
Teams must agree what metrics mean and who is accountable.
Student response: Practice communicating definitions and trade-offs.
Curated learning resources
Learn → Practice → Go deeper
Resource count is not progress. Finish the recommended scope and build something.
PostgreSQL Tutorial
Learn relational ideas from the database itself, not an ORM abstraction.
Do this much: Tables, queries, joins, aggregates and transactions.
Last reviewed:
SQLBolt
Fast feedback for turning SQL syntax into usable skill.
Do this much: Complete lessons 1–12 and the exercises.
Last reviewed:
Data Engineering Zoomcamp
A realistic, project-oriented introduction to pipelines and warehouses.
Do this much: Modules 1–3 first; orchestration and streaming can wait.
Last reviewed:
Next choices
What evidence will you gather next?
Nearby directions
From skills to a destination
Where could you take this?
The career roadmap explains what to learn. A goal guide helps you put those skills to work. Start with one—not every route at once.