Skip to content Skip to a section

📊Craft & Know-How

Data Scientist · Finds patterns and builds predictive models from data — a 2008 job title built on three centuries of counting, testing and visualizing evidence.

At a glance
Score intensity

Darker cells mean a higher score for this topic on that metric.

Last reviewed Sources & creditsMedia creditsMethodology

Quick answers

What does a data scientist actually do day to day?

Contrary to the 'building AI models' image, most days split between writing SQL queries and Python code to pull and clean data, running statistical tests or training models, and translating results into a chart or memo a non-technical stakeholder can act on. Practitioner surveys consistently put data cleaning and preparation at roughly half or more of total working time.

Do you need a PhD to become a data scientist?

No. Unlike medicine or law, there is no license or single required degree; a bachelor's or master's in statistics, computer science, mathematics or a related quantitative field is the most common path, and a strong portfolio of real projects often matters more to employers than the exact credential. PhDs are more common in research-heavy or applied machine-learning roles.

Is data science just statistics with a new name?

Not quite. It draws heavily on statistics — Fisher's experimental design, Tukey's exploratory analysis — but adds programming, database engineering and machine learning that classical statistics departments rarely taught. William S. Cleveland proposed the term in 2001 specifically to describe this enlarged, computing-heavy version of the field, built on statistics rather than replacing it.

Is data science at risk from AI?

The routine end is already exposed: AutoML tools can fit and tune standard models, and AI assistants can write SQL queries, first-draft exploratory charts and boilerplate pipeline code faster than a person. What has not been automated is framing the right question, judging whether a pattern is meaningful or spurious, and taking responsibility for a decision built on the result.

How much do data scientists earn?

It varies widely by country and seniority. The US Bureau of Labor Statistics put the median annual wage for the Data Scientists occupation at roughly $108,000 in 2023, while junior analysts often start closer to $70,000-$95,000 and senior or principal data scientists at major technology companies can earn $200,000-$400,000 or more in total compensation with equity.

What's the difference between a data scientist, a data analyst and a machine learning engineer?

A data analyst typically answers defined business questions with existing data and dashboards; a data scientist builds new statistical models and predictive analyses, often from messier data; a machine learning engineer takes a model out of a notebook and makes it run reliably, at scale, in production. The lines blur constantly, and many people move between all three across a career.

Open compare lab

Share this page

The popular image of a data scientist building clever predictive models is real but incomplete. Practitioner surveys and firsthand accounts consistently describe a job where finding, cleaning and reshaping messy data eats up more hours than the modeling step most people picture.

The craft passed down inside the field is less about memorizing a specific algorithm and more about disciplined skepticism: looking at the data before trusting any model of it, checking whether a pattern holds inside subgroups, and knowing when the honest answer to a stakeholder's question is that the data cannot support one.

What the work demands

857870726258
Statistics and probability
85
Programming (Python, SQL, R)
78
Data wrangling and pipelines
70
Machine learning modeling
72
Communicating findings
62
Business or domain context
58

Statistics and probability

Hypothesis testing, regression, and understanding what a p-value or a confidence interval actually claims — the inferential foundation everything else in the job sits on top of.

Programming (Python, SQL, R)

Writing code fluent enough to pull, clean and transform data at scale, not just prototype an analysis in a notebook that never has to run again.

Data wrangling and pipelines

Turning messy, inconsistent, real-world data — missing values, duplicate records, mismatched formats — into something a model or chart can actually use.

Machine learning modeling

Choosing, training and validating a model appropriate to the problem, and knowing when a simple regression beats an elaborate neural network.

Communicating findings

Translating a statistical result into a chart, a memo or a recommendation a non-technical executive can act on, without oversimplifying or burying the real uncertainty.

Business or domain context

Understanding what a metric actually means inside a specific business or scientific field, so an analysis answers the question that was actually asked.

A day in the life

