Data Scientist was dubbed "the sexiest job of the 21st century" by Harvard Business Review in 2012. But what does the role actually involve day to day? The answer is: it depends enormously — and often less glamorous than the title implies.

Reality check

Studies consistently show data scientists spend 60–80% of their time on data cleaning and preparation — not on fancy machine learning. The unglamorous work is the real work.

The core responsibilities

A data scientist's work typically spans several activities:

Data Scientist vs Data Analyst vs ML Engineer

RoleFocusKey skills
Data AnalystAnswering business questions with existing dataSQL, Excel, visualisation, statistics
Data ScientistBuilding predictive models and finding hidden patternsPython, ML, statistics, communication
ML EngineerBuilding and deploying ML systems at scalePython, systems engineering, MLOps
Data EngineerBuilding the infrastructure that data flows throughSQL, pipelines, databases, cloud

The typical project lifecycle

  1. Problem definition — what question are we actually trying to answer?
  2. Data collection — where does the relevant data live? How do we access it?
  3. EDA & cleaning — understand and prepare the data
  4. Modelling — build and evaluate candidate models
  5. Insights / deployment — share findings or push model to production
  6. Monitoring — track model performance over time; retrain when needed

The T-shaped data scientist

The best data scientists are "T-shaped": broad knowledge across statistics, coding, and domain expertise, plus deep expertise in at least one area. A data scientist at a hospital who also understands clinical workflows is far more valuable than one who knows only the algorithms.

Key takeaways

  • Data scientists spend most of their time on data cleaning, not modelling
  • The role bridges statistics, programming, and domain expertise
  • Data analysts answer questions; data scientists build predictive systems
  • ML engineers focus on deploying and scaling models in production
  • Communication is as important as technical skill — insights must be acted on