What makes a strong software-engineer portfolio
The portfolios that land interviews don't list every repo — they show judgment. A great developer portfolio leads with a few projects explained in plain language: what problem it solved, what you actually built, and the evidence (a merged PR to a well-known project says more than fifty solo forks). It makes contribution volume legible — private and org work included — and it reads in under a minute.
The hard part is writing it. gitshow does that pass for you: it reads your GitHub the way a senior reviewer would, picks the work that signals the most, and drafts the prose. You edit, you publish. The cards above are the output.