A public GitHub is a free interview. Most hiring teams either ignore it or read it wrong.
You do not need an hour. You need ten minutes and the right five questions.
What to look at
- A recent project they wrote, not forked. Read one pull request top to bottom.
- Their commit messages on real work. Are they explaining the why, or just "fix"?
- How they reply to issues. Patient and clear? Or short and defensive?
- One README they wrote. Can a stranger run their code?
That is the whole list. Ten minutes.
What to ignore
Total commit count, star totals, contribution graphs, the year they joined. These tell you who has time, not who is good.
Side projects do not need to exist. Many strong engineers have a private GitLab and a quiet life.
How this fits a real interview
GitHub is the screening signal. It tells you who is worth spending time on.
The real test still happens in a live environment, where you watch them solve a problem on your stack. EasyEnv handles that part. Same starting point per candidate, full session recording.
GitHub gets them into the room. The room is where you actually hire.
What is the last GitHub profile that changed your mind on a candidate?