Access without a cohort is just a login
The pathway gives you access. It does not give you the people or the practice.
No peer cohort
Nobody on your route at the other three universities. Now there is.
No applied practice
Git, cloud, AI tooling, shipped projects. Assumed everywhere, taught nowhere.
You arrive unprepared, alone
Alone, at 1 AM, with forty tabs open. That is the default.
Six standing pillars
Run primarily online so members across four universities and every timetable can take part on equal footing.
Coding Foundations
Start from zero. Basics, Git, tooling, and your first live website.
Skill Tracks
AI/ML, cloud, full-stack, data. Multi-week cohorts, mixed across campuses.
Certification & pathway pipeline
Guided cohorts working through pathway-accessible courses and certifications together, plus liaison office hours on transition and course catalogues.
Build Nights
Weekly, drop-in, online. Bring what you are stuck on.
Industry & alumni
Seniors who have been through it, practitioner talks, and a build challenge across all four campuses.
Transition & portfolio
Portfolio reviews and interview practice before you need them.
Built for every stage of the pathway
Not only for people who already build things. Find the row that describes you.
A way in that assumes nothing
Coding Foundations, and people to learn it with.
Fluency before you need it
Certifications and tracks that build the baseline before you need it.
A portfolio that reads abroad
Shipped work, reviewed, and legible outside India.
The cohort your campus doesn't have
Three other universities on the same route. That is the whole point.
Real governance experience
Cross-institutional council roles, cohort ownership, sponsor relationships and a documented technical leadership record.
Recognition that travels
Certificates for LinkedIn, and a real GitHub history.
Three tiers, each earned
Open to any student with active pathway status. Renewed each year.
Learner
Entry: active pathway status. Open registration, no application beyond that.
Full access to Skill Tracks, Build Nights and certification resources.
Builder
Entry: complete one Skill Track and ship two or more reviewed projects in a semester.
Official recognised title, priority access to certification seats and mentorship, and a vote in board elections.
Lead
Entry: nominated from top-performing Builders by the board.
Runs Skill Track cohorts and Build Nights. The board-track pathway.
The council
A board across four universities, with three working teams beneath it: Tech, Marketing, Operations. Seats are applied for.
Working teams
- Tech, building and maintaining the club's technical projects and skill sessions
- Marketing, brand, outreach, and recruitment across all four campuses
- Operations, running events, logistics, and day-to-day coordination
Three-year plan*
Written down so it can be held to. Year one is the one being built right now.
Stand it up
- Founding cohort recruited across partner universities
- First Skill Track cohort launched
- Certification pipeline live
- Faculty Advisor onboarded, first Build Night held
Prove it
- First TSC Build Summit, the flagship hackathon
- First industry sponsor onboarded
- Alumni mentor network formalised
- Project portfolio programme launched; membership expands to more partner universities
Make it the standard
- Recognised as the pathway's flagship technical skilling network
- Build Summit run fully cross-institutionally
- Measurable transition outcome tracking
- Financial self-sufficiency through sponsorship
*Directional, not a promise, priorities may shift as the club grows.
Credentials that travel
Portable recognition, on the two platforms people actually check.
Digital certificates & badges
Signed certificates for Builders and Leads, formatted for LinkedIn.
Identity, credits & letters
Digital ID, project credits, and letters of recommendation for Leads.
Prizes, merch & sponsored seats
Prizes, merch and sponsored certification seats, once we have sponsors.
A real GitHub history
Your project work, pushed as real repositories under your own name.
Code of conduct
Short, and enforced.
- All discourse in Skill Tracks, Build Nights and code review is respectful, critique the work, never the person.
- Harassment, discrimination or exclusionary conduct of any kind is prohibited.
- Submitted project work must be your own, with collaboration and external resources credited transparently.
- The council engages with technology strictly for educational and career-development purposes. It does not endorse any political party, government or ideology, and does not organise protests or advocacy campaigns.
- Concerns go in writing to the General Secretary, escalate to the Faculty Advisor, and are handled confidentially and without prejudice to whoever raised them.
Before you enrol
Do I need to know how to code?
No. Coding Foundations starts from zero, no experience assumed.
Who can join?
Any student with active pathway status at Anurag, Chitkara, Rajalakshmi or Shiv Nadar. Every branch, every year.
Is this a club at one college?
No. It is independent and spans all four universities equally.
Do I need to bring or install anything?
Nothing. It runs online and there is nothing to install.
What does it cost?
Nothing. Membership, Skill Tracks and Build Nights are free to students on the pathway.
How much time does it take?
Build Nights are weekly and drop-in. Tracks run a few weeks, one session each.
What happens to my data?
Stored securely, seen only by the team that needs them, never shared outside the council.