Learn / Careers

What recruiters check on your GitHub profile (from a recruiter)

I run a technical staffing firm. When a junior candidate lists Git and GitHub, I open their profile. Here is what I look at, in the order I look at it, and how to fix yours in a weekend.

Two candidates, one interview

Two candidates. Similar resumes. Both listed “Git and GitHub”. Only one got the interview.

Candidate A: two tutorial projects copied from a course. No READMEs. Every commit made the same night, all called “update”.

Candidate B: three small projects of their own. Each had a README with a screenshot and how to run it. Commits spread over two months. One pull request where they fixed their own bug.

B was not more experienced. B just made it easy to see what they could do. That is what your GitHub is: proof, in about 30 seconds.

My checklist

  1. 3 to 6 pinned projects that are actually yours. Not forks, not a course's finished code. Small is fine. Yours is what matters.
  2. A README on each one that says what it does and how to run it. A screenshot helps a lot.
  3. Commits spread over weeks, not one big upload the night before you applied.
  4. Clear commit messages. “add cart total” tells me something. “fix” and “stuff” do not.
  5. Pull requests, even on solo projects. A branch, a pull request and a merge shows you know how teams work.
  6. No passwords or .env files in the history. This one can end a review on its own.

Fix it in a weekend

Saturday: clean up what you have

  • Pick your best 3 to 6 projects and pin them on your profile.
  • Write a README for each: one line on what it does, a screenshot, and the exact commands to run it.
  • Make old tutorial copies private, or label them clearly as course work.
  • Check for secrets. If you ever committed a password or API key, change it at the source first. Deleting the file later does not remove it from history.

Sunday: show how you work

Make your next change the way a team would, even if you are the only one on the project:

git switch -c fix/readme-typo                     # a branch for one change
git commit -am "docs: fix setup steps in README"  # a message that says what changed
git push -u origin fix/readme-typo                # share the branch
gh pr create --fill                               # open a pull request, then merge it

Then keep a habit: commit as you go, a little at a time. Weeks of small, clear commits look very different from one upload.

What I don't care about

  • The green squares on their own. Activity helps, but empty commits made to fill the grid are easy to spot.
  • Stars and followers. Nobody expects a junior candidate to have them.
  • Fancy profile decorations. A short bio, your location and how to reach you are enough.

Your resume says “Git”. Your GitHub proves it or it doesn't.

If you are not sure how branches, pull requests and clean history work yet, start with undoing mistakes safely, then work through a real team workflow. Preparing for a certification too? Here is a GH-900 study plan.

From the book

Git / GitHub Study Guide

151 pages for beginners: every command explained, 4 local drills with a PASS or FAIL checker, 4 GitHub labs written as work tickets and GH-900 exam prep.