What you will learn
- Configure the 6 GitHub profile elements recruiters actually check
- Write a profile README that adds signal, not noise
- Pin the right repositories in the right order
Why this matters
When a recruiter clicks your GitHub link from your resume, they spend under 30 seconds on your profile. If they see a default avatar, zero pinned repos, and a sea of forked tutorial repos, they close the tab. Your GitHub profile is your portfolio's front door — it either invites them in or sends them away.
The 6 things recruiters scan (in order)
1. Profile photo and bio
Use a clear headshot (not a cartoon avatar). Write a one-line bio:
Good: "CS undergrad at VIT '27 | Building with LLMs and distributed systems"
Bad: "Passionate coder | Tech enthusiast | Open to opportunities"
2. Pinned repositories (the most important element)
You get 6 pins. Use them deliberately:
- Pin 1-2: Your best, most complete projects (README, tests, clean code)
- Pin 3-4: Technically interesting projects showing range (one backend, one AI/ML, one frontend)
- Pin 5-6: Open-source contributions or course projects with substance
Never pin: Tutorial follow-alongs, empty repos, repos with only an initial commit.
3. README quality on pinned repos
Each pinned repo needs at minimum:
- One-sentence description of what it does
- How to run it locally (install + run commands)
- Tech stack listed
- A screenshot or demo GIF for anything with a UI
4. Contribution graph (green squares)
Recruiters glance at this for consistency, not volume. Steady activity over months beats a one-week burst. Genuine commits to real projects count — do not use commit-padding bots.
5. Commit messages
Recruiters who click into a repo scan the last 5-10 commit messages. These should be descriptive:
Good: feat: add rate limiting to /api/search endpoint
Bad: fixed stuff, update, asdfg, final final v2
Use conventional commits: feat:, fix:, refactor:, docs:, test:.
6. Stars and forks on your repos
You cannot control this, but you can increase it by building genuinely useful things and sharing them on Twitter/LinkedIn/Reddit. Even 5-10 stars signals that someone besides you found the project worth looking at.
The profile README
Create a repo named <your-username>/<your-username> with a README.md. Keep it short:
## Hi, I'm [Name]
CS undergrad at [College] graduating [Year].
I build [2-3 word focus area] — check my pinned repos below.
**Currently working on:** [one project with a link]
**Looking for:** [SDE internships / full-time roles] starting [Month Year]
[LinkedIn](link) | [Email](mailto:you@email.com) | [Resume PDF](link)Do not include: animated GIFs of typing text, mass badge walls for every technology ever, GitHub stats widgets showing "A+ rating." These are noise.
The 15-minute profile cleanup
- Upload a professional photo (2 min)
- Write a one-line bio (2 min)
- Unpin all repos, re-pin your best 3-6 (3 min)
- Add a README to any pinned repo missing one (5 min per repo)
- Create or update your profile README (3 min)
Quick quiz
Q: You have a GitHub repo for a to-do app you built following a YouTube tutorial, and a repo for a custom CLI tool you designed yourself. Which should you pin?
How to explain it in an interview
"My GitHub profile has 4 pinned repositories — each one is a project I built from scratch, not a tutorial follow-along. Every repo has a README with setup instructions, and I use conventional commit messages so the history tells a story. I keep my contribution graph active by working on side projects weekly."