Data Analyst Roadmap 2026: SQL, Spreadsheets, BI, Statistics and Python, in the Order Interviews Test Them
The 2026 data analyst roadmap as a web page: five phases from data literacy to domain specialisation, the eight skill areas with the proof each one needs, five portfolio projects, a weekly operating plan and the checklist to clear before you apply. The same roadmap is available as a PDF.
By Durgesh Yadav — Senior Data Engineer @ 7-Eleven · Updated 27 Sept 2026. Preparation guidance, not a hiring guarantee.
How long does it take to become a data analyst?
Six to twelve months of consistent part-time work, in five phases: spreadsheets and SQL basics in the first four weeks, intermediate SQL and one BI tool by month two, statistics and experimentation by month four, Python and automated reporting by month six, then a business domain and a four-project portfolio between months six and twelve. Each phase ends with a public artifact, which is what interviews check.
What does the 2026 data analyst roadmap look like, phase by phase?
Five phases, each ending in something a recruiter can open. The order matters more than the speed: SQL and spreadsheets come first because every later phase runs on them, and Python comes fourth because an analyst who cannot write the SQL has nothing to automate.
The time ranges assume ten to twelve hours a week. A full-time learner compresses them; a working professional with two evenings a week should double them and not feel behind.
0 to 4 weeks, data literacy and tools: spreadsheets, SQL basics, cleaning, joins, charts, KPI thinking. Proof: a cleaned spreadsheet analysis with business recommendations.
1 to 2 months, SQL and BI: intermediate SQL, Power BI or Tableau, data modelling, dashboard layout, calculated fields. Proof: two dashboards that each answer a stated business question.
2 to 4 months, statistics and analytics methods: descriptive statistics, distributions, confidence intervals, A/B testing, cohorts, funnels, segmentation. Proof: a published A/B test or cohort analysis notebook.
4 to 6 months, Python and automation: pandas, visualisation, notebooks, data validation, scheduled reporting, APIs. Proof: a weekly report automated from raw data to charts.
6 to 12 months, domain specialisation and portfolio: product, finance, marketing, operations or risk analytics, plus stakeholder storytelling. Proof: four polished case studies with memos, dashboards and SQL.
Which skills come first: SQL, spreadsheets or a BI tool?
SQL first, spreadsheets alongside it, BI once you can shape a table. Analyst interviews screen on SQL before anything else, and in PrepNPlaced's review of 328 Indian analytics job descriptions more than 80% named it. Excel appeared in 81% of the same postings, which is why the roadmap does not treat it as beneath you: the first month is spent in a spreadsheet on purpose.
Each skill area below has one proof attached. Build the proof; the topic list is only there to tell you what the proof has to contain.
SQL for analysts: select, filter and sort, joins, CTEs, window functions, dates, cohorts, funnels, retention, pivoting, null handling, duplicates, performance basics. Proof: solve 100 SQL questions and annotate the business logic of each.
Spreadsheets: cleaning, lookup functions, pivot tables, Power Query, charts, scenario modelling, conditional formatting, validation, financial models. Proof: a spreadsheet dashboard with its assumptions and checks visible.
BI and dashboard design: Power BI, Tableau or Looker, star schemas, calculated metrics, filters, drilldowns, layout, accessibility, refreshes, row-level security. Proof: dashboards that support one specific decision each.
Power BI or Tableau?
Power BI, unless the job descriptions you are targeting say otherwise. In the same 328-posting review, 43% named Power BI and 2% named Tableau. Learn Power BI properly, then spend a weekend on Tableau so neither keyword blocks you.
What 'intermediate SQL' means here
You can write a query with two CTEs and a window function without looking anything up, explain what each join does to the row count, and say which of your queries would be slow on a table a thousand times bigger.
How much statistics does a data analyst need, and what for?
Enough to run and read an experiment, and enough to stop a wrong conclusion. That is a shorter list than a statistics degree: descriptive measures, distributions, sampling, confidence intervals, hypothesis tests, A/B tests, statistical power, bias, and the difference between correlation and causation.
The business-analytics layer sits on top. KPI trees, revenue, margin, CAC, LTV, retention, churn, funnels, cohorts, segmentation, product events and user journeys are what the statistics get applied to, and the interviewer's case question is usually one of them.
Statistics and experimentation proof: a plain-English experiment readout that a product manager could act on.
Business and product analytics proof: a KPI tree for one business model, from the top-line number down to the levers a team controls.
Read Khan Academy Statistics for the foundations and 'Causal Inference for the Brave and True' (free) once A/B tests start to feel easy.
When does Python enter the roadmap, and how much of it?
Month four, and only the analyst's slice of it: pandas for cleaning, joins and groupby, a plotting library, notebooks, reading from an API, and writing a script that can be rerun end to end. Software engineering topics such as classes, packaging and web frameworks are not on this roadmap. Python appeared in 41% of the reviewed Indian analytics postings and tends to mark the better-paid ones, so it is worth the two months.
AI-assisted analysis is the eighth skill area, not a shortcut around the other seven. Use it to draft SQL, suggest cleaning steps and generate charts, and keep every number auditable: the roadmap's rule is that a project must show you understood, tested and could debug the output.
Python or R for analysis: pandas or dplyr, data cleaning, joins, groupby, visualisation, notebooks, APIs, reproducibility, basic automation. Proof: a notebook that reruns end to end on a fresh machine.
AI-assisted analysis: prompting for SQL, data-cleaning suggestions, chart generation, validation checks, hallucination risk, reproducible notebooks. Proof: an analysis where the assistant's output is visibly checked.
Storytelling and stakeholder communication: executive summary, chart selection, caveats, recommendations, prioritisation, data limitations. Proof: one analysis turned into a one-page decision memo.
Which portfolio projects prove you are job-ready?
Five, each with a README, a diagram, setup steps, screenshots, a demo link where possible, checks, stated limitations and a next-steps list. An interviewer opens the repo; the README is the interview. Pick different business domains for the dashboards so the portfolio does not read as one project done five times.
Sales performance dashboard: revenue, margin, products, regions and trends. SQL, Power BI or Tableau, Excel. Stretch: executive recommendations with caveats.
Product funnel analysis: acquisition, activation, retention and churn. SQL, Python, BI. Stretch: segment by channel and cohort.
A/B test readout: experiment impact and confidence. Python or R, statistics. Stretch: a decision memo for leadership.
Customer churn analysis: churn drivers and high-risk segments. SQL, Python, BI. Stretch: three retention actions.
Automated reporting pipeline: a weekly report refreshed from raw files or an API to a dashboard. Python, Sheets or Excel, BI. Stretch: data validation checks.
The portfolio checklist before applying
Three dashboards across different business domains, three SQL notebooks or files with explanations, one A/B test or causal analysis memo, one automated reporting project, and a public portfolio page with context, screenshots, methodology and recommendations.
Resume keywords, when they are true
SQL, Excel or Google Sheets, Power BI, Tableau or Looker, basic Python or R, statistics, experimentation, dashboard design, data cleaning, business KPIs, storytelling and presentations. The condition is in the heading: a keyword you cannot defend for ten minutes costs you the interview it earned.
How do you run the week, and how do you know when to apply?
Ten to twelve hours a week, split so that building beats watching: 60% project implementation, 20% documentation, 10% videos or a course for intuition, 10% notes and revision. Minimum weekly output is five commits, one written note, one demo screenshot or video, and five to twenty practice problems.
Every Sunday: review blockers, update the README, write what you learned, plan the next week, and compare your progress against three target job descriptions. Every month, ship one small project or one milestone of the capstone. Apply when the portfolio checklist above is complete, not when the course ends.
Interview preparation: SQL questions with joins, windows, cohorts and date logic; case questions that choose KPIs and diagnose a business problem; dashboard critique and storytelling; confidence intervals, A/B testing and bias; behavioural stories about influencing a decision and handling ambiguous data.
Use videos for intuition and demos, official documentation for correctness, practice platforms for repetition, and projects for proof.
Track a weekly scorecard: hours, problems solved, commits, notes written, demos recorded, applications and interviews.
Related Guides
Keep Preparing
Move between roadmaps, interview questions, and tools without losing your preparation thread.
Can I become a data analyst without a degree or experience?
The roadmap does not require either; it requires the five proofs. Hiring managers open dashboards and SQL files, and a candidate with three domain-specific dashboards, a written A/B readout and an automated report has more to show than most graduates. A career switcher's existing domain (support, operations, sales, finance) is an advantage in phase five, because the analysis reads like it came from someone who knows the business.
Should I learn Python or R?
Python, for the Indian market. It appears in 41% of the analytics postings PrepNPlaced reviewed and is the language the automation and AI-assisted phases assume. R remains a fine choice for the statistics phase if a target employer uses it, and the roadmap lists dplyr alongside pandas for that reason.
Power BI or Tableau first?
Power BI. In a review of 328 Indian analytics job descriptions, 43% named Power BI against 2% for Tableau. Learn Power BI to the point of building a star schema and writing DAX measures, then spend a weekend on Tableau so the keyword is true on your resume.
How many hours a week does the roadmap assume?
Ten to twelve, with 60% of that spent building projects. At that pace the five phases run six to twelve months. With two evenings a week, double the calendar time rather than skipping phases; the proofs are the point, and each one takes the hours it takes.
Which business domain should I specialise in?
The one you already understand or the one your target companies hire for: product, marketing, finance, operations, risk or people analytics. The roadmap puts specialisation in months six to twelve so that the earlier dashboards can be rebuilt for that domain. A generic portfolio competes with everyone; a fintech risk portfolio competes with far fewer people.
Is the roadmap free, and where is the PDF?
Yes. This page is the web version of the free PDF prepared on 31 May 2026, linked in the secondary button above and on the 2026 Tech Career Roadmaps page, which also carries a Top 50 Data Analyst Interview Questions deck. The paid Data Analytics cohort follows the same order over 18 live classes.
Next Step
Turn The Guide Into Practice
Use PrepNPlaced tools to turn this learning path into resume proof, targeted practice, and interview-ready explanations.