RoadmapsWeek-by-week routes to a career goal

A roadmap that actually gets you success.

Learning from scattered tutorials leaves you with no order, nothing to show and no finish line. Every roadmap here is one route to one goal: what to learn each week, what to build, and how you know you are done.

Browse roadmapsRead a free sample

Reading a sample needs no account.

ONE ROUTE, WEEK BY WEEKbuildsuccess,not just notesROADMAPBACKENDPRODUCTIONAI COREAGENTSCLOUDCAPSTONESUCCESS

01The roadmaps

Pick the route that fits your goal.

Each roadmap is a finished route: a week-by-week plan, a project at every milestone and a checklist that tells you when a week is done. The paths on the shelf are the ones developers are actually choosing.

30 roadmaps · 1 ready to read, 29 coming soon

01 / 30Ready to read

Full stack AI development

For frontend developers who want to build and ship AI products.

  • 30 weeks
  • ~1,200 hours
  • 5 milestones

AI engineer is the fastest-growing job on LinkedIn’s 2026 listLinkedIn Jobs on the Rise 2026

View roadmap
02 / 30Coming soon

Full-stack web developer

For people who want to build a whole web product, from database to screen.

The most common developer role: 27% of respondentsStack Overflow Developer Survey 2025

03 / 30Coming soon

Backend engineer

For developers who want APIs, databases and deployment to feel routine.

The second most common role: 14.2% of respondentsStack Overflow Developer Survey 2025

04 / 30Coming soon

Frontend engineer

For developers who want to build fast, accessible interfaces at scale.

A core path in Pluralsight’s 2026 software career guidePluralsight, software developer career paths 2026

05 / 30Coming soon

DevOps and cloud engineer

For engineers moving into AWS, Terraform, CI/CD and on-call work.

DevOps and DevSecOps both have their own role roadmaproadmap.sh

06 / 30Coming soon

Data engineer

For developers who want the pipelines and warehouses behind every dashboard.

Its own role in the Stack Overflow survey since 2019Boot.dev analysis of Stack Overflow surveys

07 / 30Coming soon

Mobile app developer

For developers who want to take an Android or iOS app from first screen to store.

Android and iOS each have their own role roadmaproadmap.sh

08 / 30Coming soon

Machine learning engineer

For developers who want to train, evaluate and ship models, with the maths they need.

AI and ML roles lead LinkedIn’s 2026 rising-jobs listLinkedIn Jobs on the Rise 2026

09 / 30Coming soon

Security engineer

For developers who want threat modelling, secure code and incident response.

Cyber Security, DevSecOps and AI Red Teaming each have a role roadmaproadmap.sh

10 / 30Coming soon

Software architect

For senior developers who want system design, trade-offs and technical leadership.

The fourth most common role: 6.1% of respondentsStack Overflow Developer Survey 2025

11 / 30Coming soon

AI engineer (LLM apps)

For developers who want the shortest route to building and shipping LLM features.

AI engineer is the fastest-growing job on LinkedIn’s 2026 listLinkedIn Jobs on the Rise 2026

12 / 30Coming soon

AI agent developer

For developers who want agents that use tools, MCP and several models to finish real tasks.

13 / 30Coming soon

RAG and search engineer

For developers who want embeddings, vector search and retrieval that returns the right answer.

14 / 30Coming soon

LLMOps and AI evaluation engineer

For engineers who want to test, monitor and cost-control AI features in production.

15 / 30Coming soon

AI consultant and solutions engineer

For people who want to scope AI work for clients and build the first working version.

AI consultant or strategist is the second fastest-growing job on LinkedIn’s 2026 listLinkedIn Jobs on the Rise 2026

16 / 30Coming soon

Prompt and AI automation specialist

For people who want to automate real work with prompts, workflows and a little code.

17 / 30Coming soon

Data analyst

For people who want to turn data into answers with SQL, spreadsheets and dashboards.

Data and analytics is one of five fastest-growing skill stacks in IndiaLinkedIn Skills on the Rise 2026 (India)

18 / 30Coming soon

Data scientist

For people who want statistics, modelling and experiments that change a decision.

Data science ranks second among skills India’s global capability centres hire forTaggd, India GCC skills in demand 2026

19 / 30Coming soon

Analytics engineer

For analysts and engineers who want clean, tested warehouse models with dbt and SQL.

20 / 30Coming soon

MLOps engineer

For engineers who want to deploy, monitor and retrain models without drama.

21 / 30Coming soon

Platform engineer

For engineers who want to build the internal tools and paved roads other developers deploy on.

Platform engineering ranks fourth among skills India’s global capability centres hire forTaggd, India GCC skills in demand 2026

22 / 30Coming soon

Site reliability engineer (SRE)

For engineers who want uptime targets, observability and calm incident response.

23 / 30Coming soon

Cloud engineer (AWS)

For engineers who want to design, secure and run workloads on AWS.

24 / 30Coming soon

Kubernetes and cloud-native engineer

For engineers who want containers, clusters and operators to feel routine.

25 / 30Coming soon

Cybersecurity analyst (SOC)

