Which data role fits you: BA, DA, DS or DE, by the Tuesday task
The question each data role answers, the tool it opens and the person it talks to on an ordinary Tuesday, and a plain way to tell which one you would enjoy: one page.
Get the free PDF
One page, print-ready, free to share. No signup needed.
Job titles overlap and change from one company to the next. The Tuesday morning does not. This page describes the four data roles by what they actually do on an ordinary day: the question they answer, the tool they open, the person they talk to, and a plain way to tell which one you would enjoy. The print-ready A4 PDF is at the bottom.
Tuesday, 9am
| Role | The question | The tool | Talks to |
|---|---|---|---|
| BA | what should we change, and why | a process map, a deck | the ops lead who owns the process |
| DA | what happened last week, exactly | SQL, a dashboard | marketing, who asked on Monday |
| DS | what will happen, and how sure | a notebook, a model | product, who wants a yes or no |
| DE | is the data there at 8am | Airflow, a warehouse | the analyst waiting on the table |
All four open SQL on that Tuesday. The difference is what they do after.
The business analyst spends the morning with the operations lead, walking through how an approval moves between four people and where it waits. The afternoon is a one-page case: what the wait costs, what to change, what it would take.
The data analyst has a question from marketing on the desk since Monday: did the campaign bring new customers or the same ones again? The morning is a query, the afternoon is the chart and the two sentences under it.
The data scientist is asked whether a customer is likely to leave next month. The morning is a notebook, the afternoon is a conversation with product about what the model gets wrong and what it would cost to act on it.
The data engineer checks that the night's run landed, then spends the day on the pipeline that will make the next analyst question a one-liner instead of a week.
The tell
- People, then data: the meeting is the work. BA.
- Data, then people: the answer is the work. DA, or DS when the question is about next month.
- Data, then machines: the 8am run is the work. DE.
How to tell, honestly
Not from the salary table. From which part of the day you would look forward to.
- You like the meeting where the process gets fixed. The numbers are your evidence. BA.
- You like the moment the chart answers the question, and showing it. DA, or DS when the question is about next month.
- You like it when the job ran at 8am and nobody had to ask. DE.
- Not sure. Normal. Most people start as DA because SQL is the door to all four, and move later once they know which part of the day they wait for.
Remember
- The task, not the title. Pick the Tuesday you want.
Titles are negotiable, and a "data scientist" at a 20-person company often does all four jobs. Read the task in the job post (there is a sheet on that too) and decide from the Tuesday it describes.
Try a Tuesday before you pick
Each path has a free Foundations intro course on d8a.academy: a short first task in the role, in the browser, no setup. The analyst one is a query on a real table; the others follow the same idea. It is the quickest honest way to find out which part of the day you would wait for.
The full page is a free print-ready A4 PDF: four roles, one Tuesday.
Frequently asked questions
What is the difference between a data analyst and a data scientist?
What does a business analyst do with data?
What does a data engineer do all day?
Which data role should a beginner start with?
Get the free PDF
One page, print-ready, free to share. No signup needed.