--- title: Learning to Code From Scratch as a Career Changer description: Move from zero coding experience to a job offer, one deliberate phase at a time. category: life tags: [career-change, coding, self-taught, job-search] version: "1.0" updated: 2026-09-13 sources: - name: Self-Taught vs Bootcamp vs CS Degree: Which Path Is Right (2026) url: https://scrimba.com/articles/self-taught-developer-vs-coding-bootcamp-vs-cs-degree-which-path-is-right-in-2026/ - name: Coding Bootcamp vs Self-Taught: Which One is Right For You? url: https://careerkarma.com/blog/coding-bootcamp-versus-self-study/ - name: Bootcamp vs Self-Taught: Which Path Wins? | IT Support Group url: https://thisisanitsupportgroup.com/blog/it-bootcamp-vs-self-taught-which-path-2026/ --- Switching into software isn't about grinding tutorials forever — it's about picking one path, building real things, and getting in front of people who hire. This checklist walks you from "I don't know where to start" to "I have a job offer," roughly in the order you'd tackle it. ## Phase 1: Pick Your Path and Set Expectations - [ ] Decide bootcamp, self-taught, or degree `{essential}` This 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 timeline Expect 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 `{when: considering-a-bootcamp}` Course 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 `{when: comparing-to-a-cs-degree}` Weigh 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 coming `{essential}` A 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 possible `{essential}` Don'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 it Common 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 frameworks Trying to learn React before plain JavaScript just adds confusion. - [ ] Work through a structured course start to finish, not a pile of scattered videos Half-finished courses don't show up on a resume. - [ ] Practice writing code daily, even 30 minutes Consistency beats occasional marathon sessions for actually retaining the skill. - [ ] Learn git and GitHub early `{essential}` Every 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. ## Phase 3: Build Real Things - [ ] Build 3–5 original projects, not tutorial clones Employers can spot a copied tutorial project instantly. - [ ] Deploy at least one project live on the internet A 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 why This is often the only thing a recruiter actually reads. - [ ] Contribute to someone else's open-source project, however small It 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 showing An empty portfolio with a fancy homepage doesn't help you. ## Phase 4: Fill the Gaps Employers Test For - [ ] Learn basic data structures and algorithms `{essential}` Technical screens still lean on this even when the daily job doesn't. - [ ] Practice explaining your code out loud Interviewers 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 own Most real work is maintaining existing systems. - [ ] Understand basic testing and how to write a unit test It'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 `{when: targeting-a-specific-stack}` ## Phase 5: Get Job-Ready - [ ] Rewrite your resume around outcomes, not just past job titles Frame 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 code A second pair of eyes catches things you're blind to after months of solo work. - [ ] Apply to jobs before you feel "ready" `{essential}` Nobody feels ready; waiting for that feeling just delays income. - [ ] Track every application and its stage in a spreadsheet `{essential}` Job searches in tech routinely mean 50–100+ applications; you'll lose track without one. - [ ] Practice live coding under time pressure, not just untimed practice The 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 accepting `{essential}` This is close to your only chance to set your starting salary; most employers expect some back-and-forth. ## Phase 6: After You Land the Job - [ ] Ask for a slower ramp-up if you're the only career changer on the team It'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 engineers `{essential}` That comparison is the #1 cause of impostor syndrome burnout in new developers.