How the school works
Read. Build. Ship. Compound.
Four verbs. The whole method. The full curriculum is free and public. The platform is free, forever. A small live cohort exists for those who want it. The rest of this page explains how all of that fits together.
What we are doing
The promise.
The vision, 2036. When a recruiter wants to know if an Indian engineer can actually build, the answer they trust most is a CTOschool profile. The trust is the asset; we just produce the asset. If we ever do something that doesn't make a CTOschool profile more trusted, we shouldn't do it.
The mission, now. Make CTO-grade education the default for every Indian engineering student — by publishing the full curriculum free, giving every learner a public profile to ship into, and running a small live cohort for those who want one.
The verbs matter. Publish, ship, post, compound. Not teach, deliver, certify, place.
The rules of decision
Four values. Real constraints.
The values are not a wall poster. They are how we decide. When a marketing draft, a pricing change, or a partnership opportunity contradicts one of them, the value wins.
Proof over claims.
When we want to make a point, we show a learner's profile. Never aggregate numbers. Never adjectives. If we cannot point to one specific learner doing one specific thing, we say nothing.
Open over closed.
The curriculum is published in public, free, forever. The platform is free, forever. The work our learners do is public by default. Anything that pulls us toward gating, paywalling, or hiding pulls us away from the school we are choosing to be.
Discipline over talent.
A learner who codes thirty minutes a day for a year out-builds a learner who codes four hours every Sunday. Everything we run is built around the daily streak.
Honesty over hype.
We do not promise jobs. We do not run discount urgency campaigns. We do not promise transformation. We promise a system, and we are clear that the work is the learner's.
How the work actually happens
Four verbs. Four stages.
The whole school is shaped around four verbs. Daily for a year. That is the system.
Read the chapter.
~130 chapters across six phases, every chapter readable without an account. Read at your pace. The roadmap is published; nobody is grading you on speed.
Build the project.
Every chapter has a project brief. The brief is intentionally smaller than what you think you need; you will discover what is missing as you go. That is the school working.
Ship to your public profile.
A screenshot. A deployed link. A Loom walkthrough. A learning from an 11pm bug. Every post lands on ctoschool.live/yourname, dated and public.
Watch it compound.
Day 1 is one post. Day 90 is a portfolio. Day 365 is a credential. The math of compounding is doing the work daily, in public, where nobody can argue with the dates.
The rhythm. One post a day. One shipped build a week. One capstone-shaped artifact a month. If a learner shows up to that rhythm — even alone, even free, even without ever buying anything — the body of work follows.
What the paid version adds
The cohort.
The school is free. The cohort is optional. Some learners want the discipline of a live 8pm session, direct mentorship on every post, and a demo day in front of real builders. For them, we run a small twelve-month program, once or twice a year, by application.
The cohort runs through the same Zero-to-CTO roadmap. The chapters are the same. The projects are the same. What the cohort adds is live discipline.
More about the school
What we believe. What we refuse.
The manifesto is the 318-word belief statement. The founder reads it aloud at every cohort opening; new hires read it on day one. It does not change.
What we don't do is ten commitments that keep the brand from drifting into the patterns that make tech education distrust-worthy. The discipline that protects the school from itself.