It's Not About the Green Squares
The GitHub contribution graph — the grid of green squares showing your daily commit activity — is the most misunderstood metric in engineering hiring. Junior engineers obsess over maintaining a "streak." Hiring managers and engineering managers largely ignore it. What they actually look at is: can this person finish something, document it, and make it usable by someone else?
A repository with 500 commits and no README communicates one thing: this engineer writes code for themselves. A repository with 50 commits, a clear README, a working demo, and an architecture diagram communicates something far more valuable: this engineer thinks about their audience.
The Pinned Repository Strategy:
GitHub allows you to pin up to 6 repositories on your profile. Treat these as your portfolio. Pin 2–4 repositories that represent your best work across different domains. Each pinned repo must have a Golden README — a README that functions like a product landing page.
A Golden README contains:
- What is it? (1 sentence): "A distributed rate limiter built in Go using Redis and the token bucket algorithm."
- Why does it exist? (1–2 sentences): "I built this to understand how API gateways implement rate limiting at scale."
- Screenshot or GIF: Show it working. A 10-second GIF of the app running is worth more than 500 words of description.
- Tech Stack badges: Use shields.io badges for a clean visual summary.
- How to run it (copy-pasteable):
git clone ... && docker-compose up. If it takes more than 3 commands to run, it won't be run. - Architecture diagram: A simple box-and-arrow diagram showing how components interact. Draw it in Excalidraw or Mermaid.
The Profile README:
GitHub supports a special repository — username/username — whose README.md is displayed at the top of your profile page. Use this as a professional introduction:
## Hi, I'm [Name]
Senior Backend Engineer specializing in distributed systems and Go.
Currently building [X] at [Company].
**What I'm working on:** [Current project]
**What I'm learning:** [Current focus]
**Writing about:** [Blog link]
Keep it short. Three to five lines. Link to your blog and LinkedIn. This is the first thing an engineering manager sees when they visit your profile.
Red Flags to Eliminate:
- Repositories named "test," "practice," or "homework" pinned to your profile.
- A pinned repo with only an "Initial Commit."
- A README that says only "TODO."
- Forked repositories with no modifications pinned as if they were your work.
Each of these signals the same thing: this engineer doesn't think about how their work is perceived by others — a soft skill that matters enormously at senior levels.
Key Point: The most effective GitHub portfolios are not the ones with the most repositories — they are the ones where every pinned repository tells a complete story. One finished, well-documented project that solves a real problem is worth more than twenty half-finished experiments. Engineering managers hire people who ship, and a polished repository is the closest thing to a shipped product you can show without a production system.