Why Recruiters Open Your GitHub Before They Open Your Resume

Rajan got the interview. He had an 8.2 CGPA. Four years of hard work. A solid resume.

The interviewer opened his laptop, typed something, and turned the screen around.

"This is your GitHub. Can you walk me through one of these projects?"

Rajan looked at the screen. Three repositories. All from his second year. All titled things like "data-structures-practice" and "os-lab-programs." Half of them were empty.

The interview was over before it started.

---

What Recruiters Actually Do Before They Call You

Here is what happens at most tech companies in India today when your resume lands on their desk.

They open LinkedIn. They check your profile. Then they open GitHub. They look at your repositories. Only then do they read your resume.

By the time they read your name and CGPA, they have already made a judgment. Not about your grades. About your work.

This is not an exaggeration. It is how hiring works now, especially at product companies, startups, and any organisation that takes engineering seriously.

The degree shows the foundation you built over four years. GitHub shows what you did with that foundation.

---

Why GitHub Became So Important

Three or four years ago, a fresher could walk into a campus placement drive with a decent CGPA and a list of skills on a resume. The interviewer would ask theory questions. If you answered correctly, you moved forward.

That process still exists at some companies. But it is shrinking fast.

Here is what changed. Companies started losing money on bad hires. They hired freshers with good marks who could not write working code. They spent months training people who had memorised answers but had never actually built anything.

So they started asking for proof.

Not proof of knowledge. Proof of work.

And the easiest place to show proof of work is GitHub. It is free. It is public. Every commit has a timestamp. You cannot fake it the way you can fake a resume line.

---

What a Bad GitHub Profile Looks Like

Most engineering students have GitHub profiles. Most of them look like this:

• 3 to 8 repositories
• All from college assignments or online tutorials
• Names like "todo-app-react-tutorial" or "college-mini-project"
• Last commit: 11 months ago
• README: empty, or just "This is my project"
• No deployed links
• No meaningful description of what the project does or why it exists

This profile does not help you. It actually hurts you. It shows a recruiter that you have heard of GitHub but you have not used it the way professionals use it.

---

What a Good GitHub Profile Looks Like

A good GitHub profile for a fresher does not need to be impressive. It needs to be genuine.

Here is what matters:

1. Consistent activity. Green squares in the contribution graph. Not every day, but regularly. This shows you build things, not just study things.

2. Projects that are described. A good README answers three questions: What does this do? Why did you build it? How do I run it? That is it. Three questions. If your README answers all three, you are already ahead of 80% of applicants.

3. At least one live project. Something deployed. A URL someone can click and see. Even a simple project that is live is more convincing than a complex project that only runs on your laptop.

4. Evidence of professional workflow. Commit messages that are not "initial commit" and "fixed stuff." Multiple commits showing the project growing over time. If possible, evidence of code review: a pull request with comments.

5. A pinned project section. GitHub lets you pin your six best repositories to the top. Use this. Do not make a recruiter scroll through your lab assignments to find the one worthwhile project you built.

---

The Question Students Always Ask

"But I don't have any projects worth showing. I only know college assignment stuff. How do I improve my GitHub when I don't have work experience?"

This is the honest challenge. And it is exactly why programmes like FabForge exist.

The only way to build a strong GitHub portfolio is to do meaningful work. Not tutorial work. Not "I followed a YouTube video and now have a todo app" work. Client-facing work, on a live project, with professional feedback from people who know what they are doing.

The good news is this: three months of structured project work builds a GitHub portfolio faster than anything else you can do on your own.

---

What to Do Right Now

Even before you join any programme or get any internship, here are things you can do today:

1. Complete your profile. Add a photo, a bio, your city, your email. A blank profile looks abandoned.

2. Write a README for every existing project. Even your lab projects. Even the half-finished ones. Three sentences is enough: what it does, what you used to build it, and the current status.

3. Pin your best work. Even if "best" is not very impressive. Pinned is better than buried.

4. Delete the truly embarrassing repositories. Or make them private. Empty repositories and repositories named "test1" and "asdfgh" make your profile look messy.

5. Build one small thing and deploy it. Anything. A portfolio page. A simple calculator. A weather app that uses a public API. Deploy it on Vercel or Netlify, both of which are free. Then add the live link to your README.

These five things take one weekend. They will not make you impressive, but they will make you look like someone who takes their craft seriously. That alone puts you ahead of most freshers.

---

Frequently Asked Questions

Does CGPA still matter for jobs? Yes, but less than it used to. A 7.0 CGPA with a strong GitHub is more competitive than an 8.5 CGPA with an empty one at most product companies. Government PSUs and some service companies still weight CGPA heavily. Know where you are applying.

How many projects should I have on GitHub? Quality over quantity. Two or three well-described, live projects beat ten half-finished tutorial clones. Focus on depth, not count.

What if my code is not very good? Put it up anyway. Recruiters are not expecting perfection from a fresher. They are expecting evidence that you actually write code. A working project with imperfect code is infinitely better than no project at all.

Should I put college lab programs on GitHub? Put them in a single repository called "college-labs" or make them private. Do not showcase them as projects. They are evidence of attendance, not evidence of building.

What is the fastest way to build a better GitHub? Work on client projects with professional feedback. That means finding an internship or programme where your code gets reviewed by working engineers. Three months of that changes your profile faster than three years of solo work.