Career Change to Tech: A 6-Month Roadmap

You are 32, working in marketing or finance or healthcare. You read about tech salaries. You hear about engineers making $300k a year working remote. You wonder if you could make the switch.

The short answer is yes. The long answer is that it takes 6 to 12 months of focused work, and most people who attempt it give up around month 3 when the initial excitement wears off.

Here is a realistic 6-month roadmap to make the career change to tech in 2026, based on patterns from people who actually did it.

First, Pick the Right Path#

Tech is not one career. It is several distinct paths, each with different skills, timelines, and market dynamics.

Path 1: Software Engineering

The classic tech career. High pay, high demand, but requires real technical skills.

• Time to job-ready: 6 to 12 months of focused study
• Entry-level pay (2026): $90k to $140k
• Difficulty: high

Path 2: Product Management

Less technical. Focus on strategy, customer insights, and execution.

• Time to job-ready: 3 to 9 months
• Entry-level pay (2026): $100k to $160k (Associate PM at top companies)
• Difficulty: medium, but harder to break in without internal transfer

Path 3: UX/Product Design

Visual and interaction design for digital products.

• Time to job-ready: 6 to 12 months (portfolio building)
• Entry-level pay (2026): $80k to $130k
• Difficulty: medium

Path 4: Data Analytics

Working with data to drive business decisions. Less technical than data science.

• Time to job-ready: 3 to 6 months
• Entry-level pay (2026): $75k to $115k
• Difficulty: medium

Path 5: Technical Sales / Customer Success

Selling tech products to businesses. Often the fastest path for non-technical career changers.

• Time to job-ready: 1 to 3 months
• Entry-level pay (2026): $80k to $140k + commission
• Difficulty: low to medium

Path 6: Product Marketing

Marketing for tech products. Bridges traditional marketing and tech.

• Time to job-ready: 2 to 6 months
• Entry-level pay (2026): $90k to $140k
• Difficulty: medium

This roadmap focuses on Software Engineering since it is the most common (and hardest) path. The principles apply to other paths with adjustments.

Month 1: Foundation#

Week 1-2: Validate the Decision

Before you invest 6+ months, make sure this is what you want.

• Spend 5 hours coding through a free Codecademy or freeCodeCamp HTML/CSS course
• Watch 3 hours of "day in the life of a software engineer" videos on YouTube
• Read 5 r/ExperiencedDevs threads about the realities of the job
• Talk to 2 to 3 engineers in your network (LinkedIn coffee chats)

If after these 20 hours you are still excited, proceed. If you are bored or frustrated, consider a different path.

Week 3-4: Pick Your Stack

You cannot learn everything. Pick a specific direction:

Front-end web development: HTML, CSS, JavaScript, React. Easier to see results, lots of jobs.

Back-end web development: Python or Node.js, databases, APIs. More logical, less visual.

Full-stack: Both. More employable but takes longer.

Data engineering: Python, SQL, data pipelines. Growing market.

DevOps / Cloud: AWS or GCP, Linux, scripting. Good entry path for IT folks.

For most career changers, full-stack JavaScript or Python is the safest bet. JavaScript has the most entry-level jobs. Python has the gentlest learning curve.

Week 4: Set Up Your Environment

• Install VS Code
• Set up Git and GitHub
• Create a Twitter/X account focused on tech (follow developers, learn the language)
• Buy or get free access to a learning platform (Frontend Masters, Codecademy Pro, Scrimba)

Month 2: Build Real Skills#

The 4-Hour Daily Rule

You cannot make this career change with 1 hour per day after work. You need at least 3 to 4 hours of focused study daily, plus 6 to 8 hours on weekend days.

Total: ~30 hours per week of coding/learning.

This is hard if you have a full-time job. Some options:

• Wake up 2 hours earlier
• Use lunch break (1 hour)
• Code 1.5 hours after work
• Block 12-15 hours on weekends

