A 10-hours-a-week study timetable for full-time employees
In this article (6 sections)
Related programme: the Data Science course (6 months; ₹1,30,000 (inclusive of GST) · EMI from ₹5,000/month).
Ten hours a week alongside a full-time job works if you split it into one long weekend block for new material, three short weekday sessions for practice, and one fixed review slot, and if you decide in advance what to drop in a bad week. The timetable below assumes a 9-to-6 office job with a commute and is meant to be copied and adjusted, not admired.
Where ten hours actually come from
Before the timetable, find the hours. Write down last week honestly, in hours:
| Block | Mon–Fri total | Sat | Sun |
|---|---|---|---|
| Work + commute | 50 | 0 | 0 |
| Sleep | 37 | 8 | 8 |
| Meals, chores, family | 20 | 6 | 6 |
| Phone and TV | 12 | 4 | 4 |
| Left over | 1 | 6 | 6 |
This is one hypothetical week; yours will differ. The pattern is common, though: weekday evenings hold little truly free time, and most of the reliable hours sit on weekends. So the plan below puts six of the ten hours on Saturday and Sunday.
The weekly timetable
| Day | Slot | Hours | Task type |
|---|---|---|---|
| Mon | 7:00–7:45 am | 0.75 | Redo one exercise from the weekend without looking |
| Tue | 9:30–10:15 pm | 0.75 | Read notes; write three questions for the doubt session |
| Wed | 7:00–8:00 am | 1.0 | New exercise on this week's topic |
| Thu | — | 0 | Rest. Protects the week from collapsing |
| Fri | 9:30–10:00 pm | 0.5 | Fix one error from the error log |
| Sat | 10:00 am–1:00 pm | 3.0 | Live class or new material, notebook open |
| Sun | 10:00 am–1:00 pm | 3.0 | Assignment or project work |
| Sun | 8:00–9:00 pm | 1.0 | Weekly review: what I can do now that I couldn't last Sunday |
| Total | 10.0 |
Three design choices are deliberate:
- Thursday is empty. A plan with no slack breaks the first time a meeting runs late. One empty day absorbs one bad day.
- Weekday sessions are short and specific. Forty-five minutes is enough to redo a known exercise. It is not enough to start something new, so the timetable never asks you to.
- The Sunday evening review is its own slot. It is the hour most people skip, and the one that tells you whether the other nine worked.
If your live classes run at different times, move the Saturday block to match and keep the rest of the shape.
A 12-week arc for a data science start
The weekly grid repeats; the content moves. For a data science foundation, this is a realistic order at ten hours a week:
- 1Weeks 1–2: Python basics — variables, lists, loops, functions. One small script per week.
- 2Weeks 3–4: pandas — reading a CSV, filtering, grouping, joins.
- 3Weeks 5–6: SQL — select, where, group by, joins; the same questions answered in both pandas and SQL.
- 4Weeks 7–8: Statistics — distributions, averages that lie, confidence intervals, one A/B test by hand.
- 5Weeks 9–10: First model — train/test split, linear and logistic regression, one honest evaluation.
- 6Weeks 11–12: One small project end to end, written up in a README.
If you are in a structured programme, follow its sequence instead; the point is that each fortnight has a named outcome you can check on Sunday.
The bad-week protocol
Some weeks will not hold ten hours: a release, month-end close, a wedding, fever. Decide now what survives:
| Week type | Keep | Drop |
|---|---|---|
| Normal | Everything | Nothing |
| Busy (6 hours available) | Saturday block, Sunday review | Weekday sessions |
| Very busy (3 hours) | Watch the recording at 1.25x, do one exercise | Project work |
| Lost week (0–1 hour) | Sunday review only, 20 minutes | Everything else |
The rule is that the Sunday review never drops. Even in a lost week, twenty minutes of writing down where you are keeps the thread. Two lost weeks in a row is a signal to use a catch-up plan rather than hoping to double up.
What to do with the hours you do have
People with limited time often spend it rewatching. Rewatching feels productive and mostly is not. A better split of a ten-hour week is roughly:
- 3 hours taking in new material (class or reading)
- 5 hours doing: exercises, assignments, project work
- 1 hour reviewing and fixing errors
- 1 hour asking questions and reading answers
If your week is mostly watching, move hours from watching to doing.
When ten hours is not enough
Ten hours suits a six-month programme like our Data Science course if the hours are real. It does not suit a programme with more weekly live time, or a period at work when you are regularly staying late. If the timetable fails three weeks in a row despite the bad-week rules, the answer is a longer timeline or a lighter programme, not more willpower.
Frequently asked questions
Is 10 hours a week enough to learn data science while working?
It is enough to make steady progress through a structured programme over six months or more, provided the hours are protected and mostly spent practising rather than rewatching. It is not enough to learn it in a few weeks.
Should I study before work or after work?
Put the hardest practice where your head is clearest, which for many people is early morning or a weekend block. Use tired weekday evenings for lighter tasks such as reviewing notes or fixing small errors.
Pankit Kumar has 10 years in Data Science & AI, building and shipping production systems in regulated pharma and clinical environments. He is a freelance trainer at Boston Institute of Analytics, AnalytixLabs and Scaler, and has taught this material to thousands of working professionals.
This article is part of our Data Science programme — 6 months. From data foundations to machine learning, deep learning and deployment.
Explore Data Science