Two things matter when you're planning a career transition around a program, and most institutes make you choose between them.
The first is certainty. You've arranged work, family and money around a finish date. You need it to hold.
The second is depth. You didn't enrol to be marched through a syllabus on schedule. If your batch hasn't understood gradient descent, moving on next Tuesday because the calendar says so serves nobody.
We think you're entitled to both, and this article explains exactly how we deliver both — the machinery that protects your dates, and the machinery that protects your understanding. Then, because your own planning matters as much as ours, the second half is a practical guide to building a study routine that holds up across a long program.
Your end date is a commitment, not an estimate
Here's what that means in practice.
You get a published calendar at enrolment. Session dates, assessment windows, project review milestones and your program end date — in writing, before you pay. Not a rough duration. A date.
We build the slack in advance. Every program carries buffer weeks distributed across its length — the number scales with the program, and they're marked on your calendar from day one. These aren't holidays and they aren't padding. They exist so that when a batch needs an extra session on a difficult module, that session has somewhere to go. Most programs discover they need flexibility and take it out of the end date. We plan for it and take it out of the buffer.
Schedule changes carry a minimum of 72 hours notice, except in genuine emergencies, and the replacement slot is confirmed at the same time as the change — never "to be announced."
When a mentor changes, continuity is our job. The incoming mentor receives your batch's progress record, outstanding doubts and project status before their first session. You should never have to re-explain where your batch had reached. If that ever happens to you, it's a delivery failure on our side and we want to hear about it.
And the commitment that matters most: if a program runs past its published end date because of changes we made, no additional fee applies, and mentorship and placement support continue through the extension.
We'd rather be measured on this than praised for it. Ask for your batch's calendar before you enrol, and hold us to the date on it.
And inside that calendar, we will not hurry you
This is the part we care about more, and it's where our teaching philosophy actually lives.
A doubt session ends when the doubt is resolved, not when the hour is up. That's what the format is for. If three people in a batch still can't follow why we chose one model over another, the session hasn't finished its job yet.
If a batch needs another session on a topic, the batch gets another session. This is what the buffer weeks are for. Your mentor doesn't need permission to slow down, and slowing down doesn't cost you your end date.
We don't move forward while a batch is lost. Technical curricula are sequential — week five genuinely depends on week three. Pushing ahead on schedule while half a cohort is still stuck doesn't save time; it manufactures a much larger problem two months later, when the gap has compounded and nobody can locate its origin.
Ask the basic question. In month six. In front of everyone. The learners who struggle most in any cohort are not the ones who ask too many questions — they're the ones who stopped asking in month two because they felt behind, and then quietly fell further behind. Doubt sessions, mentorship sessions and project reviews are all timetabled components of your program, and attendance at them counts toward your 75% exactly as a live class does. They aren't extras. They're where the learning actually consolidates.
Depth is what you're buying. You can find the content free on the internet, and a lot of it is good. What you can't easily get is a practitioner who watches you attempt something, sees where your reasoning breaks, and stays with it until it doesn't. Rushing that would mean charging you for the one thing you could have got for nothing.
How both are true at once
The two promises above only work together because of one design decision: we plan for flexibility rather than hoping we won't need it.
| Approach | What happens when a batch needs more time |
|---|---|
| Fixed calendar, no slack | Either the batch is rushed, or the end date slips. Usually both, eventually. |
| No fixed end date | Depth is protected; your planning isn't. Timelines drift indefinitely. |
| Fixed end date with designed buffer | The batch gets the extra sessions. Your finish date holds. |
This is why we can say, without contradiction, that we won't rush you and that we intend to finish when we said. The flexibility isn't an exception to the schedule. It's built into it.
Two honest caveats, because a promise with no limits isn't a promise:
- Buffer is finite. A batch that needs substantially more time across many modules will exhaust it. If that's happening in your cohort, you'll hear it from us early — not in the final month.
- Your own attendance still governs your timeline. Below 75%, placement support is restricted and certificate issuance is delayed. Below 50%, extending enrolment or re-enrolling in missed modules attracts fees under our standard policy. Our buffer covers the batch's pace. It can't cover missed sessions.
What the timeline actually contains
It's worth seeing why a serious program can't run to the same calendar as a video course. These are the stages between a syllabus and a finished learner:
| Stage | Why it takes the time it takes |
|---|---|
| Teaching the concept | The fastest part. Content can be delivered quickly. |
| Applying it | Practice, mistakes, correction. Can't be sped up by teaching faster. |
| Assessment | Module tests, assignments, practical assessments, case studies — compulsory unless marked optional. |
| Re-attempt where needed | One re-test per module on approval. Learners who need it, need it. |
| Project work | Real data, real decisions, documented failures. |
| Project review | Reviewed, returned with feedback, revised. |
| Capstone | Submitted, approved, and where applicable defended before a mentor or expert panel. |
| Certification | Requires 75% attendance, passed assessments, approved projects, cleared dues. |
Most of those are dependencies, not sessions. A lecture-only course runs to a fixed calendar because nothing waits on anything. A program that certifies you only once your capstone is approved cannot, because your capstone is approved when it's good — not on a date chosen in advance.
One consequence worth planning around: certification gates placement eligibility. Pending assessments or an unapproved capstone don't just delay a certificate — they delay your entry into the placement process. Staying current is worth more than it looks.
Plan for the whole arc, not just the program
| Phase | What drives it |
|---|---|
| Your program | Curriculum depth, assessments, project reviews, capstone approval. The duration is on your program page and your calendar. |
| Interview readiness | Runs inside the closing phase of your program, overlapping with it — mocks, resume, aptitude practice. |
| Active job search | Continues after the program ends. Typically one to six months or longer, depending on domain, experience level, flexibility and market conditions. |
Whatever your program's length, budget for it plus a job search on the far side. That search is the part learners most often leave out, and it's usually the longest single variable in the whole timeline. If you've planned only for the program and nothing after, the shortfall will feel like the program failed you when it's actually a planning gap. We'd rather you knew that at the start.
Plan from what happens, not what you intend
Kahneman and Tversky documented a robust finding: people systematically underestimate how long their own work will take — even having done similar work before, even knowing about the bias. "I'll finish the module this weekend" is the same error as "this will run exactly to plan."
The fix is reference class forecasting — estimate from your actuals, not your intentions:
- After month one, compare study hours you actually completed against hours you planned.
- Use that ratio for every future estimate. Hit 60%? Plan at 60%, and stop treating the gap as a failure of willpower.
- Keep 15–20% of your own schedule empty. Not as a reward for being ahead — as the space that absorbs an ill week or a work deadline.
A plan with no slack isn't ambitious. It's a plan that breaks in an ordinary week. It's the same reason we build buffer into ours.
Building a timetable that survives the whole program
Start from the hours that exist. Most working professionals have 12–15 hours a week. Write down exactly where they are — specific days, specific times — before allocating a single topic.
Make every block conditional. Gollwitzer's research on implementation intentions found that plans phrased as "when X happens, I will do Y" are acted on far more reliably than general intentions with identical content. So not "revise SQL this week," but: "When I finish dinner on Tuesday and Thursday, I'll do SQL problems at my desk until 9:30." Trigger, place, stop time.
Limit what's open at once. Borrowed from kanban, the Toyota method: make the work visible and cap it. A simple board — to learn / learning now / needs practice / solid — with a hard limit of two or three items in "learning now." Half-finished topics carry a mental cost and nothing half-learned survives an interview.
Design out the two failure modes. Lean practice names three problems; two describe most collapsed study plans exactly. Muri (overburden) — a plan that needs an unusually good week to work will succeed twice and then break, and the break will feel like a character flaw rather than a design error. Mura (unevenness) — five hours every Sunday and nothing between is the most common study pattern there is, and six days off is six days of forgetting. Slightly under-ambitious and evenly spread beats heroic, every time.
A weekly template
| Day | Block | What |
|---|---|---|
| Mon | 60 min | New concept from the live class + attempt problems |
| Tue | 60 min | Practice, then closed-book self-test on Monday's material |
| Wed | 45 min | Mixed problems — this week and two weeks ago |
| Thu | 60 min | Project work |
| Fri | 30 min | Write down every unresolved question from the week |
| Sat | 2–3 hrs | Project work + doubt session, with Friday's list in hand |
| Sun | 60 min | Spaced review of an older module + plan the week ahead |
Two features are load-bearing. Friday's list converts "I'm generally lost" into specific questions a mentor can answer — vague confusion wastes a doubt session; a written list uses it. And Sunday's older-module review is what stops month-two knowledge evaporating before a month-nine interview.
How to study so the time pays off
Test yourself instead of reviewing. Roediger and Karpicke showed that retrieving from memory produces markedly better long-term retention than re-reading — even though re-reading feels more productive. Reviewing the evidence across techniques, Dunlosky and colleagues rated practice testing among the highest-utility strategies available, and highlighting and re-reading among the lowest. Close the notes. The gaps that appear are the point.
Spread it out. Cepeda and colleagues confirmed across a large body of research that distributed practice beats massed practice. Two hours on Tuesday and Thursday beats four on Saturday.
Mix the problems. Rohrer and Taylor found that interleaving problem types improves your ability to choose the right approach — while making practice feel harder. Interviews never announce the topic; they present a problem and expect you to classify it.
Practise your weakest thing. Ericsson described expertise as the product of targeted practice with immediate feedback on specific weaknesses. Later meta-analysis found the effect real but more variable than the popular "10,000 hours" version claims — so the defensible takeaway is simply that practising what you're bad at, with feedback, beats practising what you're good at, comfortably.
Expect difficulty to feel bad and work well. Bjork's work on desirable difficulties established that conditions slowing practice often improve retention and transfer. If study feels smooth throughout, that's a signal rather than a success.
Explain it out loud. Teach a concept to someone non-technical. The moment you reach for jargon is the moment you haven't understood it.
Four ideas about the shape of learning
Philosophies rather than findings — we use them because they change behaviour.
Shu-Ha-Ri (守破離). From Japanese martial arts: Shu, follow the form exactly; Ha, break from it once you understand why it exists; Ri, move beyond form. Most learners try to start at Ha, improvising before fundamentals are solid, and mistake the resulting confusion for the subject being hard. The stages are sequential for a reason — and Shu takes as long as it takes. This is, in one phrase, why we won't rush the early modules.
Kaizen (改善). Small, compounding improvement. One concept improved each day, sustained across a program, transforms a candidate — which is also why a few weeks either way matters far less than most learners fear. Consistency across months dwarfs the calendar.
Hansei (反省). Honest reflection, including after success. After every review or assessment, write what you'd do differently before reading the feedback. Cleared it easily? Write it anyway.
Shoshin (初心). Beginner's mind. The learners most at risk are those who've watched many videos and believe that constitutes knowing.
From the Indian tradition, two ideas sit alongside these. Svadhyaya — disciplined self-study — is the reminder that class time resolves confusion while self-study builds competence. And abhyasa, described in the Yoga Sutras as practice sustained over a long time, without interruption, and with earnestness, is a strikingly exact description of what separates learners who finish from those who drift. Without interruption is the operative phrase.
If something does change
- Ask for the revised calendar in writing, with the new dates and make-up slots confirmed.
- Ask what shifts downstream — capstone review window, certification, entry into placement activity.
- Use the gap. A moved session is a free week for spaced review of an older module, which is the thing nearly everyone skips.
- Escalate a pattern. One rescheduled session is life. A pattern is a delivery problem — raise it with your coordinator, and if it isn't resolved, formally in writing, with an acknowledgement in three working days and an outcome within fifteen.
Frequently asked questions
Your schedule and your end date
How long does the program take?
It varies by program — the duration for the one you're considering is on its program page. What doesn't vary is that you get a published calendar at enrolment carrying your specific end date in writing, before you pay. Ask for it, whichever program you're looking at.
Do you actually finish on schedule?
That's the commitment, and it's why every program carries buffer weeks rather than us hoping we won't need them. Ask for the calendar, and hold us to it.
When do I get my calendar, and how far ahead does it run?
At enrolment, before you pay. It carries your program end date, assessment windows and project review milestones, with session dates visible for at least the next 8 weeks at any point in the program. If you're being asked to commit money to a program whose dates you haven't seen, that's a reasonable thing to insist on — from us or anyone.
What happens when a public holiday falls on a session day?
The session moves, and the replacement slot is published at the same time as the change rather than later. Holidays are foreseeable, so these should appear in your calendar from the start rather than arriving as a surprise three days out.
What if my own availability changes mid-program?
Tell your academic coordinator as early as you can. Moving to a different batch timing is easier between modules than in the middle of one, and easier while your attendance is healthy than after it's slipped. If you can see a difficult stretch coming — a work project, a house move, exams — raise it in advance rather than absorbing it quietly.
Can I pause the program if something serious comes up?
Talk to the academic team before your attendance falls, not after. If you anticipate an extended absence for medical, personal or professional reasons, you're strongly encouraged to communicate formally so options can be explored while they still exist. Once attendance drops below 50%, the available paths narrow to extending enrolment or re-enrolling in missed modules, with fees applicable.
If the program runs past its end date because of changes you made, do I pay more?
No. Where an extension results from changes we made, no additional fee applies and mentorship and placement support continue through it. The one separate case is where your own attendance falls below 50% — extending or re-enrolling then does attract fees under our standard policy.
Mentors and teaching
Are your mentors full-time staff or working practitioners?
Working practitioners, and that's deliberate — it's how you get the decisions that don't appear in textbooks: why a team shipped the less accurate model, what breaks in production, what a hiring manager actually probes. It also carries an honest cost. People with live jobs occasionally have work conflicts, which is a real source of rescheduling. We think the trade is worth it, and the answer to the cost is notice and continuity rather than pretending it doesn't exist.
Will I have the same mentor throughout the program?
Usually, though it's not something we'd promise across a program running many months. What is guaranteed is continuity: an incoming mentor receives your batch's progress record, outstanding doubts and project status before their first session. You should never be asked to re-explain where your batch had reached. If you are, that's a failure on our side and worth flagging immediately.
Why do mentors change at all?
Ordinary reasons, mostly — a practitioner's work commitments shift, someone relocates, a specialisation module needs a different expert. The problem was never that changes happen; it's that they used to happen without a handover. That's what the progress record exists to fix.
What if I don't get on with my assigned mentor?
Raise it, and raise it early rather than enduring it. Start with your academic coordinator — reassignment is usually straightforward and nobody treats it as a complaint about the mentor. If the concern is more serious than a poor fit, our grievance process explicitly covers conduct complaints involving trainers and staff, with confidentiality protected and retaliation for a good-faith complaint treated as a violation in its own right.
So why do some learners report longer timelines?
Two different causes, and it's worth separating them. Sometimes a batch genuinely needs more sessions on hard modules, which is the buffer working as designed. Sometimes it's rescheduling or a mentor change — that's operational, it's ours, and it's why we now commit to 72 hours notice, confirmed replacement slots and a formal handover when faculty change.
Pace and depth
What if my batch needs more time on a topic?
You get it. That's exactly what the buffer is for — a mentor can add a session on a difficult module without your end date moving. We'd much rather use a buffer week than leave a cohort behind.
Who decides when a buffer week gets used?
Your mentor, based on how the batch is actually performing — assessment results, the questions still arriving in doubt sessions, how project work is going. It doesn't require sign-off from anyone senior, which is the point: a mentor who has to request permission to slow down will simply not slow down.
What happens to buffer weeks the batch doesn't need?
They go to revision, extra project time, or interview preparation brought forward. They don't shorten the program, because your end date is a commitment in both directions — you shouldn't have to re-plan around finishing early any more than around finishing late.
I learn quickly. Will I be held back waiting for the rest of the batch?
No, and this is a fair thing to ask about a program that promises not to rush anyone. Live classes move at the batch's pace, but almost nothing else does. Project work, self-study, additional problem sets and one-to-one mentorship all run at yours — and a learner who's ahead should be going deeper rather than sitting still. Tell your mentor you have headroom and ask for harder problems. The most common mistake fast learners make is coasting through the middle of a program and then discovering their projects are no deeper than anyone else's.
What if I'm slower than everyone else in my batch?
Then you're the reason doubt sessions exist, and you should use them without apology. Most learners who fall behind don't do it because the material is beyond them — they do it because they stopped asking around week six when they felt behind, and the gap compounded quietly from there. Ask early, ask basic questions, and use one-to-one sessions for the things you'd rather not raise in a group.
If two people are stuck, does the whole batch wait?
Not in the live class — that would be unfair to everyone else, and it isn't what the live class is for. It's what doubt sessions and one-to-one mentorship are for: individual gaps get closed in the format built for them, without holding twenty other people. Where a substantial part of the batch hasn't followed something, that's different, and that's when a buffer session gets used.
Can I skip modules I already know?
You can move quickly through content you're confident in, and you should — spend the time saved on your weaker areas instead. What you can't skip is the assessment: all prescribed tests are compulsory unless explicitly marked optional, and passing them is a certification requirement regardless of your prior experience. In practice, that's useful. Learners are frequently more confident about a topic than an assessment shows they should be.
How do you decide a batch is ready to move on?
Assessment performance, the questions still coming up in doubt sessions, and how project work is landing. Not the calendar. If those signals say the batch hasn't got it, moving on doesn't save time — it manufactures a bigger problem two months later, when the gap has compounded and nobody can locate where it started.
Will a longer timeline delay my placement support?
It can, and here's the mechanism: certification requires 75% attendance, passed assessments, approved projects and cleared dues — and certification is a prerequisite for placement eligibility. Pending work delays entry into the placement process, not just your certificate.
Planning your own time
How many hours a week do I need?
12–15, spread across the week rather than concentrated. Two hours on four days beats eight hours on a Sunday, because spacing is what keeps material alive until an interview months later.
What if I genuinely don't have 12–15 hours a week?
Say so before you enrol rather than discovering it in month three. A program is a poor purchase at any price if the hours aren't there, and we'd rather lose the enrolment than have you spend money on something you can't attend. If your constraint is temporary — a heavy quarter at work, for instance — talk to your coordinator about which intake to join instead.
Is it better to study a little every day or in long weekend blocks?
Little and often, and this is one of the clearest findings in the research on learning rather than a matter of preference. Distributed practice beats massed practice for retention at equal total hours. Five hours on Sunday and nothing until the next Sunday means six days of forgetting between every session, and it's the most common failed study pattern there is.
When should I start applying for jobs?
Interview preparation runs inside the closing phase of your program, and applications should begin around then rather than after you finish. Learners who wait until the program ends before starting a search add their entire search duration to the end of an already long timeline. Overlap the two.
How do I revise older modules without falling behind on the new one?
Give it one fixed slot a week — the Sunday block in the template above — rather than trying to fit it around everything else. It doesn't need to be long. Thirty to sixty minutes of closed-book self-testing on a module from two months ago is enough to keep it retrievable, which is the entire objective. What kills month-two knowledge isn't insufficient revision; it's zero revision.
How do I know if I've actually learned something, rather than just followed it?
Two tests. Close everything and write down what you remember — if that's difficult, you recognised the material rather than learned it, and recognition doesn't survive an interview. Then explain it to someone non-technical. The point where you reach for jargon is the point where your understanding stops.
I'm falling behind. What should I do?
Tell us early. If you can see a hard period coming — work travel, illness, exams — inform your mentor in advance, and flag unplanned absences within 24 hours. There are options while you're above the attendance threshold and considerably fewer below it.
Are recordings enough if I miss a live session?
They'll help you catch up on content, but they don't count toward attendance except where the academic team approves it in writing for a specific session — and a recording can't answer the question you have while watching it. Treat them as revision, and bring what they don't resolve to your next doubt session.
What's the single most useful study habit?
Closed-book self-testing. It's the most consistently supported technique in the research, it costs no extra time because it replaces re-reading rather than adding to it, and it rehearses the exact format of a technical interview.
Program schedules, attendance requirements, assessment and re-test rules, certification criteria and the grievance process are set out in full in our Student Policies & Guidelines.