For people who want to detect, triage and respond to threats in a security operations centre.

IT and cybersecurity is one of five fastest-growing skill stacks in IndiaLinkedIn Skills on the Rise 2026 (India)

26 / 30Coming soon

Cloud security engineer

For engineers who want to lock down identities, networks and data in the cloud.

27 / 30Coming soon

AI security engineer

For security and AI engineers who want to defend against prompt injection and model abuse.

28 / 30Coming soon

QA and test automation engineer (SDET)

For testers and developers who want automated tests, CI gates and quality ownership.

29 / 30Coming soon

Python backend developer

For developers who want FastAPI or Django APIs, databases and deployment in one route.

30 / 30Coming soon

Embedded and IoT engineer

For developers who want to program devices, sensors and connected hardware.

Do not see your goal?

Describe it in one sentence and the assistant writes a roadmap for you. Change it the same way, then add any week to your study plan.

Have one written for me

02Progress tracking

Finish a day, and the roadmap keeps count.

Your Study plan is the only tracker. Add a roadmap to it and weeks, milestones and percentages follow from the days you finish.

  • 01

    The Study plan is the only tracker

    Add a roadmap to your Study plan and every study day becomes a session. Finish a day there, or on the roadmap page, and it counts everywhere.

  • 02

    Weeks and milestones complete themselves

    A week is done when all its planned days are. A month or milestone is reached when its weeks are. Nothing to tick by hand.

  • 03

    Never a misleading zero

    A roadmap you have not added shows "Add to Study plan", not 0%. A week you left out of the plan reads "not in plan".

  • 04

    Mark what you have learned

    Tick "I have learned this" on any subtopic. Those marks feed the skill map and the topic count.

70%

Your progress

Backend developer in 20 weeks

Next: Week 4 · day 4

Example
Week 1 · Python fundamentalsDone
Week 2 · HTTP and the webDone
Week 3 · REST API designDone
Week 4 · SQL, auth and tests3/6
Week 5 · Relational design and ORMs0/6

Finishing a day in your Study plan fills in the week, the month and the milestone.

03Multiple views

One roadmap, three ways to see it.

Read it as weeks, or open the big pictures: the skill map, the swim lanes and the milestone tracker.

1 / 3

See what leads to what.

Every topic is a box, laid out so what you need first is on the left and what it unlocks is on the right. Hover one to light up its prerequisites and what it opens; click to see its weeks and subtopics.

Python fundamentals#1Git and the commandline#2HTTP and the web#3REST API design#4SQL and relationaldesign#5Auth and sessions#6Testing#7ORMs and migrations#8NoSQL and documentstores#9Caching with Redis#10Queues andbackground jobs#11Docker#12CI/CD pipelines#13Logs, metrics andtraces#14Errors andresilience#15Cloud fundamentals#16Infrastructure ascode#17Security essentials#18Scaling andperformance#19System design#20Event-driven design#21Search at scale#22Capstone project#23Interviews and jobsearch#24
  • Foundations
  • Data and APIs
  • Production
  • Cloud and scale
  • Capstone and jobs
  • Specialist tracks
  • Learn first (on hover)
  • Opens up (on hover)

Topic 19 · Cloud and scale

Scaling and performance

In the weekly plan

16

Learn first

Opens up

Subtopics

  • Profiling
  • Read replicas
  • Horizontal scaling
  • Load testing

Drawn from an example roadmap, Backend developer in 20 weeks. Every roadmap on the site has the same views.

04Custom roadmaps

Not listed? Have the assistant write yours.

Describe your goal in a sentence. You get a week-by-week roadmap in the same shape as the others, and you change it by asking.

  • 01

    Describe a goal in a sentence

    Ask for "a roadmap for AWS Solutions Architect in 10 weeks". The assistant plans it and opens it.

  • 02

    Every week written for you

    Each week gets a day-by-day plan, a project task and a done-when list, in the same shape as the built-in roadmap.

  • 03

    Change it by asking

    Say "make week 3 lighter" and a confirm card shows the change before it is made.

  • 04

    Same views, same tracking

    Flow chart, week pages and progress all work. Add it to your Study plan to track it. Copy a public roadmap, or share yours by link.

05The route

Every roadmap is one route, week by week.

Every station is a week. Each milestone is a working piece of the same product, so you finish with something real to show. Here is an example: Backend developer in 20 weeks.

MONTH 1FoundationsMONTH 2Data and APIsMONTH 3ProductionMONTH 4Cloud and scaleMONTH 5Capstone and jobsWeek 1: Python fundamentalsSTART1Week 2: HTTP and the web2Week 3: REST API design3Week 4: SQL, auth and tests · Milestone 1M14Week 5: Relational design and ORMs5Week 6: Migrations and NoSQL6Week 7: Caching with Redis7Week 8: Queues and background jobs · Milestone 2M28Week 8A: Track A · Event-driven design8AWeek 9: Docker9Week 10: CI/CD pipelines10Week 11: Logs, metrics and traces11Week 12: Errors and resilience · Milestone 3M312Week 13: Cloud fundamentals13Week 14: Infrastructure as code14Week 15: Security essentials15Week 16: Scaling and system design · Milestone 4M416Week 16A: Track B · Search at scale16AWeek 17: Capstone: build17Week 18: Capstone: harden18Week 19: Capstone: ship and write up19Week 20: Interview loop and offers · Milestone 5M520APPLICATIONS STARTFoundationsWeeks 1–4Data and APIsWeeks 5–8AProductionWeeks 9–12Cloud and scaleWeeks 13–16ACapstone and jobsWeeks 17–20
FoundationsData and APIsProductionCloud and scaleCapstone and jobsSpecialist tracksMilestone: a working piece of the product