If you cannot maintain 30 hours per week, your career change will take 12+ months instead of 6.

What to Study

For full-stack JavaScript:

• Week 5-6: JavaScript fundamentals (variables, functions, arrays, objects)
• Week 7-8: ES6+ features (arrow functions, async/await, destructuring)
• Week 9: DOM manipulation, fetch API
• Week 10-12: One small project (todo app, calculator, weather app)

Recommended resources:

• "The Modern JavaScript Tutorial" (javascript.info)
• freeCodeCamp's JavaScript Algorithms certification
• "You Don't Know JS Yet" book series by Kyle Simpson

Month 3: Frameworks and First Big Project#

Week 13-16: Learn React (or Your Framework)

React is the most-hired framework in 2026. Spend 4 weeks getting comfortable:

• Components, props, state
• Hooks (useState, useEffect, useContext, useReducer)
• Forms and validation
• Routing with React Router
• API calls and data fetching

Recommended: official React docs (excellent in 2026), then "The Complete React Course" on Udemy.

Project 1: Real CRUD App

By end of month 3, build a real project:

• Frontend in React
• Backend API (use Node.js + Express, or Python + FastAPI)
• Database (PostgreSQL)
• Deployed on Vercel + Render or Railway

Examples:

• A book tracking app (search books, track reads, rate them)
• A workout logger (log exercises, see history, set goals)
• A budget tracker (categorize expenses, see trends)

This project should take 60+ hours. It is your first real portfolio piece.

Month 4: Build Depth and Portfolio#

Week 17-20: Second and Third Projects

You need 3 strong projects in your portfolio. Make the second and third more ambitious:

• Add authentication (login/signup)
• Add a third-party API (Stripe for payments, OpenAI for AI features)
• Add tests (unit tests with Jest, integration tests)
• Add CI/CD (GitHub Actions for automated deployments)

By end of month 4, you should have:

• 3 deployed projects with live URLs
• Clean GitHub profile with consistent commits
• A simple portfolio site with project descriptions
• Working knowledge of full-stack development

Week 21: Algorithms and Data Structures

Start LeetCode. Tech interviews require it.

• Solve 30 to 50 easy problems
• Cover: arrays, strings, hashmaps, basic recursion
• 1 hour per day, 5 days per week

You will not be ready for FAANG interviews yet. But you will be ready for small-to-mid company interviews.

Month 5: Job Search Preparation#

Week 22: Resume

Write your tech resume from scratch. This is hard for career changers because your previous experience does not directly apply.

Structure:

1. Header (name, contact, LinkedIn, GitHub, portfolio URL)
2. Summary (2-3 lines): "Career changer with X years of experience in [field], now focused on full-stack web development. Built 3 production apps using React, Node.js, and PostgreSQL."
3. Projects (your 3 best, with descriptions and tech stack)
4. Skills (languages, frameworks, tools, databases)
5. Education (degree, even if non-CS)
6. Previous experience (1 to 2 bullets per role, focusing on transferable skills)

Run your resume through our ATS checker to make sure it scores well against tech job descriptions.

Week 23: LinkedIn Overhaul

Your LinkedIn needs to be tech-focused:

• Headline: "Full-Stack Engineer | React, Node.js, PostgreSQL"
• About: rewrite to focus on your tech journey and what you bring
• Experience: highlight technical aspects of past roles
• Projects: add all 3 to a Projects section
• Skills: list technical skills relevant to tech roles

Get our LinkedIn audit if you want detailed feedback.

Week 24: Network Outreach

Cold outreach is essential for career changers without tech networks.

Send 5 to 10 messages per day to:

• Engineers at companies you want to work at
• Recruiters at tech companies
• Former colleagues now in tech
• Bootcamp grads with similar backgrounds

Template:

"Hi [Name], I am transitioning into tech from [your field] and would love to learn about your path. I have spent the last 5 months building 3 full-stack apps and prepping for engineering roles. Would you be open to a 20-minute chat? Happy to ask about [specific topic from their profile]."

