The Promise and The Caveat

"Learn to code in 12 weeks and get hired."

You've seen those ads. Here's the real version: You can go from zero to junior developer in 6 months. But you need to commit 20-30 hours a week. Not videos. Actual coding.

If you're in Singapore considering a career switch into tech, here's your roadmap.

Month 1: Foundations (Don't Skip This)

Most people skip this. They regret it later.

Week 1-2: How The Web Actually Works

Practical understanding. Not theory.

What happens when you type a URL and hit enter
Client vs server
HTML, CSS, HTTP

You don't need to memorize this. You need mental models to reason about problems.

Resources: freeCodeCamp's "Responsive Web Design" course (free), The Odin Project (free, Singapore-friendly).

Week 3-4: JavaScript Fundamentals

Most people struggle here. Don't memorize. Understand.

Variables, data types, functions, scope
Loops, conditionals, control flow
Breaking problems into steps
Build something: to-do list, calculator, game

Don't move on until you can build something small without constantly looking things up.

Reality check: 60-100 hours total. So 15-25 hours a week for 4 weeks.

Month 2: Real Projects Begin

You're going to start building things that actually work.

Week 5-6: Deeper JavaScript

Arrays and objects (how to store and manipulate data)
Async/await (how to wait for things to finish loading)
Fetch API (how to get data from other websites)
Build something with an API: a weather app, movie search, currency converter

These aren't tutorials you follow. These are problems you solve using JavaScript.

Week 7-8: Git and GitHub

This is non-negotiable. Every developer uses version control.

What Git is and why you need it
Basic workflow: add, commit, push
GitHub: where your code lives online
Writing decent README files

Push 2-3 projects to GitHub this month. This is the start of your portfolio.

Checkpoint: You should have 2-3 working projects on GitHub. Not perfect. Working.

Month 3: Choose a Framework and Go Deep

This is the big decision. React vs Vue vs something else?

Real talk: React has the most job postings in Singapore. So start with React.

Week 9-12: React Fundamentals

Components: how to break UIs into pieces
JSX: writing HTML-like syntax in JavaScript
Props and state: how components communicate and change
Hooks: useState, useEffect, and how to think in hooks
Build 2-3 React projects with APIs

Don't chase advanced patterns yet. Master the basics. You'll need them.

Checkpoint: You can build a multi-page React app that fetches data and updates the UI.

Month 4: Backend Basics + Databases

Here's where you stop being frontend-only.

Week 13-14: Node.js and Express

Setting up a web server
REST API basics (GET, POST, PUT, DELETE)
Routing and middleware
Building actual endpoints that do things

You're building the "behind the scenes" part of a website.

Week 15-16: Databases

Pick one: PostgreSQL (SQL) or MongoDB (NoSQL). Doesn't matter much for learning. Stick with one.

How to store data
Basic queries (getting data out, putting data in)
Connecting your backend to a database
Building a full-stack project: frontend + backend + database

Checkpoint: One complete full-stack project deployed somewhere live. Not on your laptop. Actually online.

Month 5: Portfolio and Deployment

Your projects need to live somewhere people can see them.

Week 17-18: Deploy Everything

Frontend: Vercel or Netlify (free tier, handles React beautifully)
Backend: Railway, Render, or fly.io (free tier works fine)
Custom domain: optional but impressive

Don't leave projects on your laptop. Deployed projects in your portfolio are worth 10x what's on localhost.

Week 19-20: Portfolio Polish

3-4 solid projects minimum
Clean, readable code with comments
Good READMEs that explain what you built
A simple portfolio website (doesn't have to be fancy)
LinkedIn updated with projects and links

What makes a portfolio stand out:

Projects that solve actual problems (not tutorial clones)
Clean UI (doesn't have to be gorgeous, just not broken)
Code you can actually explain
Projects you can show to someone in 3 minutes

Month 6: Actually Getting Hired

Week 21-22: Resume and Applying

Resume format: chronological, skills, projects. Tailor to each job (not generic).

Apply to 5-10 jobs per day on:

JobStreet, LinkedIn
Company career pages directly
AngelList (startups)
Singapore tech Telegram groups

Target entry-level roles.

Week 23-24: Interview Prep

They'll ask:

"Tell me about a project you built"
"Why that technology?"
"What would you do differently?"
"Solve this coding problem"

Practice explaining your projects. Out loud. To real people. It's harder than you think.

LeetCode for practice, but don't overdo it. You're not interviewing at Google. Easy problems work.

Checkpoint: You should be getting interviews by week 24. Offers aren't guaranteed yet. But you should be talking to people.

Realistic Salary Expectations (Singapore 2026)

Junior Developer: SGD 3,500-5,000/month
After 1-2 years: SGD 5,000-7,000/month
Mid-level (3-5 years): SGD 7,000-12,000/month

These are realistic ranges, not FAANG outliers.

1-to-1 vs Bootcamps vs Self-Study

Bootcamps:

Pros: Fast, structured, you graduate with a cohort
Cons: Expensive (SGD 10,000-20,000+), one-size-fits-all, doesn't guarantee jobs
Best for: People who need extreme structure and accountability

Self-study:

Pros: Free or cheap, completely flexible
Cons: Easy to get stuck, easy to quit, no accountability
Best for: Disciplined people with time

1-to-1 tutoring:

Pros: Personalized, fills gaps fast, interview prep, real feedback
Cons: More expensive than self-study, less than bootcamps
Best for: People who want structure without bootcamp prices, career switchers

Honestly? 1-to-1 helps career switchers the most because you can focus on YOUR blockers, not a generic curriculum.

Common Mistakes

Following the wrong tutorials. Some are outdated. Use official docs and courses from reputable sources.
Not building things. Watching isn't learning. You learn by breaking things and fixing them.
Building tutorial clones. Netflix clone #47 isn't impressive. Build something you actually use.
Not deploying. Your code on GitHub means nothing if it doesn't run.
Applying too late. Month 5, start applying. Don't wait until Month 6.

Real Talk: Will You Actually Get a Job?

If you follow this roadmap? Probably yes.

But here's what determines the probability:

Discipline: Can you commit 20+ hours/week for 6 months?
Portfolio: Do you have 3-4 projects people can actually see?
Interview skills: Can you explain what you built and why?
Luck and timing: Are companies hiring when you're ready?

You can't control luck. You can control everything else.

Next Steps

Pick a starting date. Not someday. Actual calendar date.
Set up your learning environment. Laptop, internet, maybe a code editor (VS Code, free).
Start Month 1 content this week. freeCodeCamp or The Odin Project.
Build in public. Blog, GitHub, social media. Show your progress. It helps.

Want guided help? We work 1-to-1 with career switchers at every stage — from "what's a variable?" to "help me nail this interview."

Let's build your portfolio →