Your GitHub portfolio: what recruiters actually look at

Should you put your GitHub on your resume? Do recruiters actually click it? Short answers: yes, and yes — but not the way you hope. Nobody reads your code line by line. Your GitHub profile gets skimmed like a resume: about thirty seconds, in a predictable order. Treat it as a portfolio and those thirty seconds work for you.

What recruiters see, in order

1. The contribution graph. It's the biggest visual element on your profile, and it reads at a glance: is this person active? A wall of gray says "abandoned account" before anyone scrolls further — fair or not.
2. Pinned repositories. The six tiles under your bio are the only repos most visitors will ever see. Empty pins mean GitHub chose for you, badly.
3. Repo names and descriptions. final-project-2 tells a story; so does flight-price-tracker — scrapes and charts airfare trends. Only one of them is a good story.
4. READMEs — if you're lucky. A reviewer who clicks into a pinned repo gives its README ten seconds: what is it, can I see it running, is there a screenshot?
5. Your profile README. Optional, but it's the one place you control the narrative: who you are, what you build, where to find the good stuff.

Notice what's not on the list: code quality. Engineers who interview you may read code later. The skim that decides whether you get that interview is all surface — which is exactly why the surface is worth an afternoon.

Making your GitHub a portfolio, in an afternoon

• Pin deliberately. Six slots: your two or three best projects, anything with real users or stars, and nothing that's a tutorial-follow-along.
• Write READMEs like landing pages. One sentence on what it does, a screenshot or GIF, how to run it. Your best project with a blank README is invisible work.
• Name and describe every public repo — the description shows up in the pinned tile and in search.
• Add the link to your resume. A GitHub link on a resume gets clicked more than a personal site — it's where technical hiring already lives.
• Keep the graph alive. Consistency reads as passion at a glance. Small real contributions count double here: issues, reviews, and doc fixes all light up squares. And if your real work hides in private repos and feature branches, fix the common reasons work doesn't show — or let GitShine keep a steady, natural-looking baseline on repos you choose, free.

The honest hierarchy

A green graph gets your profile a second look; pinned repos with real READMEs get you a conversation; the code gets you the offer. Each layer only matters if the one before it worked. Spend effort in that order — and let the maintenance (the part that's pure discipline, not craft) take care of itself.