What is a good roadmap to learn data analysis?
You Google "how to become a data analyst" and get 50 different roadmaps. Most of them are broken. Here is why, and the project-based approach that actually works.

You Google "how to become a data analyst" and get hit with 50 different roadmaps.
Learn Excel first. No, start with SQL. Actually, Python is more important. Don't forget statistics. Oh, and you need Tableau too.
Confusing? Absolutely.
Here's the truth: most roadmaps are broken. Let's fix that.
Why traditional roadmaps don't work
The typical data analytics roadmap looks like this:
Excel → SQL → Python → Statistics → Viz → ML
Linear. Rigid. One-size-fits-all.
The problem?
Not everyone starts from zero. Not everyone needs the same skills. Not everyone has unlimited time.
If you already know Python, why force you through Python tutorials? If you're interviewing for SQL-heavy roles, why make you learn R first?
A good roadmap adapts to the learner, not vice versa.
Learning by doing: the 42 School approach

Traditional education teaches theory first, practice later. Watch 50 hours of tutorials, then maybe build something.
That's backwards.
The best way to learn data analytics is the same way 42 School revolutionized programming education: project-based learning, where you build real things instead of watching someone else build them.
Here's how it works:
1. No hand-holding
You're given a real project, not a step-by-step tutorial, not a "follow along with me" video. A problem to solve.
Figure it out. Google it. Struggle. Break things. Fix them.
That's how you actually learn.
2. Real projects, not toy problems
Forget the Titanic dataset. Build something that looks like actual work:
- Analyze sales performance data
- Build an executive dashboard
- Clean a messy customer database
- Write SQL queries for real business questions
When you're done, you don't have a certificate. You have a portfolio piece that proves you can do the job.
3. Feedback that's built in
On D8A, every project ends with a deliverable you push to GitHub. The platform validates it automatically and adds it to your live portfolio. No waiting, no guessing whether you did it right, you get a clear signal and a finished piece of work in one move.
Why this works
You don't learn to swim by watching swimming tutorials. You learn by getting in the water.
Data analytics is the same. Watching someone else write SQL doesn't make you good at SQL. Writing SQL makes you good at SQL.
D8A is built on this philosophy. No endless video courses. No theoretical lectures. Just guided projects that build your portfolio as you go.
Choose a path, not a pile of tutorials
Modern data analytics isn't one linear path, and it isn't a vague list of tools either. It's a handful of career directions, each with its own center of gravity. On D8A, you pick one and follow a guided track of projects built for it:
📊 Data Analyst
SQL, dashboards, and storytelling with data. The most accessible entry point into the field, and the foundation everything else builds on.
Best for: Complete beginners and career switchers who want results fast.
🧠 Data Scientist
Python, statistics, and machine learning. Open-ended problems where the answer isn't known upfront.
Best for: People who love math and want to build systems that predict.
🛠️ Data Engineer
Pipelines, warehouses, and the infrastructure that moves data reliably. Closer to software engineering than to analytics.
Best for: People who care more about how the data flows than what it says.
💼 Business Analyst
Requirements, process mapping, and translating between business and tech. Light on code, heavy on clarity.
Best for: Natural facilitators who are strongest in the room with stakeholders.
Not sure which one fits? That's exactly what the quiz is for, answer a few questions about your background and goals, and we'll point you to the right starting path.
How the D8A skill tree works
We built D8A specifically to solve the "one-size-fits-all" problem. Instead of a linear playlist, you get a skill tree of guided projects.
- Choose your path, Data Analyst, Data Scientist, Data Engineer, or Business Analyst. Pick based on YOUR goals, or let the quiz decide.
- Build real projects, each one is based on an actual business scenario. No Titanic datasets. No toy problems.
- Get validated automatically, finish a project, push it to GitHub, and the platform checks your work and marks it done.
- Watch your portfolio fill, every validated project is added to a public, shareable portfolio page that updates as you progress.
- Get hired, by the time you finish a path, your portfolio is your CV. It shows what you can do, not just what you studied.
The biggest mistake people make
Trying to learn everything at once.
You see "learn SQL, Python, R, Tableau, Power BI, stats, ML..." and try to do it all.
Result? You learn nothing well.
Better approach:
- Pick ONE path
- Complete 2-3 projects
- Build something you can show employers
- THEN move to the next skill
Depth beats breadth.
A portfolio with 3 excellent SQL projects is infinitely more valuable than surface-level knowledge of 10 tools.
Common questions
Python or R?
Python: Max job opportunities, data science path, automation. R: Statistical work, academia, research.
Honestly? Start with SQL. It's required for both anyway, which is why every D8A path starts there.
How long to become job-ready?
| Time investment | What you can achieve |
|---|---|
| 3 months (full-time) | One full path + portfolio |
| 6 months (part-time) | One path, deep, with a strong portfolio |
| 12 months (casual) | Multiple paths, broad portfolio |
Timeline matters less than portfolio quality.
What if I get stuck on a project?
That's the point. Getting stuck forces you to problem-solve and research, exactly like real work. The struggle is what makes the learning stick.
The real roadmap
Here's the truth: the best roadmap is the one you actually follow.
Stop optimizing. Start building.
- Pick one path
- Complete one project
- Get it validated
- Improve
- Repeat
That's it.
You don't need the perfect plan. You need to start.
You learn data analytics by doing data analytics. Not by watching. Not by reading. By building, breaking, fixing, and shipping real projects, and ending up with a portfolio that gets you hired. 🚀



