Skip to content
Start with a free 3-minute AI session Try it
All paths

Data & Analytics

SQL, pandas, statistics and visualisation — plus the part that actually gets people hired: turning an analysis into a decision somebody acts on.

6 topics 20 resources 5 projects 92h of material

Finish this and you can take a messy dataset, establish what is true in it, quantify how sure you are, and present it to someone who will not read your code.

  1. SQL foundations

    Beginner

    The single highest-leverage skill in this field. Joins, aggregation and window functions, in that order.

    Build this

    An analysis answered entirely in SQL

    Load a public dataset into Postgres and answer five business questions without leaving SQL — no pandas, no spreadsheet.

    The constraint teaches you how much can be done at the database layer, which is the difference between a query that takes a second and a notebook that takes ten minutes.

    Done when: Five documented queries with their results and a note on what each one tells you.

    Any open dataset with a real schema
  2. Python for data

    Beginner

    pandas for reshaping, NumPy underneath it, and notebooks kept tidy enough that someone else can rerun them.

    Build this

    Clean a genuinely messy dataset

    Find real data — government portals are ideal — with inconsistent dates, duplicate entities and missing values. Clean it, and log every decision you made and why.

    That log is the deliverable. Anyone can call dropna(); explaining why dropping those rows did not bias the result is the actual skill.

    Done when: A reproducible cleaning notebook and a written decision log.

    Open Government Data, India
  3. Warehouses and pipelines

    Advanced

    Where analytics data lives once more than one person depends on it — modelling, transformation and tests that run on a schedule.

    Build this

    A small warehouse with tests that fail loudly

    Take a raw dataset, model it into fact and dimension tables, and add data tests — uniqueness, referential integrity, accepted ranges. Then deliberately corrupt the source and confirm the tests catch it.

    Done when: A modelled warehouse, a passing test suite, and evidence that it catches bad data.

  4. Communicating the analysis

    Intermediate

    The last mile, and the one that decides whether your work changes anything.

    Build this

    One page that changes a decision

    Take your best analysis and compress it to a single page for someone who will not read the notebook: the recommendation first, the evidence second, the caveats honestly stated third.

    Then give it to someone outside the field and ask them what you are recommending. If they cannot say, the page is not finished.

    Done when: A one-page recommendation that a non-technical reader can restate correctly.

Not sure this is your path?

A path is only worth the hours if it is the right one. The counselling session tests the direction you arrived with rather than simply agreeing with it.

Find your direction

Close, but not quite yours?

These nine are fixed on purpose — complete, sequenced, and ready today. If your direction sits between two of them, we will build the path around you instead.

Ask for a custom path