Phase 1: Pick Your Path and Set Expectations

Decide bootcamp, self-taught, or degreeThis choice shapes your next 6–24 months, so make it deliberately rather than drifting. Self-taught programming is more cost-effective but requires discipline and may take longer, while bootcamp grads often have higher job placement rates but need to build strong portfolios too.
Set a realistic timelineExpect at least 6–12 months of consistent work before you're job-ready, longer if you can only study part-time.
Check its outcomes report first if considering a bootcampCourse Report's 2025 survey shows 79% of alumni employed full-time, with a median salary increase of 51% over pre-bootcamp income, but market conditions matter as much as the bootcamp itself — one major program's placement dropped from 83% in 2021 to 37% in 2023.
Budget for the real cost, not just tuition if comparing to a cs degreeWeigh lost income too: four years of full-time study means four years not earning a developer salary, and even at a conservative junior salary the foregone earnings can run into the hundreds of thousands over that time.
Tell your household or support system what's comingA career change eats evenings and weekends; get buy-in before you're three months in and burned out.
Keep your current job while you learn, if at all possibleDon't quit before you have savings or a start date; the job search itself can take months.

Phase 2: Build the Fundamentals

Pick one language to start and stick with itCommon first choices are Python or JavaScript — don't hop languages every few weeks.
Learn how the web works (or how your chosen stack works) before frameworksTrying to learn React before plain JavaScript just adds confusion.
Work through a structured course start to finish, not a pile of scattered videosHalf-finished courses don't show up on a resume.
Practice writing code daily, even 30 minutesConsistency beats occasional marathon sessions for actually retaining the skill.
Learn git and GitHub earlyEvery job will expect you to already know version control; it's not something you pick up in an interview.
Join a community (Discord, local meetup, subreddit)Isolation is the #1 reason people quit self-taught learning.

Build 3–5 original projects, not tutorial clonesEmployers can spot a copied tutorial project instantly.
Deploy at least one project live on the internetA link people can actually click beats a folder of code they have to run locally.
Write a README for every project explaining what it does and whyThis is often the only thing a recruiter actually reads.
Contribute to someone else's open-source project, however smallIt proves you can work with other people's code, which is most of the job.
Skip building a portfolio site until you have projects worth showingAn empty portfolio with a fancy homepage doesn't help you.

Learn basic data structures and algorithmsTechnical screens still lean on this even when the daily job doesn't.
Practice explaining your code out loudInterviewers care as much about how you think as whether the answer's right.
Learn to read and debug someone else's code, not just write your ownMost real work is maintaining existing systems.
Understand basic testing and how to write a unit testIt's a common gap for self-taught developers and an easy thing to be asked about.
Tailor this list to what those job postings actually ask for, rather than studying everything equally if targeting a specific stack

Rewrite your resume around outcomes, not just past job titlesFrame your old career's transferable skills (communication, project ownership) alongside your new technical ones.
Get a technical person to review your resume and one project's codeA second pair of eyes catches things you're blind to after months of solo work.
Apply to jobs before you feel "ready"Nobody feels ready; waiting for that feeling just delays income.
Track every application and its stage in a spreadsheetJob searches in tech routinely mean 50–100+ applications; you'll lose track without one.
Practice live coding under time pressure, not just untimed practiceThe nerves of a timed interview are a different skill than solving a problem at home.
Prepare 2–3 stories about your career change for behavioral questions"Why are you switching?" comes up in nearly every interview — have a real answer ready.
Negotiate the offer before acceptingThis is close to your only chance to set your starting salary; most employers expect some back-and-forth.

Ask for a slower ramp-up if you're the only career changer on the teamIt's reasonable to ask for extra ramp time and no one should hold that against you.
Keep learning in public (blog, small talks, contributions)It compounds toward your next role and keeps your skills from going stale.
Don't compare your year-one self to your team's senior engineersThat comparison is the #1 cause of impostor syndrome burnout in new developers.