A complete, honest roadmap for the skills data analysts actually use, from spreadsheets and SQL through statistics, data cleaning, visualization, business understanding, storytelling, a programming language, and AI-assisted analysis. It runs top to bottom, foundational to advanced, so you always know what comes next. Free to read, no signup required.
How to use this: tap a step on the map to open its details, skill pills, and guidance in a side panel. Work down the spine in order; each stage assumes the ones above it. Aim for working competence and analyse real data as you go, because the technical skills only click once you’ve used them to answer an actual question.
Do a real end-to-end analysis
Nothing proves you can analyse data like an analysis you actually did. A complete project, from a messy dataset to a clear recommendation, is the centrepiece of any data-analyst portfolio and the thing interviewers dig into.
Take a public dataset, clean it, query it with SQL, and build a dashboard that answers a real question.
Write a short business narrative: the question, what you found, and what you’d recommend.
Analyse something you personally care about, because your own data makes for a more convincing story.
Reproduce a company metric (e.g. monthly active users, conversion) from raw data end to end.
Publish it: a dashboard link plus a written narrative of your reasoning. The write-up matters as much as the chart, because it shows how you think, which is what a hiring manager is really buying.
Frequently asked questions
You need practical, applied statistics (averages, distributions, correlation vs causation, sampling, and enough about significance to avoid over-reading noise) far more than advanced or theoretical maths. Most day-to-day analysis is careful reasoning about data, not heavy computation.
SQL. It’s the most requested technical skill in data-analyst roles because nearly all business data lives in databases. Spreadsheets and clear communication matter enormously too, but if you’re prioritising one technical skill, make it SQL.
It depends far more on consistent practice and real projects than any fixed timeline. With focused effort on SQL, spreadsheets, statistics, and visualization, plus a couple of end-to-end analysis projects, many people reach entry-level readiness in a matter of months. The exact time varies widely by background.
No specific degree is required, and this field is strongly portfolio-driven. Analyses you’ve actually done, with a clear write-up, carry more weight than most certificates. A degree or certification can help pass some hiring filters, but demonstrated ability is what interviews test.
Not to start. You can get a long way and land roles with strong SQL, spreadsheets, statistics, and a BI tool. A programming language becomes valuable as you handle bigger data, automate repetitive work, and move toward more technical or analytics-engineering roles.
No. SQL, spreadsheets, statistics, data cleaning, visualization, and communication are the core. Experimentation, a programming language, and data-warehousing awareness you deepen as your role demands. Nobody is equally strong across all of it.
Ready to prepare for real interviews with a personalized plan?
This roadmap is the map. When you’re ready to actually get hired, Interview Ready turns it into a personalized 30-day plan built around your resume and a specific target role: real practice in the right order (SQL, case studies, behavioural), a guided project track alongside it, and progress tracking the whole way. Start free.
