Resume vs Portfolio vs GitHub: What Gets You Shortlisted at IIT NIT Placements

Your resume has a 7.4 CGPA, three internships, and a project that 'used Machine Learning to predict stock prices.' So does literally everyone else in your batch. The brutal truth about IIT NIT placements is that getting shortlisted has nothing to do with working hard and everything to do with being strategically visible. Resume, portfolio, GitHub — you've heard all three terms thrown around in every pre-placement talk. But nobody actually tells you which one moves the needle.

Let's fix that right now.

The Placement Game Nobody Explains Honestly

Campus placements at IITs, NITs, BITS, and IIITs follow a specific filtration funnel. Companies shortlist, then test, then interview. The shortlisting stage is where 80% of students get eliminated before they even open their mouths.

Here's what most PPT sessions don't tell you: different roles and different companies weight your resume, portfolio, and GitHub profile completely differently. Treating all three as interchangeable is how you end up shortlisted for roles you don't want and invisible to the ones you do.

What Your Resume Actually Does (And What It Doesn't)

Your resume is not a document. It's a filter-pass ticket. Its only job is to get you past the ATS bot and the two-minute HR skim. That's it.

What makes a resume work in campus placements:

• Clean single-page format — no tables, no columns, no designer templates that ATS systems misread
• Quantified impact in every bullet: not 'built a recommendation system' but 'built a recommendation system that reduced churn by 18% for 10K users'
• Keywords from the exact JD copy-pasted into your experience section — this is not cheating, this is literacy
• CGPA above the cutoff, prominently placed — yes, it still matters at most core and product companies
• Relevant coursework only — nobody cares about your Engineering Drawing elective

What your resume cannot do: show depth, show taste, show how you actually think. That's not its job. Stop asking it to do things it was never built for.

The Resume Mistake Most Students Make

Padding. Two-line projects that were tutorials in disguise. 'Proficient in Python' when you've written exactly one Jupyter notebook. Recruiters from Microsoft, Google, Goldman, and McKinsey have seen thousands of IIT NIT resumes — they pattern-match fluff instantly.

If your resume is a highlight reel of things you technically did but can't speak to for 10 minutes, fix that before placements hit.

GitHub: The Cheat Code That Most Students Waste

For software, data, and product engineering roles, your GitHub profile is the single most powerful shortlisting asset you have — and the majority of students treat it like a graveyard for half-finished tutorial clones.

Here's what a strong GitHub profile actually looks like to a senior engineer reviewing your application:

• Consistent contribution graph — green squares over months, not a 3-day burst before applications open
• READMEs that explain what the project does, why it exists, and how to run it — in plain English
• Original projects, not forks of popular repos you've never touched
• Clean commit history — not 'final final FINAL version 3' as your commit message
• At least one project with real users, a live deployment, or meaningful stars

Students at NIT Trichy and IIT Madras who get into top product companies consistently say the same thing: the GitHub link on their resume did more work than any bullet point. Because it shows, not tells.

GitHub Red Flags That Kill Shortlisting Chances

• Empty repositories with only a README
• 100% forks with zero original commits
• Private repositories — if it's not visible, it doesn't exist
• Projects named 'MyProject1', 'Assignment3', 'test123'

Fix your GitHub before you fix your resume. Recruiters at companies like Atlassian, Razorpay, and Zepto check profiles directly.

Portfolio: When It Matters and When It's Overkill

A portfolio is context-dependent. For most core engineering and quant finance roles, nobody will look at your portfolio website. For design, product management, front-end development, data science, and UX — it's non-negotiable.

What a good portfolio does:

• Shows your thinking process, not just the output
• Demonstrates taste — visual hierarchy, clean writing, intentional design choices
• Tells a story about who you are as a problem-solver
• Lives at a custom domain (yourname.dev or yourname.in costs under ₹800/year — no excuses)

Students applying for PM and design roles at companies visiting BITS campuses or IIITs frequently skip the portfolio entirely and then wonder why they keep failing shortlisting for those specific profiles. The portfolio isn't a vanity project. It's proof of craft.

What to Actually Put in Your Portfolio

• 2-3 deep case studies, not 10 shallow project thumbnails
• One project that shows you went beyond the brief — you iterated, you tested, you improved
• A short 'About' section that sounds like a person wrote it, not a LinkedIn summary generator
• Contact information that works — broken contact forms are a silent application killer

The Real Shortlisting Framework: Which One Wins by Role

Stop thinking about resume vs portfolio vs GitHub as a competition. Think of it as a role-specific stack that you deploy strategically.

• SWE / Backend / Full-Stack roles: Resume (60%) + GitHub (40%). Portfolio optional but bonus points.
• Data Science / ML roles: Resume (50%) + GitHub with notebooks/models (40%) + Portfolio case studies (10%)
• Product Management: Resume (40%) + Portfolio with PM case studies (60%). GitHub irrelevant.
• UI/UX / Design: Portfolio (70%) + Resume (30%). GitHub only if you write component libraries.
• Core Engineering / VLSI / Civil: Resume (80%) + Academic projects document (20%). Portfolio largely irrelevant.
• Quant / Finance / Consulting: Resume (90%) + academic pedigree. Neither GitHub nor portfolio moves the needle here.

Knowing which stack applies to your target role is the difference between a smart application and a scattered one. Students from NIT Warangal placement cells consistently advise tailoring your digital presence role-first, not as a generic 'personal brand' exercise.

The One Thing That Actually Ties It All Together

None of these documents exist in isolation. What shortlists you is consistency across all three surfaces. If your resume says you built a recommendation engine, your GitHub should have that repo, and your portfolio (if applicable) should have a case study explaining your approach.

Inconsistency is the fastest way to get flagged in interviews even after you clear shortlisting. Recruiters cross-reference. Senior engineers Google you. HR checks LinkedIn against your resume.

Build a coherent narrative. Every project, every role, every skill claim should point toward the same version of you.

Getting Your Placement Mindset Right

The students who clear placements at IITs and NITs aren't necessarily the ones with the best CGPA or the most side projects. They're the ones who treat shortlisting as a craft — who understand the game well enough to play it intentionally.

That same intentionality shows up in how they carry themselves on campus too. There's a reason the sharpest people in your placement batch are usually the ones who show up to mock interviews and company PPTs in a clean 320GSM heavyweight KS Verse hoodie — not because it's a uniform, but because they sweat the details everywhere. The ones rocking IIT Kharagpur campus drops in their placement prep season know that identity and presentation matter, whether it's your GitHub README or what you walk into a pre-placement talk wearing.

Placements are high-stakes. Your 240GSM oversized campus tee and your polished resume both say something about how seriously you take the craft of showing up.

The Actionable Checklist Before Placement Season Hits

• Audit your GitHub — delete dead repos, write proper READMEs, deploy at least one project
• Quantify every resume bullet — if you can't put a number on it, question whether it belongs
• Decide your target role stack and build only the documents that role actually needs
• Get your resume reviewed by someone who has actually hired people, not just someone who has been hired
• If you need a portfolio, build it before October — not the week companies arrive
• Cross-check your resume, GitHub, and LinkedIn for consistency

The students who get shortlisted aren't the ones who worked the hardest in college. They're the ones who understood the system clearly enough to work it. Now you do too.