Standup and dashboard checkData pulling and cleaningLunchModeling and analysisStakeholder meetings and reviewsOff the clock (mostly) 036912151821 24h
  1. 8–9 Standup and dashboard check

    Reviewing overnight pipeline runs and key metrics dashboards, and a short sync with the team on priorities for the day.

  2. 9–12 Data pulling and cleaning

    Writing SQL queries against a data warehouse, joining and reshaping tables, and handling missing or inconsistent values — commonly the largest single block of a working day.

  3. 12–13 Lunch

    A genuine break, and often an informal setting where cross-team problems get raised before they reach a scheduled meeting.

  4. 13–15 Modeling and analysis

    Building or refining a statistical model, running an experiment's significance test, or digging into why a metric moved.

  5. 15–17 Stakeholder meetings and reviews

    Presenting findings to a product or business team, reviewing an A/B test's results, or defending an analysis's assumptions under questioning.

  6. 17–8 Off the clock (mostly)

    Personal time, except around a product launch or a quarterly business review, when evenings can absorb last-minute analysis requests.

The know-how

Craft knowledge practitioners actually pass on — not motivation.

01

Look at the data before you model it

Plot the raw distributions, scatterplots and simple summaries before fitting anything — a habit that catches broken data, unit errors and outliers a model would otherwise quietly absorb and hide.

John Tukey, 'Exploratory Data Analysis,' 1977
02

Check whether the trend survives inside subgroups

An aggregate trend can reverse completely once the data is split by a relevant category — a pattern known as Simpson's paradox, named for a 1951 paper by statistician Edward H. Simpson.

Edward H. Simpson, 1951 paper; phenomenon noted earlier by Karl Pearson and others
03

Hold out a test set and do not look at it until the end

Repeatedly checking performance against the same held-out data, then adjusting the model, quietly leaks information from that data into the model — touching it only once is what keeps a final result honest.

Standard practice, formalized in Hastie, Tibshirani and Friedman, 'The Elements of Statistical Learning,' 2001
04

Budget most of the project for cleaning, not modeling

Real projects consistently run closer to 80% data preparation and 20% modeling than the reverse — planning a timeline around the opposite assumption is a common way projects run late.

Echoed widely since Steve Lohr, 'For Big-Data Scientists, "Janitor Work" Is Key Hurdle to Insight,' New York Times, 2014
05

Ship the simplest model that could plausibly work first

A baseline — sometimes just a rule or a linear model — clarifies how much a more complex model actually adds, and is often good enough to ship on its own.

Martin Zinkevich, 'Rules of Machine Learning: Best Practices for ML Engineering,' Google, rule #4
06

When a pattern looks too good, hunt for the confound

A surprising correlation is more often an artifact of a hidden third variable than a genuine discovery — actively search for what else could explain it before presenting a result.

Rooted in Fisher's experimental-design tradition; formalized in Judea Pearl, 'The Book of Why,' 2018

Tools of the trade

Python (pandas, scikit-learn, NumPy)

The dominant language for data manipulation and classical machine learning, with pandas for tabular data and scikit-learn for standard modeling algorithms.

SQL

The query language for pulling data out of the relational and cloud data warehouses — Snowflake, BigQuery, Redshift — where most companies' data actually lives.

Jupyter Notebook

The standard interactive environment for exploratory analysis, letting a data scientist run code, view a chart and take notes in the same document.

Tableau / Power BI

Business-intelligence dashboarding tools used to turn a finished analysis into something a non-technical stakeholder can explore and monitor without writing code.

Git and cloud platforms (AWS, GCP, Azure)

Version control for code and, increasingly, for models, alongside the cloud infrastructure that stores data and runs training jobs at a scale a laptop cannot handle.

How people fail at it

Testing until something is significant

Running many statistical comparisons and reporting only the one that crosses a significance threshold produces false discoveries that will not replicate — a well-documented failure mode known as p-hacking.

Shipping a model that leaks the target

Accidentally including a feature that encodes the outcome being predicted produces unrealistically strong offline results that collapse once the model runs on genuinely unseen production data.

Building a sophisticated answer to the wrong question

A carefully tuned machine-learning model solving a problem a simple SQL query or spreadsheet formula would have answered just as well wastes effort and can miss the actual business question.

Similar professions

Closest neighbours on the six-score profile — not the same field only.

Continue exploring

Keep exploring

More in Science & Research