What Is Data Science and What Do Data Scientists Actually Do?

Updated

Data science is the practice of turning raw data into decisions: it combines statistics, programming, and domain knowledge to frame a question, gather and clean data, explore it, model it, and communicate what the results mean. It suits people who are comfortable with ambiguity and want to work at the intersection of analysis and software — and it is not the same as building machine learning models all day, nor does it require a PhD.

The three-part definition, and what it is not

Data science sits where three capabilities overlap:

  • Statistics and probability — knowing what a result means, how uncertain it is, and when a pattern is noise.
  • Programming and data handling — getting data out of systems, reshaping it, and automating repeatable steps.
  • Domain knowledge — understanding the business, scientific, or operational context well enough to ask a question worth answering.

That combination is what separates it from adjacent roles:

Role Main focus Typical output
Data analyst Describing what happened; dashboards and reporting Metrics, reports, visualizations
Data scientist Explaining and predicting; framing questions and testing hypotheses Analyses, models, recommendations
ML engineer Putting models into production reliably Serving infrastructure, pipelines, monitoring

The boundaries blur in practice, especially at small organizations. But if your day is mostly SQL queries and dashboards, you are doing analysis; if it is mostly model deployment and latency tuning, you are doing engineering.

The typical workflow

Most projects follow a recognizable arc, though rarely in a straight line:

  1. Frame the question. Turn a vague request ("why are customers leaving?") into something measurable ("which behaviors in the first 30 days predict non-renewal?"). This step determines everything downstream.
  2. Collect the data. Pull from databases, APIs, logs, files, or sensors. Expect access, permissions, and data-quality problems here more than anywhere else.
  3. Clean and prepare. Handle missing values, duplicates, inconsistent formats, and unit mismatches. This is usually the largest share of the work.
  4. Explore. Summarize distributions, check correlations, and plot the data before modeling. Exploratory analysis frequently changes the question.
  5. Model or test. Apply statistical tests or machine learning where they add value — not by default.
  6. Communicate. Present findings with the uncertainty intact, in language the decision-maker can act on.

A concrete example: a team wants to reduce support ticket volume. Framing it as "which ticket categories have the highest repeat-contact rate?" leads to a clean analysis of existing logs. Framing it as "build a chatbot" skips straight to a solution and usually produces a model nobody can evaluate.

Core skills and tools

Entry-level and near-universal:

  • A language for analysis — Python or R. Python dominates where data science overlaps with software engineering; R remains strong in statistics-heavy and research settings.
  • SQL for querying relational data.
  • Spreadsheets, still the fastest way to sanity-check a small dataset.
  • Basic visualization and the ability to write a clear summary.
  • Version control (Git) and reproducible notebooks or scripts.

Specialized, learned on the job or in later coursework:

  • Machine learning — supervised and unsupervised methods, model evaluation, and the discipline not to overfit.
  • Big-data and parallel tooling for datasets that no longer fit comfortably in memory.
  • Experiment design and causal inference.
  • Domain-specific methods; geospatial work, for instance, needs its own toolchain. GRASS (Geographic Resources Analysis Support System) is an open-source engine for raster, vector, and geospatial processing, with a built-in temporal framework and a Python API for time series analysis and large-scale computation — a good illustration of how a domain pulls in tools beyond the generic stack.

Common misconceptions

  • "It's mostly model building." Modeling is often a small fraction. Cleaning, framing, and communicating dominate.
  • "You need a PhD." Many working data scientists hold master's degrees or come from adjacent roles. A PhD matters mainly for research-oriented positions.
  • "More data always helps." Better-framed questions and cleaner data usually beat more rows.
  • "The model is the deliverable." The deliverable is a decision someone can make with confidence.
  • "It's a solo job." Most work is collaborative with engineers, analysts, and the people who own the problem.

Realistic paths into the field

There is no single gate. Common routes:

  • From analysis: move from reporting to hypothesis testing and modeling, adding Python or R to an existing SQL skill set.
  • From software or engineering: add statistics and experiment design; your data-handling skills transfer directly.
  • From a domain field (finance, biology, operations, GIS): add programming and statistics; domain knowledge is often the hardest part to acquire and your biggest advantage.
  • Formal study: degree programs help with structure and credentials, but a portfolio of finished projects demonstrates capability more directly.

Whatever the route, build a small portfolio of end-to-end projects: a question, the data you gathered, the cleaning decisions you made, the analysis, and a short write-up of what you concluded and what you would do differently. Two or three such projects, documented honestly including their limitations, say more than a long list of completed courses.

Deciding whether it fits you

Choose data science if you enjoy messy problems, are willing to spend substantial time on data preparation, and like explaining results to non-specialists. If you prefer building reliable systems, look toward data or ML engineering; if you prefer fast, well-defined reporting, analytics may be a better fit. The field rewards curiosity and rigor more than any single tool.