Code review
Line by line on a real repository. Structure, naming, tradeoffs, and what a reviewer at a product company would block in a pull request.
Loading programs
Two ways to work with a mentor directly: take the whole program privately at your own pace, or book sessions by the hour to unblock something specific. Same mentors either way.
01 — Pick your shape
This is the only decision that matters on this page. Everything below is detail on whichever one you pick.
The same curriculum as the cohort — 76 sessions, 12 projects, the deployed capstone — except it is you and a mentor, on a schedule you set, moving at your pace.
4 months · One-time · Lifetime access
You can already build. You are stuck on a specific decision — an architecture you cannot defend, a round you keep failing, an offer you do not know how to answer.
1 hour each · Add as many as you need
02 — Honest routing
Most people should take the cohort. It is the cheapest option here and for the majority it works better — the pressure of a room is part of why it works. Private is for when that genuinely does not fit.
| Compare | CohortGroup of 25 | Private program1:1, full curriculum | SessionsBook by the hour |
|---|---|---|---|
| Best for | You want the whole skill and can commit to a fixed schedule | You want the whole skill but cannot make fixed timings | You already build and are stuck on one thing |
| Scope | 76 sessions · 12 projects | 76 sessions · 12 projects | Whatever you bring |
| Schedule | Fixed, Mon–Fri evenings | Agreed with you, movable | Booked by the hour |
| Pace | Cohort pace, 4 months | Yours — faster or slower | N/A |
| Peers | 24 others on the same track | None — this is the tradeoff | None |
| Code review | Weekly, 1:1 | Every session, 1:1 | In the session |
| Interview prep | Included | Included | Book as a mock round |
| Price | ₹24,999 | ₹74,999 | From ₹1,549 / hour |
The private program costs three times the cohort because it is three times the mentor hours. If your reason for going private is only that a cohort feels intimidating, take the cohort — that feeling passes in week two and you keep ₹50,000.
03 — Private program
Nothing is removed and nothing is abbreviated. The only things that change are who is in the room and when the room opens.
Python to a deployed AI product · 4 months
Full StackEnd-to-end portfolio · 4 months
BackendAPIs, data and system design · 4 months
FrontendUI engineering at product standard · 4 months
In the cohort: Fixed Mon–Fri evening slots
Privately: Slots agreed with you, moveable when work explodes
In the cohort: Cohort pace — everyone moves together
Privately: Skip what you know, dwell on what you do not
In the cohort: Generic project briefs
Privately: Projects aimed at your target role or your actual product
In the cohort: Weekly review window
Privately: Review in every session, because every session is yours
You lose the cohort. No peers, no group review, no one else struggling with the same bug on Thursday.
The curriculum is identical. You are buying flexibility and attention — not extra content.
04 — Single sessions
Sessions work best when they are narrow. Pick the thing that actually blocks you — you can always book another.
Line by line on a real repository. Structure, naming, tradeoffs, and what a reviewer at a product company would block in a pull request.
High-level and low-level design for something you are actually building — or for the round you are about to sit.
A real round with real pressure, then honest feedback on what would have failed you and how to fix it before it counts.
A roadmap from where you are to the role you want — including the offer conversation most engineers handle badly.
05 — Process
The form asks what you are stuck on, or what you want to learn, and a link to the code. Context up front is worth twice a session that starts with introductions.
Before any money moves. We tell you which of the three options fits — including when the answer is the cohort, or nothing at all.
Matched on what you actually need — not whoever is free. If nobody is a genuine fit, we say so rather than sell you a slot.
Every session ends with a written summary: decisions made, what to read, the next concrete step. So the value survives the call.
06 — Before you book
Yes — all 76 sessions, all 12 projects, the same capstone. Nothing is cut and nothing extra is added. You are paying for scheduling flexibility and undivided attention, not for more content.
Yes. You pay the difference, prorated against the sessions you have already attended. It happens most often when someone changes jobs mid-cohort and the evening slot stops working.
Often, yes — three months is common if you already know the early material and can give it more hours a week. The projects still have to get built and reviewed, and that sets the floor.
For code review or system design, yes — bring a repository, even a messy one. For career strategy or a mock interview, no code is needed.
Tell us within 24 hours and we will rematch you with a different mentor at no extra cost. A bad match is our error, not your problem — but fees are not refunded, so the free fit call exists to catch a mismatch before any money moves.
No, and we would rather say so. A few hours cannot substitute for four months of structured practice. If you cannot build the thing at all yet, a program is the honest answer — cohort or private.
Twenty minutes, free, before anything is decided. We will tell you which of the three options fits — including when the answer is that none of them do.