PROOF-OF-WORKB.Tech Year 1 Program
Register →

B.Tech · Year 1 · Weekend Program — Rev 2026–27

Don't just earn a degree.
Graduate with proof.

A year-long weekend program that takes 1st-year B.Tech students — any branch — from “undecided” to a public portfolio of real projects, AI fluency, and interview-ready confidence.

Register for the 2026–27 Batch → See the program

Limited seats Starts August Saturdays + Sundays

Why this program exists

Half of India's engineering graduates are unprepared for hiring. Not because jobs are gone — because hiring changed.

01

Companies now hire on proof-of-work — projects you've built, publicly visible, not just a CGPA line.

02

60–70%of fresher job descriptions now list AI skills — even in non-AI roles.

03

Resumes are screened by AI before a human ever reads them.

04

Meanwhile core branches are booming — semiconductors, EVs, embedded systems — but most colleges don't teach ECE, EEE, or ME students the path to it.

Your degree makes you eligible. Your proof-of-work gets you hired.

The build — 10 months, 20+ weekends

One year. Twenty-plus weekends. A portfolio that speaks before you do.

Sat = hands-on lab. Sun = career & communication studio. Every month ends with something you can link to.

  1. Phase 0 · Weekend 0

    Kickoff

    Honest data on how hiring actually works today, the program contract, and your dev setup — Python, VS Code, Git, GitHub. You leave with a personal "why" statement.

    0
  2. Phase 1 · Months 1–4 · Everyone together

    Foundations

    Git & GitHub, Python by building real tools (not slides), pandas on your own state or district's open data, problem-solving and aptitude drills — then AI fluency: how LLMs actually work, prompt discipline, and building + deploying your own AI helper.

    1
  3. Phase 1 · Month 5

    Showcase 1

    Technical writing, LinkedIn presence, and Resume v1 — then Demo Day #1: five-minute project demos, peer scoring, an industry guest. Track counseling assigns your semester-2 branch. Winter break: a 20-day build challenge or shadow an engineer.

    2
  4. Phase 2 · Months 6–8

    Branch tracks

    Real projects in your own field, in mixed-branch teams. GD practice, mock HR questions, and aptitude drills continue every Sunday.

  5. Phase 2 · Month 9

    Capstone sprint

    Cross-branch teams build ONE substantial thing — hardware and software together, like a real engineering team — with weekly mentor reviews and a public GitHub + README standard.

    4
  6. Phase 2 · Month 10

    Launch

    Portfolio polish, Resume v2 built for AI screening, mock interviews with external volunteers, GD rounds — then Demo Day #2 with faculty and industry guests, and your certificate, if you've earned it.

    5

Every week, all year: aptitude Q-of-the-week, English speaking circle, one industry-news discussion. Placement prep as a habit, not a final-month panic.

How we run it

We run this program the way companies run teams.

  • Every month, one PUBLIC artifact. GitHub is your transcript — not a grade sheet nobody outside your college can read.

  • Mixed-branch teams, always. CSE students learn hardware. ECE, EEE, and ME students learn to ship software.

  • "AI writes, you review." Predict the output before you ask AI for it — we teach you to command AI, not depend on it.

  • Certificate earned, not given. See the criteria below.

EARNED · NOT GIVEN · EARNED · NOT GIVEN · CERTIFICATE OF BUILD
  • ≥ 80% attendance across the year
  • ≥ 3 shipped, public projects on GitHub
  • 1 Demo Day presentation, in front of judges

Questions

Before you register.

1I'm from ME / EEE — is this just coding?
No. Semester 2 has a dedicated track for every branch — CAD and mechanisms for ME, motors and EV systems for EEE. Core engineering is exactly where hiring is growing fastest right now.
2I've never written code. Can I keep up?
The program assumes zero background. Month 1 starts at setup and basics, and you get 1-to-1 doubt-clearing sessions whenever you need them.
3Will this affect academics?
Exam months have light weeks by design. The weekly load is about 7 hours, weekends only — Saturday labs, Sunday studio.
4What do I actually get at the end?
A public portfolio — GitHub and a personal site — five-plus finished projects, one capstone, real interview experience, and a certificate, if you earn it.

Registration

Four years pass either way. Graduate with proof.

Register for the 2026–27 batch before seats close. Weekend commitment, year-long payoff.

Register Now →

Seats capped are limited for mentoring quality.