Putting Your GitHub on Your Tech Resume: Best Practices

<h2>Why your GitHub is your strongest asset</h2> <p>In the tech world, your GitHub often speaks louder than your degree. Recruiters and senior engineers running interviews will systematically check your profile. Give them something worth looking at.</p> <h2>Optimizing your GitHub profile</h2> <h3>The profile README</h3> <p>GitHub lets you display a README on your profile page (create a public repo with the same name as your username). Put in:</p> <ul> <li>Your title and specialty</li> <li>Your primary stack</li> <li>Your 2-3 flagship projects with a one-line description each</li> <li>Your GitHub stats (github-readme-stats)</li> </ul> <h3>Pinned Repositories</h3> <p>Pick 4-6 repos to feature. Each one should have:</p> <ul> <li>A complete README with a demo GIF or screenshots</li> <li>A clear one-sentence description</li> <li>Topics (languages, frameworks) properly tagged</li> <li>A .env.example if the project requires environment variables</li> </ul> <h2>How to reference GitHub on your resume</h2> <p>Place the link in the header, not under skills. Recommended format:</p> <p><strong>github.com/your-handle</strong> — 12 public repos, X contributions in 2024</p> <p>When you cite a project on your resume, add the direct link to the repo:</p> <p>"Project X — <em>React, FastAPI, PostgreSQL</em> | github.com/you/project-x | 45 stars"</p> <h2>Negative signals to avoid</h2> <ul> <li>An empty profile or one with only forks</li> <li>Commits only at night or on weekends (it can suggest you are coding during work hours...)</li> <li>Non-descriptive commit messages ("fix", "test", "wip")</li> <li>Spaghetti code with no comments in your public repos</li> <li>An empty README — that is a deal-breaker</li> </ul> <h2>Open source: how to leverage it</h2> <p>If you have contributed to open source projects (even small fixes), mention it. A merged PR in a well-known project (React, FastAPI, shadcn, Next.js...) is worth more than 10 side projects.</p>