GUIDE · PORTFOLIO

A developer portfolio built on your GitHub work

A list of repositories is not a portfolio. How to turn three of them into the page a hiring engineer actually reads.

Updated 2 November 2026

The short version

Show three projects, not thirty. For each one say what problem it solves, what you built, one decision you made and why, and link to the code and a working demo. Put your email and GitHub where nobody has to look for them.

Why a list of repositories is not enough

Somebody reviewing applications has a few minutes per person. Your GitHub profile shows names, languages and stars. It does not show judgement — why you built something the way you did — and that is what a reviewer is trying to find out. A portfolio is the guided tour: it tells them which three things to look at and what to notice.

Choose three projects

  • One that goes deep. A hard problem you stayed with: a sync engine, a parser, a scheduler, a tricky data model.
  • One that shipped. Something real people used, even if it was ten classmates or a shop down the road.
  • One that shows range. A different stack or a different kind of problem from the other two.

Leave out tutorial clones unless you took them somewhere the tutorial did not. A recent, modest project you understand completely beats an impressive one from years ago you can no longer explain.

Write each project as a short case

  1. The problem, in one sentence a non-engineer would follow.
  2. What you built. The stack goes in one line underneath, not in the headline.
  3. One decision. A trade-off you made and why: “SQLite rather than Postgres, because it runs on the shop's single laptop with no server.” This is the line reviewers remember.
  4. The result. What changed because it exists. Use numbers only if they are real.
  5. Links: the code, a live demo, and a short write-up if there is one.

Make the code easy to judge

Whoever clicks through will open the README first. Give it a screenshot, one paragraph on what the project does, and the exact commands to run it. Tests, a tidy commit history and clear folder names say more about you than a long feature list. If one file or pull request shows your best work, link straight to it.

The page itself

Your name and one line about what you build; the three projects; a short paragraph about you; and how to get in touch — email, GitHub and LinkedIn. Dark or light does not matter. Readable text, working links and pictures of the actual product do.

Mistakes that cost interviews

  • Skill bars with percentages. Nobody knows what “Java 80%” means, and it invites the question you cannot answer.
  • Every language you have ever touched. List what you would be comfortable being interviewed on.
  • A demo link that is down. Open every link the day you send the portfolio out.
  • Template text still on the page — a sample name, a placeholder email, “Project title”.

Doing this in XODE

The portfolio editor has templates made for developers. Start from one, replace the sample text with your own, or let the XODE Agent fill it from a resume you already have — you see every change before it is made. When you publish, the dialog points out anything that still reads as the template wrote it, picture boxes left empty and missing contact details, and the portfolio goes live at its own address on xodeinc.com.

More guides

Try it on your own work

Free, in your browser. Start from a template and replace it with your own words.