The short answer
About 138 hours of study for software development: roughly 14 weeks at 10 hours a week, 7 weeks at 20 or 28 weeks at 5. Across 15 tech jobs in HTD Talent's program data (October 2026), job-ready skills take 106 to 193 hours. That's study time to job-ready skills, not time to get hired.
Key takeaways
- Learning to code to a job-ready level takes about 106 to 193 hours of study, depending on the job you're aiming for.
- At 10 hours a week, that's 11 to 20 weeks. Weekly hours change the timeline far more than talent does.
- Skills you already have come off the total, so your real number is often lower than the table.
- Job-ready skills and getting hired are two different finish lines. These hours cover the first one only.
- A full-time bootcamp packs far more hours into a similar number of weeks, and a degree takes years. Neither is required to start.
Most answers to this question are a range so wide it's useless. "Three months to a year." "Depends on you."
We'd rather give you a number. HTD Talent builds training programs by mapping each target job against live job-posting data, then counting the study hours it takes to reach job-ready skills. So we can tell you, program by program, how many hours it takes and how many weeks that becomes at your pace.
Below: the full table for 15 tech jobs, what "job-ready" means, what pushes your number up or down, how the hours compare with bootcamps and degrees, and a weekly schedule that works around a full-time job.
How long it takes for 15 tech jobs
Here's the core data. Hours are total study time to job-ready skills. Weeks are rounded up.
| Program | Target job | Study hours | Weeks at 5 h/wk | Weeks at 10 h/wk | Weeks at 20 h/wk |
|---|---|---|---|---|---|
| IT and Networking | Network and Computer Systems Administrator | 106 | 22 | 11 | 6 |
| UX and Product Design | Product Designer | 108 | 22 | 11 | 6 |
| Cybersecurity | Information Security Analyst | 111 | 23 | 12 | 6 |
| IT Project Management | IT Project Manager | 119 | 24 | 12 | 6 |
| Business Operations | Business Operations Analyst | 129 | 26 | 13 | 7 |
| QA and Testing | Software QA Analyst and Tester | 135 | 27 | 14 | 7 |
| Software Development | Software Developer | 138 | 28 | 14 | 7 |
| Web Development | Web Developer | 141 | 29 | 15 | 8 |
| Customer Success | Customer Success Manager | 146 | 30 | 15 | 8 |
| Data and BI Analytics | Business Intelligence Analyst | 148 | 30 | 15 | 8 |
| Cloud and DevOps | Site Reliability Engineer | 176 | 36 | 18 | 9 |
| Growth Marketing | Growth Marketer | 182 | 37 | 19 | 10 |
| AI Engineering | AI Engineer | 187 | 38 | 19 | 10 |
| Product Management | Product Manager | 191 | 39 | 20 | 10 |
| Data Science | Data Scientist | 193 | 39 | 20 | 10 |
Source: HTD Talent's program data (October 2026).
Study hours to job-ready skills, by program
Two patterns stand out. The coding-first jobs (software, web, QA) cluster tightly between 135 and 141 hours. The jobs that stack a second discipline on top of code, like machine learning for AI engineers or statistics for data scientists, sit near 190.
Not every program here is a pure coding track. Product design and customer success lean on tools and process more than code. They're in the table because people asking how long to learn to code are often asking how long it takes to get into tech.
You can see what's inside each one on the ready-made programs page.
How long does it take to become a software developer?
About 138 hours of study gets you to job-ready skills for a software developer role. At 10 hours a week, that's 14 weeks.
Those hours aren't arbitrary. Our Software Development program is six courses and five hands-on labs, built around what employers ask for. In the postings we sampled for software developer roles, 38% mentioned Python and 27% mentioned Java. JavaScript showed up in 11% and Docker in 9%.
So the program spends its hours on Python, Java, SQL and the Spring tools Java teams use. It doesn't spend them on languages few postings ask for.
One thing worth knowing before you commit. The Bureau of Labor Statistics says software developers typically need a bachelor's degree in computer and information technology or a related field. Plenty of people get in without one. But the degree expectation is real, and it's a reason some learners pick an adjacent job first, like QA or web development, where the skill hours are similar.
Job-ready skills and getting hired are two different finish lines
"Job-ready" means you can do the core work of the role at the level employers describe in their postings. You can write the code, use the tools and show it in real projects that an expert has reviewed.
Getting hired is a separate project. It depends on your resume, your portfolio, the local market, how many applications you send and some luck. Nobody can honestly put a week count on it, and we won't.
That's why every number in this guide stops at skills. If a program promises you'll be hired in a set number of weeks, ask how they measured it.
What changes your number
The table assumes you take the whole program. Your real number moves with four things.
- Skills you already have. If you write SQL at work, you don't need the SQL course. Our custom plans let you skip what you already know, so those hours come off the top.
- Weekly hours. This is the biggest lever. The same 138 hours is 28 weeks at 5 hours a week and 7 weeks at 20.
- Consistency. Ten hours every week beats 25 hours one week and zero the next. You lose less time relearning.
- The job you pick. Moving from Software Development (138 hours) to Data Science (193 hours) adds 55 hours, or about six weeks at 10 hours a week.
If you want to see your own number, build your own plan. Pick a field and a job, mark what you already know, set your weekly hours, and the timeline updates.
How this compares with full-time bootcamps and CS degrees
Our hours are lower than a bootcamp's or a degree's, and that's worth explaining honestly.
| Path | Typical length | Approximate hours | Source |
|---|---|---|---|
| HTD Software Development, part time | 14 weeks at 10 h/wk | 138 study hours | HTD Talent program data, Oct 2026 |
| Full-time coding bootcamp | About 14 weeks | 560 to 1,120 (40 to 80 h/wk) | Course Report |
| Part-time coding bootcamp | 6 to 9 months | Varies | Course Report |
| Bachelor's degree | 4 years on paper | 5,400 or more | Federal credit-hour rule, 120 credits |
Course Report puts the average bootcamp at about 14 weeks, with full-time in-person programs running 40 to 80 hours a week. Its length figure comes from a 2020 alumni survey, the latest it cites.
For degrees, federal rules define one credit hour as at least one hour of instruction plus two hours of outside work each week for about 15 weeks. That's 45 hours per credit. A typical bachelor's needs at least 120 semester credits, so 5,400 hours is the floor. And four years is optimistic. NCES reports that 64% of first-time, full-time students who started in fall 2014 finished their bachelor's at the same school within six years.
Why is our number so much smaller? A degree teaches general education, theory and electives along with code. A full-time bootcamp's hours include lectures, group work and career prep. Our hours count only the study time on the specific skills that postings for one job ask for. They don't include job search time. Different scope, different number.
A realistic weekly schedule if you work full time
Full-time workers in the U.S. put in 8.1 hours on days they work, per the BLS American Time Use Survey for 2025. The same survey found the average person spends 2.6 hours a day watching TV. Ten hours of study a week mostly comes out of that second number.
Here's a 10-hour week we'd recommend to anyone learning to code part time.
| Day | Time | What you do |
|---|---|---|
| Monday | 1.5 hours, evening | Watch course lessons, take notes |
| Tuesday | Off | Rest |
| Wednesday | 1.5 hours, evening | Practice exercises from Monday's lessons |
| Thursday | 1.5 hours, evening | New lessons |
| Friday | Off | Rest |
| Saturday | 3.5 hours, morning | Lab or project work, the hard stuff |
| Sunday | 2 hours | Finish the lab, review the week, plan next week |
A few things make this hold up for 14 weeks.
- Put the hardest work on the weekend, when you're fresh. Weeknights are for lessons and short practice.
- Keep two days fully off. Burnout ends more learning plans than difficulty does.
- Book your weekday blocks like meetings. If they're not on the calendar, they get eaten.
- Drop to 5 hours a week during a heavy work month instead of stopping. Momentum matters more than speed.
If 10 hours is too much right now, 5 still works. Software Development at 5 hours a week is 28 weeks, about six and a half months.
When this path isn't the right fit
Self-paced, part-time study isn't for everyone. Be honest with yourself on these.
- You can't protect at least 5 hours a week for several months. Below that, you forget faster than you learn.
- The employers you're targeting require a computer science degree. Some do, especially for senior or research-heavy roles. A skills program won't replace that credential.
- You need structure every single day to stay on track. A full-time, in-person bootcamp or a degree program gives you that, at a much higher hourly cost in time.
- You want someone to promise you a job. We won't, and you should be wary of anyone who does.
If you're unsure which job to aim for, a recruiter can help you choose. Book a free call with a recruiter. And if you're weighing data roles, read data analyst vs data scientist before you pick, since the hour gap is real. Our guides on how to become a data analyst and how to become a cloud engineer go deeper on those paths.
Frequently asked questions
Can I learn coding in 3 months?
Yes, for skills at a job-ready level in many roles, if you put in 10 or more hours a week. Software Development takes about 14 weeks at 10 hours a week, and IT and Networking about 11. At 5 hours a week, plan on six months or more.
Is it better to study 20 hours a week if I can?
It's faster, and Software Development drops to about 7 weeks at that pace. But only pick 20 hours if you can hold it every week. A steady 10 hours usually finishes sooner than an ambitious 20 that collapses in week three.
Do I need to be good at math to learn to code?
For most software, web, QA and IT roles, everyday math is enough. Data science and AI engineering are different, since machine learning relies on statistics and some linear algebra. That's part of why those programs run closer to 190 hours.
Which language should I learn first?
Learn the one the job you want asks for. In our data, Python appeared in 38% of software developer postings, 59% of AI engineer postings and 84% of data scientist postings. That makes it a sensible first language if you haven't picked a job yet.
Sources
- HTD Talent program data, HTD Talent, October 2026
- Software Developers, Quality Assurance Analysts, and Testers, Occupational Outlook Handbook, U.S. Bureau of Labor Statistics, 2025
- American Time Use Survey, 2025 Results, U.S. Bureau of Labor Statistics, 2026
- Coding Bootcamps 101, Course Report (length data from 2020 alumni outcomes report)
- 34 CFR 600.2, definition of credit hour, U.S. Department of Education via eCFR
- Undergraduate Retention and Graduation Rates, Condition of Education, NCES
- Bachelor's degree requirements, Kent State University catalog

