Data Scientist Roadmap 2026: A Seven-Month Path from SQL to Offer

This data scientist roadmap takes you from SQL to a job offer in about seven months at 10–14 hours a week. It follows the order interviews test: can you get the data, can you tell whether a result is real, can you model it responsibly, and can you explain it to someone who will act on it.

Most self-study plans over-weight the third and neglect the first and fourth. That mismatch is why capable people fail interviews they should pass, so this roadmap is weighted the way the interviews are.

It is written for analysts, graduates and career changers who can give it 10–14 hours a week. Each of the six stages ends in an exit test, so you know when to move on. The sections after the roadmap add hours per stage, free official resources, portfolio projects that work and what official pay data actually shows.

How long does each stage of the data scientist roadmap take?

The whole plan runs 32 weeks, which at 10–14 hours a week is roughly 320–450 hours. The hours below are simply weeks multiplied by that range.

If you already work as an analyst, stages one and three may take half the time. However, do not skip the exit tests, because they are what the interview will check.

Why does the SQL round stop so many candidates?

If you take one thing from this page, take this: a common point of failure in data science hiring is a live SQL round early in the process.

Not because the questions are exotic. Rather, candidates practised modelling for six months and SQL for six days, then had to write a window function while a stranger watched.

SQL is also simply everywhere. In the Stack Overflow Developer Survey 2025, 58.6% of all respondents said they had done extensive work in SQL over the past year, slightly more than Python at 57.9%.

Five weeks at the start of this roadmap looks disproportionate. It is not. In fact, it is the stage with the highest return per hour in the entire path.

Which free, official resources cover each stage?

You do not need a paid course for any single stage, although you do need a deadline and feedback. As of September 2026, these primary resources cover the ground:

• SQL: the PostgreSQL manual's tutorial on window functions, which is short, precise and exactly what the interview round tests.
• Statistics for data science: OpenIntro Statistics, a free PDF textbook covering inference, categorical data and regression.
• A/B testing and power: the power and sample-size tools in statsmodels, such as TTestIndPower, so that your test design includes a sample-size calculation rather than a guess.
• Python for analysis: the pandas 10 minutes to pandas guide, then the rest of the user guide as you need it.
• Modelling: scikit-learn's common pitfalls page. It defines data leakage and recommends splitting data before any preprocessing and using pipelines.

For deeper SQL practice with the reasoning written out, work through these SQL interview questions and answers.

What should a data science portfolio contain?

Two or three analyses that each end in a recommendation, rather than a folder of modelling notebooks. The portfolio advice for data science is different from software engineering, and people get it wrong by copying the wrong template.

A software portfolio shows you can build. A data science portfolio needs to show you can decide. That means the artefact is not really the notebook — it is the memo at the end that says: here is what I found, here is my confidence in it, here is what I would do, and here is what would change my mind.

Two well-scoped analyses with clear recommendations will out-perform ten polished modelling notebooks in almost every hiring conversation. Some ideas that work well:

1. An experiment readout. Simulate or find an A/B test dataset, compute the power the test needed, then write a recommendation that includes what you would not conclude.
2. A messy public dataset, cleaned honestly. For example, local government or transport data, with every data quality problem logged and its effect on the conclusion stated.
3. A churn or demand model with a business threshold. Choose the metric from the cost of errors, show the leakage checks you ran, and include an error analysis.
4. A decision memo. One page, written for a manager, based on one of the projects above.

How do data science interviews actually screen?

Most processes test the same competencies in a fairly stable order, even though the formats vary by company:

• Screening call and CV review. They look for evidence of analyses, not tool lists.
• SQL round. Usually live or timed, with joins, aggregation and window functions.
• Statistics and experimentation. Hypothesis tests, confidence intervals, A/B test design and common traps such as peeking.
• Case or product sense. "Sign-ups fell 10% last week — what do you check first?"
• Modelling discussion. Metric choice, validation and leakage, often built around your own project.
• Behavioural round. Disagreement, ambiguity and influence without authority.

The round-by-round breakdown in data science interview rounds goes further on each format.

What does a data scientist earn?

The cleanest official figures are American. The US Bureau of Labor Statistics reports a median annual wage of $120,230 for data scientists in May 2025, with 275,600 jobs in 2025, employment projected to grow 35% from 2025 to 2035, and about 24,800 openings a year.

Read the survey rows as a rough guide only, because respondents choose themselves and the India sample is small. No official Indian source publishes data scientist salary bands, which is why the roadmap card does not quote one. For more on what the official figures do and do not show, see data science salary by role.

Which mistakes stall a data scientist roadmap?

Most people who stall on this path make one of a handful of avoidable errors:

• Starting with deep learning. It feels like progress, yet it is rarely what an entry-level interview tests.
• Treating statistics as a formula sheet. Interviewers ask why a test applies, not only how to run it.
• Leaking the target. Scaling or imputing on the full dataset before splitting inflates every score, which a reviewer will catch.
• Portfolios with no conclusion. A notebook that ends in a confusion matrix, rather than a recommendation, shows method but not judgement.
• Applying before the SQL stage is solid. An early SQL failure can close a company's door for months.

Related reading

Still choosing a track? Start with Data Science vs Machine Learning vs AI, or the narrower Data Analyst vs Data Scientist comparison. For course options, see the best data science courses in India, and before paying for a structured programme, read is a data science bootcamp worth it.