Conversion rate: 5-10% will respond and chat. Each chat builds your network and might lead to referrals.

Month 6: Apply and Iterate#

The Apply Volume

For career changers, you need volume. Expect to apply to 100 to 300 jobs to get your first offer.

Daily routine:

• Morning (1 hour): apply to 5 to 10 tailored roles
• Afternoon (2 hours): work on a stretch project (something more ambitious)
• Evening (1 hour): LeetCode prep, technical interview prep

Target Companies

Career changers do better at certain types of companies:

Good targets:

• Bootcamp-friendly companies (Pivotal, Carta, Cruise have hired bootcamp grads)
• Mid-size companies (1,000 to 10,000 employees)
• Industries you already understand (fintech if you came from finance, healthtech if you came from healthcare)
• Companies with hiring partnerships with bootcamps

Harder targets initially:

• FAANG and elite startups (typically want CS degrees or 3+ years experience)
• Very small startups (often want senior engineers only)
• Specialized roles (ML, security, low-level systems)

The First Job Acceptance Strategy

Your first tech job will probably pay less than you hoped. That is okay.

If you can get a $85k offer at a regional bank or a mid-size SaaS company, take it. After 18 months of experience, you can jump to a $130k role. After 36 months, $180k+ is realistic.

The first job is a stepping stone. Do not over-optimize for it.

Interview Prep Specifically

Career changers often fail technical interviews because:

• They have not done enough LeetCode
• They get nervous and forget basics
• They cannot articulate what their projects do well

Practice with:

• LeetCode daily problem
• Mock interviews twice per week
• Recording yourself explaining your projects
• Pair programming with another aspiring engineer

Common Mistakes Career Changers Make#

Mistake 1: Tutorial Hell

Watching tutorials feels productive. It is not.

After your first month, every project should be built from scratch (or heavily modified from a tutorial). Coding along with someone teaches you nothing.

Mistake 2: Learning Too Many Things

You do not need to learn React AND Vue AND Angular. Pick one. Master it. Move on.

You do not need to learn Python AND JavaScript AND Go. Pick one stack.

Depth in one stack beats shallow knowledge across 5.

Mistake 3: Skipping Real Projects

Your portfolio is everything for a career changer. Without real projects, you are competing against CS graduates with internships. You cannot win that comparison.

Build apps. Deploy them. Make them complex enough to demonstrate real skill.

Mistake 4: Underestimating the Time

The bootcamp marketing makes it sound like you can change careers in 12 weeks. In reality, 6 months is the minimum, and 9 to 12 months is more realistic for sustained, lasting career changes.

Mistake 5: Quitting Your Job Too Early

Do not quit your current job before you have a tech offer. The job search can take 3 to 6 months once you start applying. Having income removes pressure and lets you be selective.

Some career changers quit, run out of savings in month 4, and take any job. They end up back where they started.

The Pay Realities#

Be realistic about pay for your first tech job:

• Bootcamp grad / career changer entry: $75k to $110k
• 1 year of experience: $95k to $135k
• 3 years of experience: $130k to $200k
• 5 years of experience: $170k to $300k

Career changers often beat this curve after the first job because their non-tech experience adds value (especially in product, sales engineering, or technical writing roles).

What to Do This Week#

If you are seriously considering a career change to tech:

1. Spend 5 hours on Codecademy's free intro course this weekend
2. Decide if you want to invest 6+ months
3. Pick your path (full-stack JS is the safest starting point)
4. Block 30 hours per week for the next 6 months
5. Set up your environment, GitHub, learning resources
6. Track your progress weekly (blog post or LinkedIn update)

This is hard. Most people who say they will do it never actually do. But the ones who do come out the other side with a higher-paying, more interesting career.

Start this weekend. Six months from now, you can be writing your first tech job offer. Or you can still be where you are today.

Your call.