3 to 5 hours
Progress, but slowly.
Enough to keep the habit and learn the foundations. Much of each session goes on remembering where you were, so end every session by writing down the next step.
Learning around a job
How to learn to code while working full time.
The short answer
Plan for 6 to 12 focused hours a week, spread over three or four short sessions rather than one long weekend. Follow one roadmap instead of switching courses, build small projects from the start, and get your code reviewed regularly. Most people who learn alongside a job do not stall because the material is too hard. They stall because a busy week breaks the routine and nobody notices.
You do not have to quit your job or pay for a full-time bootcamp to learn to code. You do need a plan that survives a bad week. This page is that plan, from the mentors at ZAM Academy, who teach people with jobs, families and studies one to one.
Two private classes, no card. Updated 5 October 2026 by ZAM Academy.
How much time
How many hours a week do you actually need?
Less than you fear, but more consistently than you think.
6 to 12 hours
What most working learners can sustain.
Enough for practice, a project and a review each week without taking over your evenings. This is the range ZAM plans around by default.
15 hours or more
Fast, if you can keep it up.
Possible in a quiet season at work. Plan for the week it drops back to six, because that is the week most people quit.
How long overall
How long does it take to become job-ready part time?
Nobody can honestly tell you to the week, and anyone who promises a date is guessing. A common estimate for going from zero to a junior-level portfolio is several hundred focused hours, often put at 400 to 600. At 8 hours a week that is roughly one year to eighteen months; at 12 hours a week, roughly eight months to a year.
Those numbers move a lot with your starting point, how consistent your weeks are, and whether someone is correcting your direction. The hours that count are the ones spent writing and fixing your own code, not watching someone else write theirs.
ZAM does not promise a job or a timeline. Your mentor sets weekly milestones around the hours you actually have, and moves them when your work does.
A realistic week
What a week of learning around a job looks like.
An example of about seven hours. Move the days around your shifts and keep the shape.
Monday · 45 min
Learn one idea
Read or watch one short lesson, then write the example yourself without copying it.
Tuesday · 60 min
Practise it
Do two or three small exercises on the same idea. Getting stuck here is normal, and useful.
Thursday · 60 min
Use it in your project
Add one small feature to the project you are building and commit it to GitHub, even if it is rough.
Saturday · 2 to 3 hours
Build and fix
The longer session: finish the feature, read your errors properly, and tidy up what you wrote this week.
Once a week · 40 to 90 min
Get your code reviewed
Show someone your code and decide together what comes next. At ZAM this is your private session with your mentor.
Sunday · 10 min
Write down the next step
One sentence: what you will do in Monday's session. It removes the cost of starting again.
Why people stop
Five reasons working learners stall, and the fix for each.
Switching courses
A new course feels like progress but resets you to the beginning. Pick one path and finish its current step before you look elsewhere.
Watching instead of building
Following a tutorial does not transfer to a blank file. From the first week, spend at least half your time writing your own code.
One bad week
Work gets busy, you miss a few sessions, and restarting feels heavy. Agree a minimum week with yourself, even two 20-minute sessions, so the habit never fully breaks.
Nobody sees your code
Without feedback you cannot tell whether you are improving or building bad habits. Get it reviewed by a mentor, a friend who codes, or a community.
No clear next step
Sitting down tired and deciding what to learn is where evenings disappear. Decide the next step at the end of the previous session, not the start of the next one.
Your options
Ways to learn around a job, compared honestly.
Each one suits someone. The full comparison, with published prices, is on the mentor vs bootcamp vs self-taught page.
Self-study
Free, flexible, and on your own.
Works well for people who have finished hard things alone before. The cost is the time lost going in the wrong direction.
Part-time bootcamp
Structured, on the cohort's timetable.
A fixed curriculum and classmates. You keep pace with the group at set times, and read their published fees and refund terms carefully.
Hourly mentor
Help when you are stuck.
Good for specific problems. You still plan your own path and keep yourself going between calls.
ZAM Academy
A path, a mentor and a weekly review.
A roadmap built around your hours, one mentor who reviews your code every week (90 minutes on Accelerator), and Zami AI between sessions. Monthly plans, no contract.
Questions
Common questions, answered plainly.
Can I learn to code while working a full-time job?
Yes. Many developers learned part time. It works when the hours are consistent, the path is clear and someone reviews your work. It fails most often when a busy month breaks the routine and there is no plan for restarting.
Should I quit my job to learn to code faster?
For most people, no. Keeping your income removes the pressure that makes people rush and give up, and part-time learning works if it is consistent. If you can afford to stop working for several months and want a cohort, a full-time bootcamp is a reasonable choice.
What is the best time of day to study?
The time you can protect every week. Many working learners use early mornings, before the day's tiredness, or a lunch break for reading and one evening for building.
What should I learn first?
Python, or HTML, CSS and JavaScript, depending on what you want to build. The free ZAM roadmap tool asks seven questions, including how many hours you have, and gives you the order.
How does ZAM fit around a job?
Sessions are private and scheduled around your availability and time zone, including evenings and weekends, and can be rescheduled when work gets busy. Plan for 6 to 12 focused hours a week; your mentor adjusts the workload to the hours you have.
Is ZAM only for people with jobs?
No. Students include working adults, career changers, university students and people between jobs. The plan is built around whatever hours you have.
Keep reading
Where to go next.
Start with two free classes
Tell your mentor how many hours you really have. The plan starts from there.
The first class maps your goal, level and weekly hours. The second is a real coding session with feedback. Then your mentor recommends one plan, and you decide.
Plans from US$79/month on Guided. Compare plans