For two decades, the deal at India’s Tier-1 colleges was simple: clear JEE, keep your CGPA respectable, show up in fourth year, and placement season would do the rest. That deal is over — and the numbers proving it are public.
Key takeaways
- Placement season is no longer a safety net: 38% of IIT students who registered for 2024 placements went unplaced — double the 2022 rate.
- New graduates have fallen to 7% of Big Tech hires, and AI has eliminated the “boilerplate junior” role — not the junior who can direct AI.
- The market now pays for verifiable proof of work: real commit history, a contest rating, deployed projects, and demonstrated AI-steering skill.
- Second year is the highest-leverage time to start: interns convert to full-time offers at 63%, and early proof compounds for two full years before placements.
The numbers no placement brochure will show you
RTI disclosures covering all 23 IITs show that of the 21,500 students who registered for 2024 placements, roughly 8,000 — 38% — were still unplaced at the end of the season, double the 19% of 2022. At newer IITs the unplaced share touched 40%.
The global picture is harsher. SignalFire’s State of Tech Talent report found that new graduates now make up just 7% of Big Tech hires, down from 15% before the pandemic — and new-grad hiring overall has fallen by half. In the same research, 37% of hiring managers said they would rather use AI than hire a fresh graduate.
Read those two paragraphs together and the conclusion writes itself: a Tier-1 admit is no longer a job guarantee. It’s an entry ticket to a tournament that now starts two years before placement season.
What actually changed: AI ate the “trainable junior”
Companies used to hire juniors to write boilerplate — CRUD endpoints, form validation, glue code. AI tools now produce that instantly, which is why Stack Overflow’s analysis of the junior market shows the traditional entry path narrowing so sharply.
But look at what job descriptions now ask for: “experience with AI-assisted development workflows” has moved from a bonus line in 2023 to a baseline requirement. The junior who is hired in 2026 isn’t paid to type code. They’re paid to direct AI, review its output, catch what it misses, and ship the result. That is a learnable, provable skill — and second year is exactly when to build it.
Your competition is already public
GitHub’s Octoverse 2025 report shows India added over 5.2 million developers last year — the largest source of new developers in the world — and became the largest open-source contributor base on the platform, ahead of the US. GitHub projects 57.5 million Indian developers by 2030.
Here’s what that means practically: the strongest students in your batch are already building in public. Their commit graphs, contest ratings and deployed projects are visible to any recruiter with a browser. A blank GitHub profile in third year isn’t neutral — next to theirs, it’s a signal.
The second-year playbook
Five moves, in order of leverage. None of them require permission, money, or a placement cell.
- Ship two real projects. Not tutorials — deployed things with a URL, used by at least one person who isn’t you. A mess bill-splitter your hostel actually uses beats a cloned Netflix UI every single time.
- Make your GitHub tell a story. Recruiters read commit history, not star counts. Steady weekly commits on real problems signal more than a one-week hackathon spike. India is now GitHub’s largest open-source contributor base — reviewers know what a genuine graph looks like.
- Hold one verifiable rating. LeetCode, Codeforces — pick one and climb honestly. Ratings are the only skill signal that can’t be embellished on a résumé, which is precisely why serious employers trust them.
- Learn to steer AI, on the record. Build with Copilot or Claude, but review every line, write commits that explain the why, and be ready to defend any file in an interview. “I shipped this with AI and can explain all of it” is the strongest sentence a 2026 candidate can say.
- Do one real internship before third year. NACE’s 2026 data shows 63% of interns convert to full-time offers — the highest in five years — and intern hires are 32% more likely to be retained after one year than hires without internship experience. One real internship in second year compounds into everything after it.
Why second year specifically
Because it’s the only year where the math is entirely in your favour. You have enough fundamentals to build, and two full years for proof to compound before anyone else in your batch starts trying. The student who starts shipping in second year doesn’t compete in placement season — they’ve usually been hired before it begins.
That’s the entire premise Tierones is built on: verified 2nd-year developers from IITs, NITs and IIITs, matched to startups that hire on proof — real commits, real ratings, real shipped work — not on a résumé PDF.
FAQ
When should I start applying for internships?
By the middle of second year. The conversion and retention data above is the reason: internships are the highest-probability path to a full-time offer, and the earlier the first one lands, the longer the compounding runs.
Do startups actually hire 2nd-years?
Yes — because startups hire on demonstrated skill, not graduation year. What they need is evidence they can verify in minutes: a real commit history, a rating, something deployed.
Is a high CGPA still worth anything?
It clears filters; it doesn’t win offers. Treat CGPA as table stakes and spend the surplus hours on proof of work — the data above shows which one the market is actually paying for.
If you’re a 2nd-year at an IIT, NIT or IIIT and you’re already building: request an invite. Verification takes your .ac.in email and your GitHub — nothing else.