Data Engineer vs Analyst vs Scientist (in one restaurant)
I keep meeting juniors who say they want to “go into data,” then get stuck choosing a title.
So I drew it as a restaurant:
The three roles
- Data Engineer → kitchen. Make the ingredients arrive clean and on time. Pipelines, quality, storage. If this breaks, nobody else can cook.
- Data Analyst → the board. Say what sold and what didn’t, so someone can decide. Metrics, reports, “so what?” If definitions are fuzzy, the board lies.
- Data Scientist → the experiment table. Test “what if we change the recipe?” Models, experiments, hypotheses. If the question is vague, the experiment is theater.
Same restaurant. Different jobs.
How to choose early in your career
Pick the pain you like solving, not the fanciest title:
| If you enjoy… | Start closer to… |
|---|---|
| Making systems reliable so data shows up | Data Engineer |
| Turning numbers into a clear decision | Data Analyst |
| Designing tests and uncertain bets | Data Scientist |
Titles blur in real companies (and “analytics engineer” sits between kitchen and board). That is fine. The useful skill is knowing which job you are doing today.
One tip before you chase tools
Learn the shared vocabulary of the business first: what people mean by conversion, retention, revenue. Tools change. Confused definitions do not wait for your stack.
If this picture helped, tell me which role you were mixing up at the start.