Every year, lakhs of engineering graduates send out the same two-page PDF: college name, CGPA, a "skills" section listing every language they've ever imported, and three projects described in one line each. And every year, recruiters spend an average of six seconds on each one before moving on.
The resume is not how you stand out. It's how you disappear into a pile.
Here is the uncomfortable truth about tech hiring in India right now: the companies worth working for have stopped trusting paper. Too many resumes are inflated, too many are copied, and a CGPA from one college is not comparable to a CGPA from another. What they do trust is evidence — things you have actually built that they can actually see.
Proof of work beats proof of study
A degree is proof that you attended. A project is proof that you can do the job. When a hiring manager can open something you made — click around it, read the code, watch it run — the conversation changes completely. You are no longer "a fresher from tier-3 college". You are "the person who built that".
This is why the strongest candidates without brand-name colleges on their resume keep getting hired over people with better paper. They removed the guesswork.
The proof-of-work path, step by step
1. Build two or three real things — not tutorials
A to-do app followed from a YouTube video proves you can follow a YouTube video. Instead, build something that solves a problem you actually have: a mess bill splitter for your hostel, a train-seat availability alerter, a tool that formats WhatsApp order messages for a family business. Small is fine. Real is mandatory. Real projects generate real decisions — and interviews are made of questions about decisions.
2. Ship it where people can touch it
A project that only runs on your laptop doesn't exist. Deploy it — Vercel, Railway, and GitHub Pages all have free tiers. A working link is worth more than a paragraph of description, because nobody has to take your word for anything.
3. Record a short demo
Most people who open your project won't create an account and explore. A 60-second screen recording of you using the thing — with one line on what problem it solves — is the highest-leverage artifact in your job search. (We wrote a full guide to recording a demo that gets interviews.)
4. Make your GitHub tell the story
When paper is out, your GitHub profile is the resume. Pin your best work, write READMEs that explain the why, and commit regularly enough that the graph shows a person who builds. Our GitHub profile guide covers exactly what reviewers look at.
5. Apply with the work, not around it
When you reach out to a company, lead with the link: "I built X, here's a 60-second demo, here's the code." That message gets replies that "PFA my resume for your kind consideration" never will. You've done the reviewer's job for them.
"But every job portal asks for a resume"
True — the old pipes still expect paper, and you can keep a simple one-pager for those forms. But notice what's happening: the actual decision increasingly happens on your links, not your PDF. And a new generation of hiring platforms is dropping the PDF entirely.
That's the entire reason we're building Iber. On Iber, builders don't upload resumes — they show verified projects, 60-second demos, and their real GitHub history, and go through structured AI interviews that companies can trust. Your work competes, not your college.
Start this week
You don't need six months. One real project, deployed, with a demo video and a clean README, puts you ahead of the vast majority of applicants — because almost nobody does it. The resume pile is crowded. The proof pile is nearly empty.