06Where this takes you

Every roadmap says what you will, and will not, be able to do.

A roadmap that promises everything teaches nothing. Each one states its outcome and its limits up front. Example:

You will

  • Build, test and ship a real backend service of your own, live in the cloud
  • Design a database, an API and the jobs behind it, and explain the trade-offs
  • Run what you build: logs, alerts, deploys, rollbacks
  • Solve about 90 coding problems and practise about 10 system designs
  • Finish with a portfolio piece, a case study and a first round of applications

You will not

  • Make you an expert in every tool you meet
  • Replace years of work on a large codebase
  • Teach machine-learning research or front-end design
  • Promise a job on a fixed date

07Where the hours go

Every roadmap budgets your hours.

You see the total before you start, and how it splits across areas. The example is about 880 hours over 20 core weeks and 2 track weeks.

160 h160 h160 h160 h160 h80 h

Foundations

160 hours · Weeks 1–4

Python, HTTP, REST, SQL, auth

Data and APIs

160 hours · Weeks 5–8

ORMs, NoSQL, Redis, queues

Production

160 hours · Weeks 9–12

Docker, CI/CD, observability

Cloud and scale

160 hours · Weeks 13–16

Cloud, IaC, security, scaling

Capstone and jobs

160 hours · Weeks 17–20

Capstone, interviews, applications

Specialist tracks

80 hours · Weeks 8A, 16A

Events, search

08The day

A study day that is planned, not guessed.

Move the times to suit you, but keep the order. Reading and watching stay a minority of the day; most of it is building.

09:0010:0011:0012:0013:0014:0015:0016:0017:0018:00Plan: Three goals for the day (09:00–09:15)Learn: Read docs, notes (09:15–11:15)LearnRead docs, notesDo 1: Small exercises (11:30–13:30)Do 1Small exercisesLunch (13:30–14:30)LunchDo 2: Bigger exercise, main project (14:30–16:30)Do 2Bigger exercise, main projectPractice: One coding problem (16:45–17:30)PracticeClose: Commit code, learning log (17:30–18:00)THE 30 / 70 RULERead and watch: at most 30%Type, run, break, fix: at least 70%Learn block 2 h · Do blocks 4 h · Plan, practice and close 1.5 h

09Inside every roadmap

Everything a roadmap comes with.

Every roadmap is built the same way, so you can start any of them and know how it works.

A route of weeks

Every roadmap is a list of weeks in order, grouped into months, with a milestone at the end of each stage.

Every week, day by day

A day-by-day plan, a project task, check-yourself questions and a done-when list on every week page.

Topics and subtopics

Read the same content by topic as well as by week: the weekly plan is the schedule, the topics are the map.

Flow chart, skill map, swim lanes

See the whole plan as one picture: the weeks with their days, what leads to what, and the rhythm over time.

Into your study plan

Press Add to Study plan on any week and its days go into your calendar.

Progress that tracks itself

Put the roadmap in your Study plan and finish each day there. Weeks and milestones complete themselves.

A real project

Milestones build one product step by step, so you finish with something working to show.

A job track alongside

Coding problems, system design, portfolio, resume and an application plan, a little each week.

An honest note

A roadmap gives you skills and proof. It cannot promise a job on a fixed date: hiring depends on the market, your location and your past experience. And if you fall behind, which is normal, a good roadmap lists what you may cut and what you must never cut.

?Questions

Before you start

What do I get with a roadmap?
A week-by-week route to one goal. Every week has a day-by-day plan, a project task and a "done when" checklist, and every roadmap can be read by week, by topic or as a picture.
Can I see one before I commit?
Yes. A roadmap’s own page shows its full month-by-month route, what you will be able to do, and a glimpse of its planning views before you buy. A roadmap someone else made with the assistant and shared or listed publicly can be read in full without an account; you need one to save a roadmap and keep your progress on it.
What if my goal is not listed?
Describe your goal in a sentence and the assistant writes a roadmap for it; change it the same way. You can also copy a public roadmap and edit your copy.
Will a roadmap get me a job?
A roadmap gives you skills and proof of work. It cannot promise a job on a fixed date, because hiring depends on the market, your location and your past work.
How does it connect to the study planner?
You can add any week of a roadmap to your study plan, so the work gets dates. Finish a day there and the roadmap keeps count.

Start with one topic. Keep going.

3 topics are finished end to end and 5 more are being written in the open. Every cheatsheet is free to read; sign in to plan, take notes and track jobs.

Get startedStart with Python