# Portfolios and GitHub for senior roles

> A senior portfolio is not more projects, it is proof of judgement. Show the decisions, not the repository count.

_Category: Winning the application · Updated: 2026-10-15 · 2 min read_

A senior portfolio is not more projects, it is proof of judgement. Show the decisions, not the repository count.

## Curate ruthlessly

Three to five pieces, each with a clear problem, your contribution, and the outcome. For senior roles, one deep case study beats ten demos.

## Write for the reader

For each project, answer: what was the problem, what did you decide, what happened? Include the trade-off you made and why. That is what "senior" looks like on a page.

## GitHub, honestly

Recruiters will skim your pinned repos for a minute at most. Make the top three represent your best work, with a real README at the top of each. Consistent, meaningful commits say more than a green wall, and a private work repo is a fine answer if that is your situation.

## What you are really showing

Evidence that you can hold a problem in your head, communicate a plan, and finish. The exact stack matters less than these three, and they connect directly to [your CV](/guides/developer-cv-for-remote-roles) and [the interview](/guides/preparing-for-a-remote-technical-interview).

## If you feel you have nothing to show

Write about a hard problem you solved at work (anonymised), or a small tool you built to scratch your own itch. A single well-explained project is enough to start.