There’s something in F1 that most people watch without seeing.
Everyone watches the race. The overtakes, the pit-stop drama, the fight for position through the final corners. What doesn’t make the broadcast is the conversation in the garage before dawn: about tyre compounds, aerodynamic balance, and the setup the team committed to before the car ever left the pit lane. Every circuit is different. The lap characteristics change. But what travels from Monaco to Silverstone to Singapore unchanged is the mechanical philosophy built into the car. Races aren’t won on the track. They’re won in the garage.
I’ve been thinking about that since the number 2,223 started appearing in our materials.
2,223 students. Nine campuses. Six states. That’s not marketing copy. It’s a test: can a demanding, rigorous programme hold what it is when it travels across that much geography?
That’s the question worth actually asking.
What the number means
The 2,223 figure comes verbatim from the Prospectus and Curriculum Guide: “Chosen by 2,223 students across India and counting.”
It’s cumulative. All four years, all active campuses, all geographies. A student who enrolled in 2022 is finishing their degree this year. A student starting now is entering a programme whose Semester 3 already has students working at companies.
The seat spread for AY 2026-27 is 770 total. Tamil Nadu has three campuses: AMET University (120 seats, Chennai), KARE (60, Srivilliputhur), and St Joseph University (60, Chennai). Karnataka has two: Yenepoya Bengaluru (120) and Yenepoya Mangaluru (60). Andhra Pradesh has SRM University (120, Amaravati). Further north: LPU with 120 in Phagwara, SGT University with 60 in Gurugram, and JECRC University with 50 in Jaipur.
When testimonials arrive from students at JECRC, at KARE, at LPU, at SRM, and at Yenepoya, that’s the actual geographic spread. Students from genuinely different university environments working through the same programme.
That’s the claim worth examining.
The risks that scale introduces
I want to be honest about what’s hard here before I say what works.
When a programme runs at one campus, gaps are visible quickly. The mentor who isn’t catching a student who’s struggling. The session that fell flat. The moment when a challenge was two belt levels ahead of where a student actually was. You notice. You fix it.
At nine campuses across six states, the gap between design and execution has more places to hide. Quality consistency becomes a real problem, not just an aspiration. The mentor:student ratio that felt manageable at 200 students needs to hold at 2,223. The professional culture around feedback, deadlines, and collaborative work that forms naturally in one tight cohort has to be deliberately constructed when the cohort is distributed across the country.
These aren’t hypothetical risks. They’re the specific failure modes any serious programme design at this scale has to address. The research on what makes engineering education actually work is clear: delivery mechanism matters as much as content. Scale makes delivery harder.
The particular challenge with programme quality at scale is that small failures don’t announce themselves. A student who misses a week of DOJO accumulation doesn’t send a signal to the core team. A session that consistently runs shallow at one campus doesn’t appear in a summary report. The failure mode is slow drift, not sudden collapse.
So what does the design do about it?
What holds constant
Four systems run identically across all nine campuses.
HEROS is the real-time learning monitoring system. It tracks student learning activity across every session and milestone, identifies gaps early, and enables timely mentor support. When a student at KARE in Srivilliputhur hasn’t engaged with a module in three sessions, the system flags it. When a student at LPU in Phagwara is stalled at the same point in the DOJO progression that another student cleared last week, a mentor can see both the pattern and the specific student. HEROS doesn’t guarantee a correct response. It makes the wrong response harder to miss.
Live Books are the digital curriculum. They update simultaneously across all campuses when industry practice shifts. A student at SGT in Gurugram is working from the same current version as a student at Yenepoya in Bengaluru. The curriculum isn’t a printed textbook sent out at the start of Year 1. It’s a living document that travels with the programme.
DOJO runs daily coding practice at every campus. Six belt levels per language, each requiring demonstrated performance before the next opens. The belt progression is the same at AMET as it is at SRM. A student in Chennai and a student in Amaravati are working toward the same calibrated milestones, at the same daily volume.
The Squad structure creates the peer layer. Students work in numbered cohort groups with mentor pairs, designed to catch problems close to when they appear rather than at the end-of-term review. The squad isn’t a campus-specific feature. It’s the same structure everywhere.
The charter the whole programme runs on is direct about it: Build Yourself First. The standard, it says, is non-negotiable.
What differs, honestly
The university provides the physical infrastructure. That means location matters.
Hostel quality, campus facilities, city context, local peer networks: these vary across the nine campuses, and none of it is irrelevant to a four-year experience.
Tuition fees differ significantly by university. AMET runs at ₹2,25,000 per year. Yenepoya Mangaluru at ₹2,26,000. St Joseph Chennai at ₹2,30,000. KARE at ₹3,00,000. JECRC and SGT at ₹3,25,000. Yenepoya Bengaluru at ₹3,26,000. LPU at ₹4,00,000. SRM Amaravati at ₹4,60,000.
Across four years, that’s a total difference of more than ₹9 lakhs between the lowest-cost and highest-cost campus. Kalvium itself collects only the ₹1,200 KNET registration fee. Tuition is paid directly to the university per its own structure.
What the design doesn’t claim is that all nine campuses deliver the programme identically at the execution level. The programme design is the same. Whether that design performs equally on the ground at every campus is an ongoing question, not a settled claim.
For a family deciding between campuses, the honest frame is: the programme you’re choosing is the same, but the place you’re choosing is different. Both matter.
The honest position
2,223 students is evidence that the design can travel. It isn’t evidence that the delivery is perfect.
What we have is a set of systems, HEROS, Live Books, DOJO, and the Squad structure, built to hold the standard across distance. What we’re learning is whether they do, and where the gaps are. That’s the work that doesn’t appear in a Prospectus, because it’s iterative, and honesty about it matters more than a clean claim.
Here’s the thing about scaling a philosophy rather than scaling a recipe. A recipe can be reduced to temperatures and quantities. A philosophy has to be held in the people who deliver it, in the design of what students actually do each day, and in the systems that catch drift before it compounds. That’s harder. It’s also the only kind of consistency that actually matters for something like this.
After every F1 race, the team runs a debrief. Not about whether the car was fast. About where the setup was wrong, what the telemetry said at corner 9, where pace was left on the table. The race is public. The debrief isn’t.
We’re in the debrief phase of running a programme at this scale. Not because things are going badly. Because the calibration is never finished.
I suspect it never will be.
Deepak is a co-founder of Kalvium. He writes at the intersection of education design, philosophy, and how engineering careers are actually built. Read more from Deepak or explore the B.Tech category.