You put your GitHub link on your resume. A hiring manager clicks it. Now you have about 30 seconds.
What do they see? For most people: an empty profile, six forked tutorial repos, and a green contribution graph that stopped in March.
It doesn't take much to fix. Most of it you can do tonight.
In 30 seconds
- Add a profile README: who you are, what you build, 2 to 3 best projects
- Pin your 4 to 6 best repos, not forks or tutorials
- Every pinned repo needs a README with a live link and a screenshot
- The contribution graph matters less than quality of what's pinned
What they look at in 30 seconds
- The top of your profile: name, photo, a one-line bio
- The profile README (if you have one)
- Pinned repositories: names, descriptions, languages
- One repo, opened: is there a README? Does it run? Is the code readable?
Notice what's missing: nobody counts your stars.
The profile README (copy and edit)
Create a repo with the same name as your username. Its README shows at the top of your profile.
# Hi, I'm Priya 👋 Backend developer · Node.js, Postgres · Pune, India I build small tools that real people use. ## What I've built - **[ShopBot](link)**: WhatsApp ordering bot used by a few local shops. Node, WhatsApp API. - **[CampusRide](link)**: live campus shuttle tracker. React, Firebase. - **[ExpenseSplit](link)**: Hindi/English bill splitter for hostel rooms. ## Writing - [How I cut my bot's reply time from 4 s to 400 ms](link) ## Right now Learning: system design basics · Open to: backend roles, 2026 📫 [your email] · [LinkedIn] · [Portfolio] Keep it short. No 40 skill badges, no animated banners, no "visitor counter".
Fix your pinned repos
Pin: 4 to 6 repos you built yourself, ideally with real users.
Unpin: forks, course assignments, "hello-world", empty repos.
Rename vague repos:
❌ project-final-v2
✅ campus-shuttle-tracker
Add a one-line description to every pinned repo: what it does and for whom.
A README that works for every pinned repo
- One line: what it is and who uses it
- Live link and a screenshot or GIF
- How to run it in 3 to 5 commands
- How it works: a short paragraph or a simple diagram
- What I'd do next: shows you think beyond "done"
Small things that add up
- Clear commit messages ("fix: retry failed payments" beats "update")
- A .gitignore so no
node_modulesor.envfiles are committed - No secrets in the code. Ever. Check old commits too
- One open-source contribution, even a docs fix, shows you can work in someone else's codebase
Save this tonight: profile README + 4 to 6 real pinned repos + a README with a live link on each. That's your first interview, done before the call.
Put it where recruiters already are
Disclosure: we build InfiniteInterfaces, a free builder network. Your projects, write-ups and hackathon results sit on your profile and go with every application, next to your GitHub link. Candidates never pay.
👉 Add your projects to your profile free
The name and projects in the sample README are made up. Use your own.


