When recruiters and hiring managers look for software engineers, GitHub is one of the first places they check. Your profile works as a living résumé: it shows not just what you know, but how you write code, how you collaborate, and how consistently you build. Most reviewers spend a minute or two on it, so the goal is to make your best work obvious quickly.
Here is a checklist, roughly in order of impact.
1. Fill in the profile basics
Use a clear photo or avatar, your real name (or the name you use professionally), and a bio that says what you do in one line, for example "Frontend engineer · React, TypeScript, accessibility". Add your location or time zone, and link to your website or LinkedIn. Recruiters search by skill and location, so these fields help you get found.
2. Pin your best work
Don't make reviewers dig through dozens of forks and tutorial repositories. Pin up to six repositories that show the work you want to be hired for. Prefer original projects over forks, and real projects over course exercises. If you contribute mainly to other people's projects, you can pin those repositories too.
3. Give every pinned repo a great README
A great project with no explanation is invisible. Each pinned repository should say what it is, why you built it, how to run it, and which technologies it uses. Add a screenshot or a short GIF for anything visual, and a live demo link if you can host one. Mention the decisions you made and the trade-offs, because that is what interviewers ask about.
4. Write good repository descriptions and topics
The one-line description and topics appear in search results and on your profile. "Real-time chat app with WebSockets, Redis and React" is far better than an empty description. Topics like react, websocket and redis also make the project discoverable.
5. Show consistent activity
The contribution graph isn't everything, but a completely blank one can raise questions. Regular contributions over time say more than a burst of commits once a month. If most of your work happens in private company repositories, turn on "Include private contributions on my profile" in your settings so the graph reflects your real activity (the details stay private).
6. Contribute to other projects
Pull requests to other projects show you can read unfamiliar code, follow conventions and take review feedback, which are core skills in any engineering team. Even small fixes to documentation or tests count. Merged PRs to well-known projects are strong signals.
7. Add a profile README
A profile README appears at the top of your profile and lets you introduce yourself, highlight projects and link to your writing. See our profile README ideas for examples you can copy.
8. Clean up what distracts
Archive or make private any abandoned experiments, empty repositories and forks you never changed. Make sure no repository contains secrets, API keys or personal data. Recruiters notice leaked credentials.
Measure your progress
Run your profile through GitScore before and after these changes. The breakdown shows which areas are strong and which need work, and the "How to raise your score" section suggests the actions with the biggest effect for your profile.