How it works
From your first class to your capstone.
Here is exactly what happens when you join CodeBakerz — what you do each week, how you are reviewed, and how you get from zero to a finished project.
Step by step
Your journey at CodeBakerz.
Step 1Optional
Book a free demo class
Join a live demo online, meet the mentor and see how a batch works. The mentor can suggest the right program for you.
Step 2
Create your account
Sign up with your name, email and phone. If the student is under 18, we also ask for a parent or guardian's name, phone and consent — as India's DPDP Act 2023 requires.
Step 3
Choose a batch and plan
Pick the program, a batch timing that suits your week, and a plan: monthly auto-pay or quarterly prepay (10% off).
Step 4
Pay securely with Razorpay
Pay with UPI Autopay or a card through Razorpay. We never see or store your card or UPI details. For under-18 students, the parent is the payer.
Step 5
Join the community and live classes
You are added to your batch group in the CodeBakerz WhatsApp Community and get your Google Meet class links and timetable.
Step 6
Weekly assignments and mentor review
Every week you get an assignment. Submit it on time and the mentor sends written feedback on what to improve.
Step 7
A project every month
Each month ends with a project — built with Git, a README and a code review, then pushed to your GitHub.
Step 8
Capstone and certificate
In month 6 you plan, build and present a capstone project. Complete it and you receive your CodeBakerz level certificate.
Industry level
What "industry level" actually means.
Real software is built by teams, with tools and habits that keep the work organised. You practise these in every program, so your first job or internship does not feel like a new world.
Git and GitHub
Every project is version-controlled, with branches and commits like a real team.
Tickets
Work is split into small tasks with clear 'done' criteria, just like at a company.
Standups
Short check-ins: what you did, what is next, what is blocking you.
Code review
A mentor reviews your code and explains how to make it better.
Deadlines
Assignments have due dates, so you learn to plan and ship.
Documentation
You write READMEs so anyone can run and understand your project.
A typical week
Two classes, one lab, one assignment.
School batches meet on weekends plus one weekday evening. College batches meet on weekday evenings. Here are two examples from our programs.
- Saturday
- Live class · 90 minutes · new concept + guided coding
- Sunday
- Live class · 90 minutes · practice and mini-project
- One weekday evening
- Doubt and lab session · ask anything, fix your code with the mentor
- During the week
- One assignment (about 2–3 hours) with written feedback
- Two weekday evenings
- Live classes · 90 minutes each · concept + hands-on build
- Weekend
- Lab session · doubts, code review and pair programming
- During the week
- One assignment or sprint task with written feedback
Attendance and recordings.
Live classes work best when you are there — you can ask questions and code along. But life happens, so nothing is lost if you miss one.
- Attendance is marked for every live class and shown in the monthly progress report.
- Every class is recorded. Recordings are visible only to students of your batch — never public.
- Missed a class? Watch the recording before the next one and bring doubts to the weekly lab session.
- Batches are capped at 30 students, so the mentor knows who is keeping up and who needs help.
- Parents of under-18 students receive the monthly report with attendance, assignments and mentor remarks.
Baking your code to give you a pie
Start with one free class.
Join a live demo class, meet the mentor and see how a CodeBakerz batch works. No payment, no pressure — decide after.