It’s a Wednesday in week 4. In the squad workroom, six students are working through a front-end assignment that’s due by end of day. The code isn’t elegant. It doesn’t have to be. It has to run.
This is what week 4 looks like. Not week 1, when the schedule looked like a test of endurance. Not orientation, when nobody knew each other’s names. Week 4 is when the rhythm has locked in, and the work has become the point.
Here’s what that week actually looks like, from Monday morning through Saturday afternoon.
Monday: the day opens with DOJO
There’s no warm-up.
At 9 AM, DOJO starts. It’s the same every morning. DOJO is Kalvium’s daily coding practice system: timed problems, no hints, logged at every step. By week 4, students don’t need to be reminded it’s starting. It’s the thing that opens the day.
In Semester 1, the problems run in Python and JavaScript. The focus isn’t on advanced algorithms yet. It’s on reading a problem carefully, forming a hypothesis, writing a small test, and iterating. Students who try to shortcut that loop find the problem comes back in a different form on a different day. Students who follow it discover they’re thinking about code differently by the time the session closes.
DOJO has six belt levels per language: Java, C++, JavaScript, Python. Each belt is tested. By week 4, most Year 1 students haven’t cleared their first belt yet. But the habit is there. That’s what week 4 is actually building.
After DOJO, the first live session of the week starts.
How the live session actually runs
There are no slides being read.
The mentor walks the room. She opens with a question and waits for a real answer. Then she builds on what the student said. If the answer reveals a gap, she asks a follow-up question, not the correction. The student finds the gap themselves. That takes longer than just being told the answer. That’s the point.
What this produces, week after week, is a room that actually thinks before it answers. By week 4, students are asking questions in session that they couldn’t have formed in week 1, because in week 1 they didn’t yet know enough to know what to ask. That sounds small. It isn’t.
The live session runs for about ninety minutes. Then it’s self-paced time.
Self-paced time and what LiveBooks actually is
A short note before going further.
LiveBooks is Kalvium’s digital curriculum: interactive, updated as industry tools change, and built so that exercises are embedded inside the content rather than tacked on at the end. You do the thing while you read about it. It’s also where you submit the work, and where HEROS, Kalvium’s real-time learning system, tracks your progress at the individual level. Mentors see a dashboard. If a student keeps getting stuck in the same section across multiple sessions, the system surfaces it. The mentor knows before the student has decided to ask for help.
Self-paced time on a Monday afternoon rewards students who stayed present in the morning session. The LiveBooks exercises connect directly to what the live session covered. The gap between understanding a concept and applying it usually shows up within the first ten minutes of self-paced work. By week 4, most students have learned to keep a mentor nearby during this block, because that’s when the real questions come out.
Tuesday through Thursday: where the week actually happens
The core of the week is here.
Each day follows a similar shape: DOJO in the morning, live session, LiveBooks work, squad time. But the squad time in the middle of the week is where the most useful things happen.
Squad time isn’t mentored in the traditional sense. The mentor is nearby but isn’t running the session. The squad decides what to work on together, and that means they also decide what to argue about. “I got this part working but I don’t understand why it works.” “Have you tried it with that input?” “I think the problem is earlier than where you’re looking.” These conversations don’t happen by design. They happen because the structure makes them impossible to avoid. You can’t hide in the back. The assignment needs two pairs of hands. And by week 4, the squad has spent enough time together in the same room, working on the same material, that the trust to have those conversations is actually there.
The most useful squad conversations have shifted from “what do we build?” to “why isn’t this working?” That shift is quieter than it sounds, but it’s a meaningful one. It means the squad has moved from figuring out the shape of the task to actually being inside it.
Friday: the build ships
Friday has a hard deadline. By end of day.
Not end of week. Not Monday. End of Friday. Whatever the week’s build is, it’s due then. The submission goes through LiveBooks and is reviewed, not against a marking scheme, but against whether it does what it’s supposed to do. If it doesn’t, there’s feedback.
The build in week 4 isn’t a production application. It’s a structured exercise. A front-end layout that renders correctly. A function that handles the inputs it’s supposed to handle. Something you can show someone and it does what you said it would do.
Getting there by Friday is the goal of the week. By week 4, most students know what the path to that goal looks like from Monday morning. They know it because they’ve run it three times already, and it’s starting to feel like a process rather than a scramble.
That’s the shift. It’s quiet. But it’s the one that matters.
Saturday: the sixth day
Saturday is still part of the week. That’s still strange to most students at week 4.
It’s a shorter day, and the format shifts: more review, sometimes reflection, occasionally a DOJO belt test. But it’s a working day. The six-day structure isn’t punitive. It’s the honest math behind building a serious skill. Eight hours a day, six days a week, sustained over four years, means the work is getting done at a point when most peers are still deciding what the work should be.
By week 4, most students have stopped thinking of Saturday as the day that shouldn’t exist. It’s become the day the previous five days get sorted.
What week 4 is actually building
Week 4 doesn’t produce a portfolio piece. It doesn’t produce a DOJO belt for most students.
What it produces is a default mode.
The assumption that today will begin with practice. That a problem is worth thinking about before the first line of code. That the person next to you sees it differently, and that’s useful rather than inconvenient. That a deadline is a deadline, not a suggestion.
These defaults don’t look impressive. They’re not the kind of thing that fits on a brochure. But they’re what the rest of the programme runs on. By the time a Kalvium student reaches Year 2 and starts work-integrated projects from Semester 3 onward, these habits have been running for two semesters. By the time a placement cycle opens, the question “walk me through your last build” doesn’t feel like a test. It feels like a Tuesday afternoon in the squad room.
For the full picture of the programme, the complete guide to Kalvium for families has everything a family needs before deciding. The first week that sets this rhythm in motion tells what changes between day one and day seven for three students who walked in on the same Monday. For how the DOJO hours and squad sessions translate into the placement cycle, here’s what the interview process looks like from the student side. And for the learning science behind why the programme is built this way, the research that explains the design is worth reading alongside this.
What we noticed watching week 4
Three things stay with you when you watch a Year 1 cohort move from week 1 to week 4.
One. The students who find the rhythm fastest aren’t the ones who came in with the most prior experience. They’re the ones who stopped waiting to understand something before trying it. That disposition is easier to build in week 4 than in week 1 because by week 4 there’s evidence it works.
Two. DOJO’s daily cadence changes what students think is possible. In week 1, the first problem in a session feels large. By week 4, it’s smaller, not because the problems are easier, but because students have now solved something every single day for a month. The practice doesn’t just build a skill. It changes the starting assumption about what one can do.
Three. Week 4 is the week the squad becomes real. Before week 4, the squad is people you’ve been grouped with. After week 4, it’s the group you debug with. That isn’t something you can schedule. It’s what happens when you give people a hard problem, not enough time, and ask them to figure it out together, repeatedly, until figuring it out together is just how they work.