Choosing a tech career path: which roadmap is right for you?
"Learn tech" is too big a goal. Nobody gets hired for "tech". People get hired as a web developer, a data analyst, an IT support technician, a security analyst or a mobile app developer. Each of these jobs needs a different set of skills, in a different order.
This subject turns the free lessons on the Marzley Tech learning hub into roadmaps: ordered lists of steps that take you from zero to job-ready (or client-ready, if you plan to freelance). Every step links to the lessons to take and says what to build to prove you can do it.
The method behind every roadmap is the same:
LEARN → PRACTISE → BUILD → SHOW → WORK → EARN
- Learn a skill from the lessons.
- Practise it with the exercises and quizzes until it feels normal.
- Build a real project with it (see the Build real projects subject).
- Show the project: GitHub, a live link, a short write-up, your CV.
- Work: apply for jobs, internships, attachments or freelance gigs.
- Earn, then keep learning the next step on the roadmap.
The roadmaps at a glance
| Roadmap | What you do all day | Good fit if you… | Main tools | Typical first job titles |
|---|---|---|---|---|
| Web developer | Build websites and web apps | like building things you can see, enjoy logic and design | HTML, CSS, JavaScript, PHP or Node, SQL, Git | Junior web developer, front-end developer, WordPress developer |
| Data analyst | Turn messy data into answers and charts | like numbers, patterns and explaining findings | Excel, SQL, Python, Power BI or Looker Studio | Data analyst, M&E assistant, reporting analyst, business analyst |
| Cybersecurity | Protect systems, find and fix weaknesses, respond to attacks | are curious how things break, patient and careful | Networking, Linux, security tools | SOC analyst (tier 1), IT security assistant, security support |
| Mobile app developer | Build Android and iPhone apps | love phones and apps, like visual work plus logic | Dart & Flutter, or Kotlin, or React Native; APIs | Junior Flutter / Android developer |
| IT support & networking | Keep computers, users and networks running | like helping people and solving hands-on problems | Windows, hardware, networking, Microsoft 365 | IT support technician, helpdesk, junior network technician |
Not sure yet? Read the next section, then try the first two weeks of two roadmaps before you commit. The first steps overlap a lot (computer basics, Excel, HTML), so nothing is wasted.
Questions to help you choose
Answer honestly and score each roadmap from 1 to 5:
| Question | Web | Data | Security | Mobile | IT support |
|---|---|---|---|---|---|
| Do I enjoy making things people can see and click? | 5 | 2 | 1 | 5 | 2 |
| Do I enjoy numbers, tables and spotting trends? | 2 | 5 | 3 | 2 | 2 |
| Do I like figuring out how things break? | 3 | 2 | 5 | 3 | 4 |
| Do I like helping people face to face? | 2 | 3 | 3 | 2 | 5 |
| Do I want to freelance for local businesses soon? | 5 | 3 | 2 | 3 | 4 |
| Do I only have a phone right now? | 2 | 2 | 2 | 1 | 2 |
The table is a starting point, not a test. The best predictor of success is which subject you still want to practise on a boring Tuesday night.
Skills every roadmap needs
These are the foundations. Do them first, whichever path you pick:
- Computer basics and typing: what a computer is, files and folders, keyboard shortcuts and typing. Aim for 35+ words per minute.
- Online safety: passwords and 2FA and scams. Employers trust people who don't get phished.
- Professional email and cloud tools: email and Google Drive.
- A CV and cover letter: CVs and letters in Word.
- Git and GitHub (for every technical path): what Git is and GitHub. Your GitHub profile becomes your portfolio.
- Using AI tools well: prompting. AI speeds up learning, but you must still understand what it gives you.
How to study so it actually sticks
- Little and often beats long weekends. One to two focused hours every day is better than eight hours on Saturday.
- Type the code yourself. Copying and pasting feels fast and teaches almost nothing.
- Do every exercise and quiz in the lessons. If you get a quiz question wrong, reread that section.
- Build something after every 4–6 lessons, even if it is small.
- Keep a learning log (a Google Doc or a GitHub README): date, what you learned, what confused you. This is also great material for interviews.
- Join a community: a campus tech club, Ajira Digital centres, Google Developer Groups, local meetups or online communities. Ask good questions: say what you tried and what happened.
A sample weekly timetable (10 hours)
| Day | Time | Activity |
|---|---|---|
| Mon–Thu | 1.5 h | One lesson + its exercise + quiz |
| Fri | 1 h | Review the week's quizzes; fix anything you got wrong |
| Sat | 2 h | Work on your current project |
| Sun | 1 h | Update GitHub/README, write your learning log, plan next week |
Jobs, attachments and freelancing
Every roadmap ends the same way:
- Attachment / internship: if you are a student, apply early. Your projects make your application stand out from classmates who only have grades.
- Entry-level jobs: apply with a one-page CV that links to 2–4 projects. Tailor the CV to each advert's keywords.
- Freelancing: start with people you can reach (family businesses, churches, schools, chamas), deliver well, ask for a testimonial. Follow the step-by-step Freelancing from Kenya subject.
Summary
- Pick a specific role, not "tech".
- Every path follows Learn → Practise → Build → Show → Work → Earn.
- Do the shared foundations first, then follow one roadmap step by step.
- Build projects and publish them; that is what gets you hired.
- Expect months, not weeks, and be wary of anyone promising guaranteed jobs or salaries.
Check yourself
What is the step after BUILD in the roadmap method? (one word)
Show answer
show
Which tool should every technical roadmap use to store and show your code? (one word)
Show answer
Git
True or false: a legitimate employer may ask you to pay a placement fee.
Show answer
false
Roughly how many projects should your CV link to? Write a range like 2-4.
Show answer
2-4