Full-stack web developer
Learn to build, test and ship a whole web product, with AI tools in your daily work and AI features inside the product, in 24 weeks.
Coming soon · planned, not written yet
The most common developer role: 27% of respondentsStack Overflow Developer Survey 2025
- 24
- weeks planned
- ~40 h
- a week
- 6
- milestone projects
- 1
- project, grown every week
These are planned figures. The weeks are written after we check the tools against current job postings and official documentation, so the final route may differ.
Built for the AI era
How AI fits this roadmap
AI coding assistants and agents can now draft code, so a full-stack developer needs to direct them, read what they produce and test it before it ships. This roadmap teaches that from week 1: you write the specification, review every change, and learn when to distrust the output. You also build AI features into a real product, such as a model-backed assistant with tests around it.
The main project
TeamBoard
A multi-user work-tracking web app with sign-in, a database, tests and a live deployment, which gains an AI assistant that summarises and drafts tasks.
What you will be able to do
- 01
Build responsive pages with HTML, CSS, TypeScript and React, and check them on a phone and a laptop.
- 02
Write a Node.js API backed by a PostgreSQL database, with sign-in, validation and clear error handling.
- 03
Direct an AI coding assistant on a feature, then review, test and correct its output before merging.
- 04
Cover your app with unit tests and end-to-end browser tests, and run them on every push.
- 05
Deploy TeamBoard with an AI assistant feature, and write a short note on where the assistant fails and how you guard against it.
01The route
Six months, one month at a time.
Each month ends in a milestone project, so you always have something to show for the work.
Month 1 · Weeks 1–4
Web foundations and AI-assisted coding
HTML, CSS, modern JavaScript and Git, with an AI coding assistant used from the first day. You learn to write clear prompts, read diffs and spot wrong answers.
MilestoneA responsive static site, published online, with a short log of AI suggestions you accepted and rejected
Month 2 · Weeks 5–8
TypeScript and React
Types, components, state and forms. You use an assistant to draft components, then fix and simplify them by hand.
MilestoneThe TeamBoard front end with task lists and forms, running against sample data
Month 3 · Weeks 9–12
Servers, APIs and PostgreSQL
A Node.js API, relational data design, SQL and migrations. You review AI-written queries for correctness and safety.
MilestoneTeamBoard reading and writing real data through your own API
Month 4 · Weeks 13–16
Accounts, Next.js and security basics
Sign-in, sessions, permissions, server rendering with Next.js, and common web security mistakes, including those AI tools repeat.
MilestoneA multi-user TeamBoard where each person sees only their own team
Month 5 · Weeks 17–20
Testing and delivery
Unit tests, browser tests with Playwright, automated checks on every push and a live deployment. You learn to have AI draft tests, then check that they test something real.
MilestoneTeamBoard live online, with tests that run automatically before each release
Month 6 · Weeks 21–24
AI features and capstone
Call a language model from your back end, stream answers to the screen, handle failures and cost, and test model output. Then portfolio write-up and interview practice.
MilestoneAn AI assistant inside TeamBoard, a portfolio write-up and a working application plan
03What is inside
Everything a week comes with.
Every week is built the same way, so once you have done one you know how all of them work.
- 01
One project, TeamBoard
You grow one product from an empty folder to a live app with an AI feature, so every tool lands in something real.
- 02
A day-by-day plan
Each week has a Learn part and a Do part, with a checklist so you know when you are done.
- 03
A project in every milestone
Six milestones, each ending in something you can show and link to.
- 04
Reference topics
Short topic pages with check questions you can come back to, including how to review AI-written code.
- 05
A job track
Interview practice, portfolio and resume help, and an application plan.
- 06
Progress in your Study plan
Add weeks to your Study plan, give them dates, and finished days are counted for you.
04Is it for you
Who this is, and is not, for.
Better to know before you start than six weeks in.
It is for you if
- You can write small programs in some language and want to build complete web products.
- You are a front-end or back-end developer, or a career changer with some coding practice, who wants the whole stack.
- You can give about 40 hours a week for six months. If you can only give less, plan for a longer calendar.
It is not for you if
- You have never written code. Do a beginner programming course first.
- You want a job guarantee. Nobody can promise that, and this roadmap does not.
- You want AI to build everything while you skip learning how the code works. Reviewing AI output needs the fundamentals, so this roadmap teaches both.
?Questions
Before you start
- Is this roadmap ready?
- Not yet. This is the plan. The weeks are being written and checked against current job postings and official documentation. Leave your email and we will write to you when it opens.
- What will it cost?
- The price is not set. Roadmaps are bought once, with no subscription. We will announce it when this one opens.
- Will the plan change?
- It may. Before the weeks are written we check the tools against current job postings, so the lengths and months here are planned, not final.
- Will it get me a job?
- It will give 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.
- Do I need to pay for AI tools?
- Not necessarily. The plan is tool-neutral: any current AI coding assistant works for the daily practice. If a week needs a paid model key for the AI feature, the roadmap will say so and show how to keep usage small.
Not open yet
Leave your email and we will write once, when it opens.