A good tech roadmap for beginners does two things: it tells you what to do this week, and it stops you from wasting time on things that do not matter yet. This 90-day plan is built for complete beginners who are starting from zero and studying part-time, roughly an hour or two most days.
Be clear about what 90 days can and cannot do. It will not make you job-ready in most roles, and you should be wary of anyone who says it will. What it can do is take you from "I don't know where to start" to having a chosen direction, solid foundations, a few small projects on GitHub and a clear plan for the months after. That is a strong position to be in.
Before you start: set yourself up
Spend a day or two on this before day one.
- Equipment. A laptop or desktop is strongly preferred. A phone is fine for reading, not for real practice.
- A study slot. Choose a regular time you can protect, such as early morning or late evening.
- Power and data plan. Know when you are most likely to have power and cheaper data, and download materials then.
- A learning log. A notebook or a simple document where you write what you studied each day. It sounds small, but it keeps you honest.
Days 1 to 14: choose your direction
The biggest early mistake is learning "tech" in general. Spend the first two weeks narrowing down.
Week 1: explore
- Read about a handful of roles: frontend, backend, data analysis, QA, DevOps, security, product management and technical support.
- For each, note what a typical day involves and what you would need to learn.
- Take the free TechDNA assessment. It takes about seven minutes, measures eight thinking traits and ranks your fit across nine roles. Use the results as a starting point, not a final verdict.
Week 2: try before you commit
- Do a short beginner exercise for your top two roles. For example, build a simple web page with HTML, or write a basic SQL query on Kaggle Learn.
- Notice which one you lose track of time doing.
- By day 14, pick one role. Write it at the top of your learning log.
If you are still torn, our guide on which tech career is right for me can help.
Days 15 to 30: foundations everyone needs
Whatever role you picked, these basics will help.
- How computers and the internet work. Files, processes, browsers, servers, DNS and HTTP at a basic level.
- The command line. Moving between folders, creating files and running programs. Our guide to Linux basics for tech careers covers this.
- Git and GitHub. Create an account, learn to commit and push, and put your first files online.
- How to search and read documentation. A skill you will use every day.
Good free resources for this stage include Harvard CS50 (week 0 and week 1 are a strong start), the Linux Journey site and Techera's TechLearnX, whose free foundation courses cover computing, Linux, programming and Git.
Days 31 to 60: core skills for your role
Now go deep on the main skill for your role. Here is what the month might look like for a few common choices.
| Role | Focus for days 31 to 60 | Free resources |
|---|---|---|
| Frontend | HTML, CSS, then JavaScript basics | freeCodeCamp, The Odin Project, MDN Web Docs |
| Backend | One language (Python or JavaScript), then basic APIs | Python.org tutorial, freeCodeCamp, The Odin Project |
| Data analysis | Excel or Google Sheets, then SQL | Kaggle Learn, freeCodeCamp |
| QA | Programming basics, test case design, bug reporting | freeCodeCamp, roadmap.sh QA roadmap |
| Security | Networking, Linux, security basics | TryHackMe (free tier), OWASP |
A weekly rhythm that works for many people:
- Four or five days of learning and exercises.
- One day of building something small with what you learned that week.
- One rest day. Rest is part of the plan, not a failure.
Keep writing in your learning log. At the end of each week, note one thing you understand now that you did not before.
Days 61 to 90: build and show your work
This month is about turning knowledge into proof.
Weeks 9 and 10: your first real project
Build one project without following a tutorial step by step. Keep it small but complete. Examples:
- Frontend: a personal portfolio page that works well on a phone.
- Backend: a simple API that stores and returns notes.
- Data: an analysis of a public dataset with a short written summary of your findings.
- QA: a test plan and bug reports for one feature of a free app.
- Security: write-ups of beginner TryHackMe rooms you completed.
Push it to GitHub with a clear README explaining what it does and how to run it.
Week 11: improve and get feedback
Share your project with a study group, community or friend in tech. Ask one specific question, such as "Is my code easy to read?" or "Does this dashboard answer the question clearly?" Fix what you can.
Week 12: review and plan the next 90 days
- Read back through your learning log.
- List the skills you have and the gaps you still see, using roadmap.sh for your role as a checklist.
- Try a TechDNA role challenge for your target role at beginner level to see where you stand.
- Write a plan for the next three months: more projects, deeper skills and, when you are ready, applications.
What comes after 90 days?
Most people need more time after this roadmap to become job-ready. The next phase usually involves:
- Two or three more substantial projects.
- Deeper knowledge of your main tools.
- A tech CV and LinkedIn profile.
- Interview practice.
- Applying consistently.
For a realistic view of the whole process, read how long it takes to get a tech job.
Common mistakes on a beginner roadmap
- Changing roles every two weeks. Give your choice a fair chance before switching.
- Skipping the boring foundations. They save time later.
- Only consuming content. Build something every week.
- Comparing yourself to people online. You only see their highlights.
- Quitting after a bad week. Missed days happen. Pick up where you left off.
Frequently asked questions
Can I get a tech job after 90 days of learning?
It is unlikely for most complete beginners, and you should be cautious of programmes that promise it. Ninety days is a strong foundation. Plan for a longer runway before you are competitive for jobs.
How many hours a day do I need for this roadmap?
The plan assumes roughly one to two hours on most days. If you have less time, stretch each phase. If you have more, add extra projects rather than rushing ahead.
What if I realise halfway that I picked the wrong role?
That is useful information, not wasted time. The foundations from days 15 to 30 apply to almost every role. Re-read your assessment results, try a short exercise in the new direction and adjust your plan.
Do I need to pay for any courses in the first 90 days?
No. Everything in this roadmap can be done with free resources. Paid courses can add structure or mentorship later, but they are not required to start.
The best roadmap starts with the right direction. Take the free TechDNA assessment to see which roles fit how you think, then use this plan to get moving.