Interviewers open GitHub links more than students expect — for 30-60 seconds. That minute forms a judgment: builder or tutorial-follower. Here’s how to pass the minute.
What actually gets checked (in order)
- Pinned repositories — the 4-6 you chose to showcase. Curate these; nobody scrolls page two.
- READMEs — the deciding artifact. What it does, stack, how to run, 1-2 screenshots. An empty README reads as an unfinished thought.
- Commit history — many small real commits over weeks signal genuine building; one “initial commit” dump of someone’s tutorial signals the opposite.
- Code quality at a glance — sensible names, structure, no committed secrets/junk files.
The 3-project portfolio that works
- One complete application — full-stack or solid frontend with real features (auth, CRUD, something deployed if possible). Your interview centrepiece.
- One domain/interest project — an AI agent, a data dashboard, an IoT script — showing curiosity beyond coursework.
- One problem-solving artifact — your DSA solutions organised by topic, or contest solutions with notes. Signals consistency.
Three defensible repos beat fifteen forks. Delete or unpin clutter — noise dilutes signal.
Habits that compound
- Commit as you build (real messages: “add login validation”, not “update”) — history becomes proof of process.
- README before “done”: a project without one is invisible work.
- Deploy what’s deployable — a live link (free hosting exists — guide) multiplies credibility.
- Green-square streaks impress mildly; working software impresses decisively. Optimise for the latter.
Put the link on your resume header, pin your best, and be ready for “walk me through this project” — because on good interview days, that’s exactly what happens.
Frequently Asked Questions
Do recruiters really check GitHub profiles?
Technical interviewers frequently do — briefly. They scan pinned repos, READMEs and commit history to gauge whether projects are genuinely built. A curated profile converts that glance into interview questions you want.
How many projects should be on GitHub for placements?
Three strong, defensible repositories — one complete application, one interest-driven project, one problem-solving collection — outperform dozens of forks and tutorial dumps. Pin them and keep READMEs complete.
What makes a good project README?
What the project does, the stack, setup/run steps, and a screenshot or live link — enough for a stranger to understand and try it in two minutes. The README is often read more carefully than the code.