Scrimba 6-Month Study Plan
Quick answer: At 10 to 15 hours per week, the Frontend Developer Path (about 81.6 hours) typically lands in 4 to 6 months. Recent BLS wage releases still show web and software roles as strong-pay tracks, and Scrimba Pro stays well below typical bootcamp price ranges (see the official pricing page (opens in a new tab)). This page maps that pace week by week so "how long?" stops being a vague worry.
Last reviewed: May 2026.
Quick verdict
If you want a week-by-week template for finishing the Frontend Developer Path on a day-job schedule, this is the page. It assumes you have already decided Pro is worth paying for and now need a calendar.
Read this page if
You are a career changer with a day job, a parent stealing hours after the kids are down, or anyone who needs proof you can hold a schedule long enough to reach hireable projects. The whole plan is built on one assumption: steady weekly hours beat heroic weekends. The main route this plan supports is the Frontend Developer Path; the Fullstack Path adds roughly two months.
Skip this page if
You are looking for an absolute-beginner intro. Start with Scrimba for Beginners first. If you already write production code and just need to plug a gap, the CS Students guide has a tighter 12-week sketch.
Pick a pace you can actually keep
| Pace | Hours per week | Time to complete Frontend Path | Best for |
|---|---|---|---|
| Intensive | 20 to 25 | About 3.5 months | Full-time learners, career changers on a deadline |
| Steady | 10 to 15 | About 6 months | Part-time learners, people with day jobs |
| Relaxed | 5 to 8 | About 10 months | Casual learners, exploring whether coding fits |
Most readers should aim for Steady. It survives a sick week, a wedding weekend, and a deadline at the day job, which is more than a 25 hour pace usually does.
The 6-month plan (steady pace)
This plan maps to the Frontend Developer Path (about 81.6 hours, 13 modules). If you switch to the Fullstack Path (about 108.4 hours), add roughly two months.
Month 1: Foundations
| Week | Module | Hours | Milestone |
|---|---|---|---|
| 1 | Welcome and web dev basics (pt 1) | 3 to 4 | First HTML page |
| 2 | Web dev basics (pt 2) | 3 to 4 | Style a full page with CSS |
| 3 | Making websites interactive (pt 1) | 4 to 5 | First JavaScript functions |
| 4 | Making websites interactive (pt 2) | 4 to 5 | First solo project |
Goal: read an HTML document, style it with CSS, and wire up basic JavaScript. You should be able to build a simple interactive page from a blank file.
Month 2: Core skills
| Week | Module | Hours | Milestone |
|---|---|---|---|
| 5 | Making websites interactive (pt 3) | 4 | DOM manipulation confidence |
| 6 | Accessible development | 3 | ARIA and semantic HTML |
| 7 | Essential CSS concepts (pt 1) | 3 | First CSS Grid layout |
| 8 | Essential CSS concepts (pt 2) | 3 | Flexbox plus CSS variables |
Goal: rebuild a layout you see on the web from screenshot to working page without copying markup.
Month 3: JavaScript depth
| Week | Module | Hours | Milestone |
|---|---|---|---|
| 9 to 10 | Essential JavaScript concepts | 5 to 6 weekly | Closures, async/await, array methods |
| 11 | Responsive design (pt 1) | 4 | Mobile-first responsive page |
| 12 | Responsive design (pt 2) | 4 | Responsive solo project |
Goal: build a small interactive app without a framework, and have it work on phone, tablet, and desktop.
Month 4: React and APIs
| Week | Module | Hours | Milestone |
|---|---|---|---|
| 13 | Working with APIs (pt 1) | 4 | Fetch from a real API |
| 14 | Working with APIs (pt 2) | 4 | API-powered app |
| 15 to 16 | React basics (pt 1 to 2) | 5 to 6 weekly | First component tree |
Goal: read other people's React code, fetch from an API, and pass data through props without panic.
Month 5: Advanced React plus portfolio
| Week | Module | Hours | Milestone |
|---|---|---|---|
| 17 to 18 | React basics (pt 3) plus Advanced React (pt 1) | 5 to 6 weekly | Hooks and routing |
| 19 to 20 | Advanced React (pt 2 to 3) | 5 to 6 weekly | Polished React project |
Goal: start your portfolio with two or three shippable React apps. See our portfolio project ideas for prompts that match the path output.
Month 6: Career prep and job search
| Week | Module | Hours | Milestone |
|---|---|---|---|
| 21 to 22 | Getting Hired module | 5 weekly | Resume, LinkedIn, portfolio ready |
| 23 to 24 | Interview prep plus applications | 5 weekly | First applications sent |
Use JavaScript Interview Challenges and the Frontend Interview Questions course alongside this module.
Where each phase maps in the catalog
The path bundles these topics in order, but if you want to drill into a specific skill or revisit it later, here is where each phase lives in the wider catalog:
- Months 1 to 2 (HTML, CSS): HTML and CSS courses
- Month 3 (JavaScript depth): JavaScript courses
- Months 4 to 5 (React, APIs): React courses and TypeScript courses
- Month 6 (interview prep): JavaScript interview challenges
Frontend-only scope, and the Fullstack extension
This calendar covers the Frontend Developer Path end to end. That is deliberate: Frontend is the path most career changers should finish first, and a clean six-month frontend plan is easier to hold than a sprawling nine-month one. If your target role is fullstack, you do not need a different plan, you need this one plus an extension.
After Month 6, the Fullstack Developer Path adds roughly 27 hours on top of the frontend foundation. At the same steady pace, budget about two extra months:
| Month | Focus | Deliverable |
|---|---|---|
| 7 | Node and Express fundamentals | A small REST API you wrote yourself |
| 8 | SQL, databases, TypeScript, and a Next.js plus AI intro | A fullstack app with a real database behind it |
If you already know you want the broader track, you can swap to the Fullstack path from the start and follow Months 1 to 6 unchanged (the frontend modules are shared), then continue into Months 7 and 8. Either way, finish and ship the frontend portfolio first; a backend with no frontend to show is a harder thing to interview on.
Printable checklist
Copy this into a notes app or print it, and tick a box each time you close out a milestone. The point is a visible chain you do not want to break.
- Month 1: Built a styled, interactive HTML page from scratch
- Month 1: Shipped a first solo project
- Month 2: Rebuilt a real layout from a screenshot
- Month 2: Comfortable with Grid, Flexbox, and CSS variables
- Month 3: Used closures, async/await, and array methods without notes
- Month 3: Shipped a responsive, framework-free app
- Month 4: Fetched from a real API
- Month 4: Built a React app with a component tree
- Month 5: Hooks and routing working in a project
- Month 5: Two or three portfolio projects shipped
- Month 6: Resume, LinkedIn, and portfolio ready
- Month 6: First job applications sent
- (Fullstack) Month 7: Wrote a small REST API
- (Fullstack) Month 8: Shipped a fullstack app with a database
A realistic daily routine
Two hours per day, five days per week, hits 10 hours and leaves weekends free for solo projects or rest.
| Block | Minutes | Activity |
|---|---|---|
| Warm-up | 5 | Re-read yesterday's notes or the previous scrim |
| Core learning | 60 | Work through new Scrimba lessons in the player |
| Practice | 40 | Solo project work or interactive challenges |
| Wrap-up | 15 | Quick notes, then post progress in Discord |
Five rules that keep the plan alive
- Start with five minutes on low-motivation days. Just open the player. Momentum is the real product. This is the Tiny Habits principle from BJ Fogg at Stanford.
- Use the Scrimba Discord as accountability. Peer pressure beats willpower.
- Do not skip solo projects. The struggle is the point.
- Track a streak. Even 15 minutes counts. The goal is no broken chain.
- Take rest days. Schedule one or two. Burnout, not bad teachers, is why most self-taught learners quit.
Read this plan if
You are committing to the Frontend or Fullstack path and want a week by week roadmap. The pace is a template, not a deadline. Adjust around your life and keep going.
Related pages
- Frontend Developer Path reviewed step by step
- Fullstack Developer Path for a longer plan
- Frontend vs Fullstack Path for help deciding
- How to Get Hired with Scrimba on the job-search phase
- Building a Coding Habit on consistency
Aim for 10 to 15 hours weekly for most learners. That pace completes the Frontend Path in about six months. Twenty to twenty-five hours weekly cuts it to about 3.5 months but is harder to sustain past month two.
Yes. Many students study 1.5 to 2 hours per evening plus a longer weekend session. Consistency beats marathons, so 30 minutes a day is better than one ten-hour Saturday.
Treat the schedule as a guide. If a module takes longer, that is fine. Understanding the material matters more than hitting weekly targets.
The career paths are designed to be sufficient. MDN documentation and LeetCode for interview prep are useful companions, but you do not need a second course platform.
Commit to the path that matches this plan
Validate scrims on free courses, then use Pro for the full Frontend sequence and Discord.